Agent skill · product strategy · aiskillstore
system-design
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
Why this skill is useful
Provides structured templates and methodologies for system design that the AI wouldn't generate reliably on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
执行环境 路径类型 说明 --------- ------ 使用方式 此技能提供模板和指导，无需本地脚本执行 调用场景 当用户需要系统设计、架构文档、技术选型时自动激活 输出位置 docs/design-catalog/ 目录（相对于项目根目录） 路径说明 无本地脚本依赖：此技能生成文档模板，不涉及本地脚本执行 生成的目录：保存在执行命令时的当前目录下的 docs/design-catalog/ 项目上下文：基于当前工作目录确定项目根目录 System Design Through EventStorming Overview Transform requirements into navigable design catalogs using EventStorming methodology and Mermaid diagrams. Core principle: Progressive elaboration through event-driven thinking, producing token-efficient visual artifacts in standardized catalog structure. Announce at start: "I'm using the system-design skill to create a design catalog for your system." When to Use Use when: User wants to design a new system Requirements exist but design doesn't Need structured thinking before implementation Team needs shared visual artifacts Don't use when: Adding features to existing system (consider brainstorming instead) Implementation already started User wants code, not design Quick Reference Phase Key Activities Output Files ------- --------------- ------------- 1. Requirements Ask questions, identify actors/constraints requirements.md 2. Big Picture EventStorming timeline with events/commands big-picture.mmd 3. Processes Zoom into critical processes, add aggregates process-{name}.mmd 4. Data & Flows ERD, state charts, sequences erd.mmd, state-{entity}.mmd, sequence-{flow}.mmd 5. Integration Generate catalog README README.md The Iron Laws Law 1: ASK QUESTIONS - No Assumptions NEVER make "industry-standard assumptions" without asking the user first. Ask about actors, constraints, scale, budget, timeline Use AskUserQuestion tool for architectural choices Mark unclear areas as hotspots instead of assuming Bad: Good: Law 2: MERMAID ONLY - No ASCII Diagrams All diagrams MUST use Mermaid format. NO exceptions. No ASCII art No text-based diagrams No "version control friendly" excuses for avoiding Mermaid Bad: Good: Law 3: EVENTSTORMING - Event-Driven Thinking Use EventStorming methodology for Phases 2-3. Required. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/system-design--29e953