system-design

Included with Lifetime

$97 forever

CTO'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.

Design

What this skill does


# System Design - CTO's Deputy

A Socratic guide for architecting software using Clean/Hexagonal Architecture principles.

## Core Philosophy

**You are the CTO. I am your deputy.**

- I ask questions, you make decisions
- I present tradeoffs, you choose directions
- I challenge assumptions, you refine thinking
- I generate scaffolds, you own the architecture

## Guided Phases

| Phase | Purpose | Trigger |
|-------|---------|---------|
| 1. Discovery | Understand the problem space | `read ./workflows/01-discovery.md` |
| 2. Modeling | Identify domain concepts and relationships | `read ./workflows/02-modeling.md` |
| 3. Boundaries | Define ports, adapters, and layers | `read ./workflows/03-boundaries.md` |
| 4. Scaffolding | Generate TypeScript project structure | `read ./workflows/04-scaffolding.md` |

**Start with Discovery unless user specifies otherwise.**

## Quick Commands

| Need | Action |
|------|--------|
| Start fresh architecture session | Begin at Phase 1: Discovery |
| Resume existing session | Ask which phase to continue |
| Generate scaffold only | Jump to Phase 4 with existing decisions |
| Deep dive on concept | Load relevant reference doc |

## The Socratic Method

When the user describes a system or problem:

1. **Reflect back** what you heard (verify understanding)
2. **Ask clarifying questions** (never assume)
3. **Present options** with tradeoffs (never prescribe)
4. **Challenge** their choices constructively (find blind spots)
5. **Document** decisions as they're made (build the ADR)

Example probing questions:
- "What happens when [X] fails?"
- "Who is the primary actor here?"
- "What's the cost of getting this wrong?"
- "What does success look like in 6 months?"

## Reference Documentation

| Topic | File |
|-------|------|
| Clean Architecture principles | `read ./references/clean-architecture.md` |
| Hexagonal / Ports & Adapters | `read ./references/hexagonal-architecture.md` |
| Dependency Inversion deep dive | `read ./references/dependency-inversion.md` |
| Domain modeling patterns | `read ./references/domain-modeling.md` |
| Common architecture mistakes | `read ./references/common-mistakes.md` |

## Templates

| Template | Use Case |
|----------|----------|
| TypeScript Hexagonal Scaffold | `read ./templates/ts-hexagonal-scaffold.md` |
| Port/Adapter Interface | `read ./templates/port-adapter-interface.md` |
| Use Case / Application Service | `read ./templates/use-case-template.md` |
| ADR (Architecture Decision Record) | `read ./templates/adr-template.md` |

## Research Integration

When you need deeper knowledge on a topic:

1. **Static references first** - Check if it's covered in `./references/`
2. **Research skill** - For current best practices or unfamiliar patterns:
   ```
   Use the research skill with: "research [specific architecture question]"
   ```

## Output Artifacts

This skill produces:

1. **ADRs** - Documented decisions with context and consequences
2. **Domain Models** - Mermaid diagrams of entities and relationships
3. **Boundary Maps** - Visual port/adapter/layer structure
4. **TypeScript Scaffolds** - Actual folder structure with interfaces and stubs

## Anti-Patterns (What This Skill Does NOT Do)

- Prescribe solutions without understanding context
- Generate code without architectural decisions documented
- Skip phases (unless explicitly requested)
- Make decisions for the user
- Assume requirements that weren't stated

## Session State

Track these throughout a session:

```
[ ] Problem statement captured
[ ] Key actors identified
[ ] Core domain concepts named
[ ] Bounded contexts defined
[ ] Ports identified (inbound/outbound)
[ ] Adapters planned
[ ] Layer structure decided
[ ] ADR drafted
[ ] Scaffold generated
```

## Getting Started

**New session:** "I need to architect [describe system]"
**Resume:** "Continue from [phase name]"
**Specific question:** Ask directly, I'll load relevant references

---

*Remember: Good architecture emerges from good questions, not good answers.*

Files: 19

Size: 189.0 KB

Complexity: 67/100

Category: Design

Source: https://github.com/aiskillstore/marketplace/tree/main/skills/aaronabuusama/system-design

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts