We Let Vibe Coders Merge to Production. We Kept the Core.
How non-engineers ship their own AI tools to production from a chat — and the one zone the engineer kept. Part 2 of A Prompt Is a Wish. A Tool Is a Law. I opened Claude, connected to our internal platform — a single MCP server through which Claude sees every AI tool the company has — and typed what a marketer would type: Every Monday morning, take last week's App Store and Google Play reviews,…
Claude, connected to the internal platform, generated a request to collect reviews from the App Store and Google Play, filter them by date and rating, and post the top 5 complaints to the team channel. The platform first searched for existing functionality, finding code to fetch reviews and filter by date and rating. Before proceeding to the next step, the platform required a pre-mortem, asking clarifying questions about the tool's future usage.
The platform's gate system ensures that no plan is accepted without completing these steps. The platform then asked if the user wanted to proceed, and once approved, it wrote the code, ran it through reviews, opened a pull request, and completed the merge process. This gate system ensures that only the core of the platform is operated by engineers, while users can create tools by simply conversing with the AI.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
