System design
Use when designing system architecture, APIs, components, or data models - provides a structured design workflow with validation and documentation outputs.From its SKILL.md
npx -y skills add NickCrew/Claude-Cortex --skill system-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.4 KB, 187 tokens by cl100k_base, as published. Nobody here has run it
System Design
Overview
Create clear system, API, component, or data model designs with explicit requirements, constraints, and validation steps.
When to Use
- Designing system architecture or components
- Specifying APIs or data models
- Producing design docs or diagrams
Avoid when:
- You only need implementation tasks (use implementation-workflow)
Quick Reference
| Task | Load reference |
|---|---|
| System design workflow | skills/system-design/references/system.md |
Workflow
- Gather requirements and constraints.
- Load the system design reference.
- Define structure, interfaces, and data flows.
- Validate against constraints and best practices.
- Deliver spec/diagram/code artifacts.
Output
- Design spec or diagram
- Validation notes and follow-ups
Common Mistakes
- Designing without constraints
- Mixing implementation details with spec scope
What ships with it: 1 file
4.9 KB alongside SKILL.md
references/
- system.md4.9 KB