<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx" -->

---
title: Vibe Coding Broke Brokit.io. Agentic AI Engineering...
description: A developer shares their experience building Brokit.io, a browser-based developer toolkit, comparing two AI-assisted development approaches. &quot;Vibe coding&quot;...
canonical: https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Vibe Coding Broke Brokit.io. Agentic AI Engineering Rebuilt It. | daily.dev
og:description: A developer shares their experience building Brokit.io, a browser-based developer toolkit, comparing two AI-assisted development approaches. &quot;Vibe coding&quot;...
og:url: https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx
og:image: https://api.daily.dev/og/posts/6WO8YlmZx.png
og:image:alt: Vibe Coding Broke Brokit.io. Agentic AI Engineering Rebuilt It.
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Vibe Coding Broke Brokit.io. Agentic AI Engineering Rebuilt It.

**[Build With GenAI](https://daily.dev/sources/buildwithgenai)** · [@abhishekdeb](https://daily.dev/abhishekdeb) · 4 min read · 1 upvotes · 0 comments

## Summary

A developer shares their experience building Brokit.io, a browser-based developer toolkit, comparing two AI-assisted development approaches. "Vibe coding" (prompt-generate-paste) enabled rapid initial development but created unmaintainable spaghetti code. Switching to "agentic AI engineering" with structured blueprints, defined roles, and architectural documentation slowed initial progress but enabled predictable scaling. The structured approach uses multiple specialized agents (UI, backend, validation) operating within defined contracts, transforming AI from a code generator into an orchestrated system builder. The author questions whether structure is necessary for AI-assisted development to scale beyond small prototypes.

## Content

Disclaimer - the tool is under active development and there might be some QA issues and UI .. i really need to spend some more time with it.

Over the past few days, I’ve been experimenting with stable and reliable agentic development workflow.

To properly test both approaches, I decided to build something real — not a demo, not another AI wrapper — but a practical tool developers might actually use.

That project became **Brokit.io** — a browser-based developer toolkit.

## What Went Wrong with Vibe Coding (Inside Brokit.io)

When I first started building **Brokit.io**, I went full vibe coding.

Prompt. Generate. Copy. Paste. Ship.

The first tool inside Brokit.io was built in under 10 minutes. It worked. It felt magical.

Encouraged by that, I built three more tools for Brokit.io within the next hour.

That’s when things started falling apart.

The codebase for Brokit.io began turning into spaghetti.
Logic lived in unexpected places.
Files were loosely structured.
Data flow wasn’t clearly defined.

Some parts of Brokit.io worked, but I couldn’t confidently explain why. If something broke, I wasn’t sure which part of the system was responsible.

Brokit.io was growing, but it felt unstable. I had speed, but no clarity. It felt like there was invisible “magic code” inside Brokit.io that might explode someday — and I wouldn’t know how to fix it.

That’s when I realized vibe coding is great for momentum, but dangerous for anything meant to scale.

![brokit screenshot.png](https://media.daily.dev/image/upload/s--ZqZWN0yc--/f_auto/v1771049182/ugc/content_2f131e8d-599d-4b12-a158-704f8c1600bb?_a=BAMAMiiu0)

## Resetting Brokit.io with Agentic AI Engineering

I wiped things back and rebuilt Brokit.io using a structured agentic AI engineering approach.

Instead of prompting randomly, I treated Brokit.io like a real software system.

Before writing code, I created the blueprint.

I defined:

- `plans.md` — high-level system planning for Brokit.io
- `instructions.md` — coding standards and architectural rules for Brokit.io
- `agents.md` — clear roles for each agent (UI, backend, validation, styling, refactor)
- Execution flow documentation — how requests move through Brokit.io
- A closed-loop monitoring mindset — every change reviewed and validated

This was not about generating code faster. It was about generating code intentionally.

It took about an hour just to structure Brokit.io properly. Another hour went into refining the first tool with controlled architecture, clear file boundaries, defined execution flow, consistent styling, and predictable state management.

That initial investment slowed me down.

But then something interesting happened.

The next five tools inside Brokit.io took about 3–4 minutes total.

Not because of randomness.

Because of parallel agents operating inside a structured system.

One agent handled UI scaffolding.
Another ensured consistency with `instructions.md`.
Another verified execution flow.
Another refactored for clarity.

Brokit.io stopped feeling like a pile of generated code and started feeling like an engineered system.

Now, when I look at Brokit.io:

I know exactly where each tool lives.
I know how data flows through the system.
I know what executes locally and what executes on the server.
I know how to extend it safely.

There is no hidden magic. No mysterious side effects.

Brokit.io feels stable.

## What Agentic AI Engineering Actually Feels Like

For me, agentic AI engineering is less about automation and more about orchestration.

It’s almost like building the architectural blueprint first — defining rooms, corridors, plumbing, and electrical layout — and then letting AI construct the building under supervision.

The AI writes the code.
The AI does basic QA.
The AI follows defined contracts.

But the human defines the system.

It’s not vibe-based. It’s system-based.

And inside Brokit.io, that difference is very visible.

## The Latest Tool Built This Way

The most recent tool I shipped under this structured setup is the Cron Expression Builder:

[https://www.brokit.io/tools/cron-builder](https://www.brokit.io/tools/cron-builder)

It’s small. But it represents a shift in how Brokit.io is being built.

## What I’m Trying to Validate

Is vibe coding enough for small tools?
Is agentic engineering overkill?
Or is structure the only way AI-assisted development actually scales?

[Brokit.io](https://www.brokit.io/) is becoming my testbed for that question.

If you’ve been building with AI recently, I’m genuinely curious:

Are you vibe coding?
Have you hit the invisible spaghetti wall?
Have you tried building a blueprint first?

Would love honest thoughts.

PS. I built the whole thing in 9 hours total spread across 5 days. Actual tool development and functional requirements were done under 5 hours. rest were ui styling and non functional stuff. 

PS2: Let me know if you need to know the bare minimum setup using cursor or claude cli

## Similar posts on daily.dev

- [My Take on Vibe Coding VS Agentic Engineering](https://daily.dev/posts/my-take-on-vibe-coding-vs-agentic-engineering-ztogp6y0v) · W endell Adriel · 0 upvotes · 0 comments

---

Tags: [#ai](https://daily.dev/tags/ai), [#architecture](https://daily.dev/tags/architecture), [#devtools](https://daily.dev/tags/devtools)

[View this post on daily.dev](https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx","headline":"Vibe Coding Broke Brokit.io. Agentic AI Engineering Rebuilt It.","text":"A developer shares their experience building Brokit.io, a browser-based developer toolkit, comparing two AI-assisted development approaches. \"Vibe coding\" (prompt-generate-paste) enabled rapid initial development but created unmaintainable spaghetti code. Switching to \"agentic AI engineering\" with structured blueprints, defined roles, and architectural documentation slowed initial progress but enabled predictable scaling. The structured approach uses multiple specialized agents (UI, backend, validation) operating within defined contracts, transforming AI from a code generator into an orchestrated system builder. The author questions whether structure is necessary for AI-assisted development to scale beyond small prototypes.","url":"https://daily.dev/posts/vibe-coding-broke-brokit-io-agentic-ai-engineering-rebuilt-it--6wo8ylmzx","datePublished":"2026-02-14T06:10:29.605Z","dateModified":"2026-03-15T03:28:22.160Z","author":{"@type":"Person","name":"Abhishek Deb","url":"https://daily.dev/abhishekdeb","image":"https://lh3.googleusercontent.com/a/ACg8ocJ07shqjSJq3IQQxHqwgJv9r3DoA6lY9jVIF4C5J-W1z2xrj0B2FQ=s96-c","description":"Typescript Enthusiast, Platform Engineering, DevOps, learning rust ","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":260}},"image":"https://media.daily.dev/image/upload/s--rUpT4FQY--/f_auto/v1771049430/posts/6WO8YlmZx?_a=BAMAMiiu0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/buildwithgenai","name":"Build With GenAI"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Build With GenAI","item":"https://daily.dev/squads/buildwithgenai"},{"@type":"ListItem","position":3,"name":"Vibe Coding Broke Brokit.io. Agentic AI Engineering Rebuilt It."}]}
```

