Toolsbook - My First Project!

Designers collect inspiration. Developers build systems. I did both.

🎨 Why I Built Toolsbook

As someone who designs and builds websites, I'm always hunting for inspiration.

• Clean layouts
• Bold typography
• Smart interactions
• Creative portfolios

Every time I found a cool site, I’d either forget it, lose the tab, or dump it into generic bookmarks. Nothing was organized — no categories, no screenshots, no context.

That’s when it clicked 💡

🤯 What if I could save websites I like — instantly — and categorize them?

⚙️ How the Idea Took Shape

I built a Chrome extension.

Now, whenever I like a site, I just click the extension — and boom 💥:

• It saves the title, URL, and description
• Takes a screenshot
• Lets me tag it with custom categories like "hero sections", "ecommerce", "minimal", etc.

It’s like a private inspiration library — built just for me.

🔍 I Explored Existing Alternatives...

But nothing felt quite right.

Here’s a quick comparison of Toolsbook vs other options:

🛠 How I Built It

Stack

• Frontend: React + Tailwind CSS
• Extension: Chrome Extension using manifest v3
• Backend: Express.js + Puppeteer for screenshots
• Database: JSON / lightweight store
• Hosting: Vercel

🚀 What's Next?

• 🔐 Login & multi-device sync
• 🗂️ Organize collections visually
• 🧠 AI-based suggestions: "This site looks like X"
• 📝 Notes/comments on saved links
• 📊 Usage analytics: Which categories you browse most

💭 Final Thoughts

Toolsbook isn't about showing off. It's about building a personal playground — where all the creative sparks I find get saved, sorted, and seen again when I need them most.

If you’re a designer or dev always chasing good taste — Toolsbook might be your secret weapon.

Built with passion & pixels — Harsh