When building something as ambitious as Peekberry—a Chrome extension and webapp that lets anyone restyle a website with natural language—you quickly realize a good idea isn’t enough. To actually ship, you need speed, structure, and a way to keep a fast-moving project from spiraling out of control.
That’s where Kiro, an AI-powered IDE assistant, became the backbone of our process. From planning and architecture to implementation and release automation, Kiro shaped every part of Peekberry’s development workflow. The result: a modern product that shipped fast, stayed maintainable, and was stable enough to reach real users.
👉 Try it yourself at peekberry.com.
Why Peekberry Exists
Peekberry is designed for non-technical teams—sales reps, product managers, and designers who want to experiment with visual changes instantly. Instead of waiting through endless dev cycles, they just type something like:
“Make the title bigger and move the button to the center.”
Peekberry applies the change live in the browser.
That deceptively simple moment is powered by a carefully structured workflow. Here’s how Kiro made it possible.
Specs: Clear, Traceable Requirements
Peekberry’s foundation was Kiro’s Spec system. Every requirement, design diagram, and task lived in .kiro/specs/peekberry-mvp/, making it easy to tie implementation back to goals.
- Requirements: User stories, acceptance criteria, and success metrics.
- Design: Architecture diagrams, database schema, UI specs.
- Tasks: A roadmap of 15 phases, each linked to requirements.
👉 Nothing slipped through the cracks, and we always knew what to build next.
Steering Rules: Built-In Consistency
Kiro also enforced steering documents: tech stack choices, UI guidelines, file structure, and even long-term product vision.
👉 Every code generation, every edit, every commit followed the same playbook—keeping consistency without constant human review.
Hooks: Automating the Mundane
From refreshing demo scripts to updating changelogs, Kiro’s hooks kept documentation in sync automatically.
👉 We never wasted time on the repetitive things teams usually forget.
MCP Integration: Database and Services, Without Leaving Kiro
By plugging into Supabase through Kiro’s MCP server, developers could manage schemas, run queries, generate types, and deploy functions—all inside the IDE.
👉 Type-safe APIs and safe migrations became a default, not an afterthought.
Context-Aware Development
Kiro pulled in everything: file context, git diffs, linting, and even project history.
👉 It felt less like a tool and more like an extra teammate who already knew the codebase inside out.
Workflow in Action
- Plan: Specs and steering files set direction.
- Build: Kiro generated consistent, standards-compliant code.
- Ship: Hooks updated docs, changelogs, and demos automatically.
This cycle repeated until we had a working MVP—polished enough to demo, reliable enough for real use.
The Payoff
- Speed: Faster iteration thanks to spec-driven planning and automation.
- Quality: Consistent UI, type safety, and enforced standards.
- Maintainability: Clean structure, synced docs, and auto-changelogs.
In short: we moved quickly without the usual chaos.
From Prototype to First Client
And then came the milestone every builder waits for: our first client conversation.
Attached below is a snapshot of the email that landed in our inbox right after the MVP demo.
It’s early days, but that message validated two things:
- Peekberry solves a real problem.
- Kiro gave us the speed and structure to actually get there.
Closing Thought
Peekberry isn’t just a Chrome extension. It’s proof of how AI-powered development environments like Kiro can transform the way software is built—bringing the rigor of a seasoned engineering org to the pace of a startup.
The result? A production-ready product, real user traction, and the confidence to scale from here.
👉 Try Peekberry at peekberry.com.
Top comments (0)