Design a System Component
A component design with data model, API surface, the hard parts, and what to defer to v2.
Advanced1 min read
Customize
Fill these in and the prompt below updates as you type. Anything you leave blank stays as a placeholder.
The exact name of the component or module
What kind of software this is, in a few words
The size this needs to handle
Tech stack or framework preference
Limits the answer must respect
Your prompt
I need to design {{component_name}} for a {{application_type}}. Context: - Scale: {{scale}} - Existing stack: {{stack}} - Key constraints: {{constraints}} Give me: 1. A high-level design with the main components and how they interact 2. The data model (tables or document schemas) 3. The API surface (endpoints or function signatures) 4. Where the hard problems are and how you'd approach them 5. What you'd defer to a v2