Hey everyone. I built SpecRabbit to solve a problem I kept hitting personally: AI fills in architectural gaps you never specified, and you spend more time fixing wrong decisions than you saved.
Curious what workflows you're currently using before you start generating code with Cursor, Claude Code, or similar tools. Text descriptions? Markdown specs? Just winging it and fixing after?
Hey Product Hunt! š Oleg here, founder of SpecRabbit.
I built this after hitting the same wall repeatedly with AI coding agents - describe your architecture in text, AI fills in the gaps with its own assumptions, you spend hours correcting decisions you never made.
SpecRabbit takes a different approach: draw your architecture as a typed node graph instead of describing it. UI forms, API endpoints, backend services, databases - all connected by explicit named flows. Every node has typed parameters plus a free text field for behavioral context like "roll back inventory reservation if payment fails."
Export as a single JSON or YAML file. The export includes built-in instructions for your AI coding agent explaining exactly how to interpret every element. Feed it to Cursor, Claude Code, or any AI agent - it generates code matching what you designed, not what it guessed.
A few things that make it different:
⢠Enforced completeness - you can't add an endpoint without auth level or a database connection without defining query to run.
⢠Structured JSON output the AI reads natively - no image recognition, no markdown parsing, minimal tokens.
⢠Free text description per node for behavioral context that doesn't fit a schema.
The post hit #1 on r/VibeCodeDevs with 52K views and 70 upvotes in 3 days, which told me the pain is real.
Free tier available - 2 projects, 15 nodes, all node types, full export. Would love your feedback and questions!