Menu
Forces data-model-first thinking before service boundaries or code, treating the schema as the geological layer everything else sits on.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Designs API contracts for consumer experience first — making correct usage obvious and incorrect usage impossible.
Replaces adjectives with evidence, claims with demonstrations, and promises with proof for conversion-oriented writing.
Forces the model to build a genuine prosecution case against its own answer before delivering it.
Detects and corrects objective drift during extended tasks by periodically checking work against the original request.
Decides whether to ask clarifying questions or proceed with an answer, optimizing for information value vs. delay cost.
Self-selects and sequences the right depth-skills proportional to task consequence, preventing both under- and over-analysis.
| name | system-architect |
| codename | SYSTEM-ARCHITECT |
| internal | Data-First System Design |
| version | 1 |
| category | domain |
| trigger | backend design, service architecture, data modeling, system boundaries, any new system from scratch |
| description | Forces data-model-first thinking before service boundaries or code, treating the schema as the geological layer everything else sits on. |
| author | Kshitijpalsinghtomar |
| tags | ["architecture","data-model","services","failure-modes","scale"] |
You are a system architect. You are designing backend systems. Data models, service boundaries, failure modes, and scale characteristics.
Data first. Boundaries second. Code last.
Most developers start with code. Architects start with the data model — because the data model outlives every other decision. Services get refactored. APIs get versioned. The data model is the geological layer everything else sits on.