aiskillstore/marketplace / skills/aaronabuusama/system-design
system-design
VerifiedCTO's deputy for software architecture using Clean/Hexagonal Architecture principles. Socratic approach - asks probing questions to help YOU make informed design decisions. Guides through Discovery → Modeling → Boundaries → Scaffolding phases. Outputs TypeScript scaffolds with ports, adapters, and domain layers. USE WHEN user says 'architect', 'system design', 'hexagonal', 'clean architecture', 'ports and adapters', 'design this system', 'structure this project', or needs help thinking through complex software structure.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| references/clean-architecture.md | markdown | 6.6 KB |
| references/common-mistakes.md | markdown | 8.4 KB |
| references/dependency-inversion.md | markdown | 7.1 KB |
| references/domain-modeling.md | markdown | 6.9 KB |
| references/hexagonal-architecture.md | markdown | 7.5 KB |
| skill-report.json | config | 159.4 KB |
| templates/adr-template.md | markdown | 6.2 KB |
| templates/controller-template.md | markdown | 10.2 KB |
| templates/entity-template.md | markdown | 8.5 KB |
| templates/port-adapter-interface.md | markdown | 7.8 KB |
| templates/repository-template.md | markdown | 10.0 KB |
| templates/ts-hexagonal-scaffold.md | markdown | 5.9 KB |
| templates/use-case-template.md | markdown | 8.5 KB |
| templates/value-object-template.md | markdown | 9.0 KB |
| workflows/01-discovery.md | markdown | 2.4 KB |
| workflows/02-modeling.md | markdown | 3.3 KB |
| workflows/03-boundaries.md | markdown | 5.8 KB |
| workflows/04-scaffolding.md | markdown | 5.2 KB |
workflows/01-discovery.md
View on GitHub# Phase 1: Discovery
**Goal:** Understand the problem space before proposing any solutions.
## Entry Questions
Start every discovery with these questions. Do not proceed until answered:
### 1. The Problem
- "What problem are you trying to solve?"
- "Who experiences this problem? How painful is it?"
- "What happens if this doesn't get built?"
### 2. The Actors
- "Who/what interacts with this system?"
- "Which of these are humans vs other systems?"
- "Who is the PRIMARY user? (there can only be one)"
### 3. The Constraints
- "What technical constraints exist?" (existing systems, team skills, budget)
- "What are the non-negotiables?"
- "What's the timeline pressure?"
### 4. Success Criteria
- "What does success look like in 3 months? 12 months?"
- "How will you know if the architecture is working?"
- "What would make you regret this design?"
## Probing Deeper
Once basics are answered, challenge assumptions:
| If they say... | Ask... |
|----------------|--------|
| "Users need to..." | "How do you know? Have you validated this?" |
| "It must be real-time" | "What's the actual latency requirement in ms?" |
| "We need microservices" | "What problem does that solve that a monolith doesn't?" |
| "It should be scalable" | "To what scale? What's your current/projected load?" |
| "Keep it simple" | "Simple for whom? Users? Developers? Operators?" |
## Red Flags to Surface
Watch for and explicitly call out:
- **Vague requirements** - "flexible", "scalable", "modern"
- **Solution-first thinking** - jumping to tech before understanding problem
- **Missing actors** - who maintains it? who pays for it?
- **Assumed constraints** - "we have to use X" (really?)
- **No failure modes discussed** - what happens when things go wrong?
## Discovery Outputs
Before moving to Phase 2, you should have:
```markdown
## Problem Statement
[1-2 sentences capturing the core problem]
## Primary Actor
[Who is this system primarily serving?]
## Secondary Actors
- [List other actors]
## Key Constraints
- [Non-negotiables]
- [Technical constraints]
- [Timeline/resource constraints]
## Success Criteria
- [Measurable outcomes]
## Open Questions
- [Things still unclear that need research/validation]
```
## Transition to Phase 2
When discovery is complete:
1. Summarize what you've learned back to the user
2. Confirm they agree with the summary
3. Ask: "Ready to start modeling the domain?"
Then: `read ./workflows/02-modeling.md`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |