Structured Output Format Generator
Design a precise output format spec that makes AI responses consistent, parseable, and ready to use.
Turn a plain-language feature description into a complete, buildable code scaffold — with file structure, typed interfaces, API contract, and implementation order.
You are a senior software architect. I'll describe a feature and you'll generate a complete blueprint I can start building from immediately — not pseudocode, real code with typed stubs. Feature description: [describe what it does, who uses it, and how it behaves — plain language is fine] Stack: - Language: [e.g. TypeScript] - Framework: [e.g. Next.js / Express / FastAPI] - Database: [e.g. PostgreSQL / MongoDB] - Auth: [e.g. Supabase / JWT / none] Return: 1. **File Structure** — which files to create, where, and why each exists 2. **Non-Goals** — what this feature explicitly does NOT do (prevents scope creep) 3. **Data Model** — types or schema for any new data this feature requires 4. **API Contract** — endpoints or server actions with typed request/response shapes 5. **Core Implementation Stubs** — main functions/components with typed signatures and TODO comments 6. **Key Architectural Decisions** — 3 choices baked into this blueprint worth being aware of 7. **Implementation Order** — what to build first, second, third for fastest path to working 8. **Rollback Plan** — how to cleanly revert if this needs to be pulled after shipping Output runnable code. Stubs should be empty but correctly typed and importable.
Developers starting a new feature, solo builders translating product specs into buildable code.
A buildable feature blueprint with file structure, non-goals, typed data model, API contract, typed implementation stubs, 3 architectural decisions, implementation order, and a rollback plan.
Sign in to leave a comment.
No comments yet.
Be the first to share your thoughts.
Works best with
Claude Opus 4
Design a precise output format spec that makes AI responses consistent, parseable, and ready to use.
Breaks down any code snippet into plain English — from high-level intent down to line-by-line mechanics.
Walks through a system design problem the way a staff engineer would — with trade-off analysis, component breakdown, and scaling considerati…