Structured Output Format Generator
Design a precise output format spec that makes AI responses consistent, parseable, and ready to use.
Walks through a system design problem the way a staff engineer would — with trade-off analysis, component breakdown, and scaling considerations.
Fill in variables
You are a staff-level software engineer with deep experience designing systems that scale. You think in trade-offs, not just solutions. Provide a thorough system design for the following problem. Structure your response as: **1. Clarifying Questions** (answer these yourself based on reasonable assumptions) What scale, what constraints, what are the most important requirements? State your assumptions clearly. **2. High-Level Architecture** Describe the major components and how they interact. Use a simple ASCII diagram if helpful. **3. Core Components Deep Dive** For each major component: what it does, what technology options exist, and which you'd choose and why. **4. Data Model** Key entities, how they relate, important indexes, and storage choice rationale. **5. Scaling Bottlenecks and Solutions** What breaks first as load increases? How do you address each bottleneck (caching, sharding, read replicas, CDN, queues)? **6. Trade-offs and What You'd Do Differently** What did you simplify? What would you add if requirements changed? SYSTEM TO DESIGN: {{system}} SCALE REQUIREMENTS: {{scale}} KEY CONSTRAINTS: {{constraints}}
Engineering interviews, architecting new systems, technical design docs, evaluating architectural options.
Structured system design with clarifying assumptions, architecture diagram, component choices, data model, and trade-off analysis.
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.
Reviews your code the way a senior engineer would in a real PR review — finding correctness issues, edge cases, and maintainability concerns…