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.

Your prompt

5 placeholders left
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

Similar prompts

Break a God Function Apart

Split an oversized function into well-named pieces without changing external behavior.

Design a Database Schema

CREATE TABLE statements with constraints, indexes, and the reasoning behind each choice.

Design a REST API

Endpoint-by-endpoint design including the error responses most API specs forget.

Explore Before You Plan

Make the agent read and explain a subsystem before it touches a single line of it.