system-design
Design System Architecture Catalogs
Unclear requirements can lead to premature implementation and missing architecture decisions. This skill guides structured discovery and creates Mermaid-based design catalogs for shared planning.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "system-design" from https://skillstore.io/skills/dwsy-system-design.md and its manifest at https://skillstore.io/api/skills/dwsy-system-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "system-design". Design an appointment booking platform for clinics.
Expected outcome:
A design catalog with requirements, a big-picture EventStorming timeline, booking and cancellation process diagrams, conceptual patient and appointment entities, and key scheduling hotspots.
Using "system-design". Help our team align on a marketplace architecture before coding.
Expected outcome:
A shared catalog that shows buyer and seller events, payment and fulfillment integrations, core entity relationships, order state transitions, and questions that need decisions.
Using "system-design". Turn our requirements notes into architecture artifacts.
Expected outcome:
Structured requirements, Mermaid diagrams for critical flows, a navigation README, and a focused list of unresolved design choices.
Security Audit
SafeAll static findings are false positives caused by Markdown formatting, Mermaid examples, paths, and ordinary system-design terminology. I found no evidence of command execution, host reconnaissance, prompt injection, credential access, or malicious intent in SKILL.md.
Risk Factors
⚙️ External commands (41)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dwsy-system-design/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dwsy-system-design?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dwsy-system-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dwsy-system-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dwsy-system-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dwsy. (2026). system-design security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dwsy-system-design/audits/7BibTeX citation
@techreport{dwsy-dwsy-system-design-2026,
author = {Dwsy},
title = {system-design security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/dwsy-system-design/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "system-design security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "Dwsy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dwsy-system-design/audits/7"
identifiers:
- type: other
value: "skillstore:dwsy-system-design:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
dwsy-system-design
2026-08-21
aaronabuusama-system-design
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a New Product System
Turn an early product idea into requirements, event flows, and architecture diagrams before implementation starts.
Align Engineering Teams
Create a shared design catalog that captures business events, process boundaries, and open architectural hotspots.
Prepare Implementation Planning
Build conceptual artifacts that can feed later task planning without locking in code or deployment details too early.
Try These Prompts
Use the system-design skill to help me design a system for this idea: [describe the product]. Ask me the first requirements question.
Use EventStorming to identify commands, events, actors, external systems, and hotspots for [system]. Build the big-picture Mermaid diagram.
Review the big-picture design and choose the 2 to 4 most critical processes. For each one, create a Mermaid process diagram and validate it with me.
Complete the system design catalog with requirements, big-picture events, process diagrams, conceptual data models, state charts, sequence diagrams, and an embedded README.
Best Practices
- Answer the discovery questions with real constraints, user roles, and success criteria.
- Review each phase before moving forward so downstream diagrams stay accurate.
- Use hotspots for uncertain decisions instead of forcing premature technology choices.
Avoid
- Skipping questions and asking for a complete architecture from vague requirements.
- Using the skill to write production code, deployment plans, or database migrations.
- Trying to diagram every possible workflow instead of focusing on critical flows.