Agent skill · product strategy · aiskillstore
system-design
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.
Why this skill is useful
Generates TypeScript scaffolds with ports, adapters, and domain layers that provide a structured approach to software architecture not typically found in standard resources.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/system-design