system-design

Transform requirements into a navigable system design catalog with EventStorming and Mermaid diagrams.

18|3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Dwsy/agent --skill system-design-dwsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/Dwsy/agent/tree/main/skills/system-design
Command: npx skills add https://github.com/Dwsy/agent --skill system-design-dwsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and planning new systems can be fragmented and error-prone. This skill provides a structured approach that converts requirements and ideas into a navigable design catalog using EventStorming, Mermaid diagrams, and progressive elaboration across five phases: Requirements, Big Picture, Processes, Data/Flows, and Integration.

Core Features & Use Cases

  • EventStorming-based phases to discover domain events, commands, actors, aggregates, and external systems.
  • Mermaid diagram support for big-picture flows, detailed processes, data relationships, state transitions, and interaction sequences.
  • Standardized design catalog structure (docs/design-catalog) that keeps artifacts organized and focused on design rather than implementation.
  • Iterative refinement across phases with non-linear progression to accommodate evolving understanding and hotspots.

Quick Start

Describe your system idea and I will generate a comprehensive design catalog using EventStorming templates.

Frequently Asked Questions about system-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a system design catalog from raw requirements?

To create a system design catalog from raw requirements, describe your system idea and the skill transforms it into a navigable structure using EventStorming, Mermaid diagrams, and progressive elaboration across five phases.

Can I use EventStorming to plan architecture and map domain events?

Yes, you can use EventStorming to plan architecture by discovering domain events, commands, actors, aggregates, and external systems, which are then mapped into Mermaid diagrams for big-picture flows and detailed processes.

Does this system design approach generate Mermaid diagrams for processes and data flows?

Yes, this system design approach generates Mermaid diagrams for big-picture flows, detailed processes, data relationships, state transitions, and interaction sequences without including implementation details.

What is the best way to structure architecture planning across different project sizes?

The best way to structure architecture planning across project sizes is using a standardized design catalog structure with iterative refinement across phases, accommodating evolving understanding and hotspots through non-linear progression.

Do I need to provide implementation details for technology selection discussions?

No, you do not need to provide implementation details for technology selection discussions, as the skill focuses purely on design artifacts and yields phase outputs like requirements, big picture, processes, data flows, and integration.

How does progressive elaboration work for conceptual design tasks?

Progressive elaboration for conceptual design tasks works by iteratively refining understanding across five phases—Requirements, Big Picture, Processes, Data/Flows, and Integration—allowing non-linear progression to address hotspots as they emerge.