design-system

Define software system components, contracts, and Mermaid architecture diagrams.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill design-system-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/arquitectura/design-system
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill design-system-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of designing robust and maintainable software architectures by providing a structured approach to defining components, their interactions, and key design decisions.

Core Features & Use Cases

  • Component Definition: Clearly outlines responsibilities, inputs, and outputs for each system component.
  • Diagram Generation: Creates visual representations of system architecture using Mermaid for components and sequences.
  • Contract Specification: Defines precise interfaces and communication protocols between modules.
  • Design Decision Rationale: Documents and justifies architectural choices, including pattern selection and alternatives considered.
  • Use Case: When starting a new microservice, use this Skill to define its boundaries, its API contract with other services, and document the chosen communication pattern (e.g., REST vs. gRPC vs. message queue).

Quick Start

Use the design-system skill to architect a new user authentication service, including component diagrams and API contracts.

Frequently Asked Questions about design-system

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

FAQPage Schema
How do I design software system architecture for a new microservice?

To design software system architecture for a new microservice, you define component boundaries, generate visual diagrams, and specify inter-module contracts. This approach outlines responsibilities, inputs, outputs, and communication protocols for each system component.

What is the best way to document architectural design decisions and rationale?

Documenting architectural design decisions involves recording and justifying pattern selections alongside alternatives considered. This ensures non-obvious design choices are transparent and maintainable when defining component interactions and system architecture.

How do I create component diagrams and sequence diagrams for system design?

You create component diagrams and sequence diagrams for system design by generating visual representations using Mermaid. These diagrams map out system architecture and component interactions to provide clear visual clarity.

Does system design require adherence to SOLID principles for module refactoring?

Yes, system design requires adherence to SOLID principles for module refactoring. Applying SOLID principles ensures robust and maintainable software architectures when defining component responsibilities and specifying inter-module contracts.

Can I define API contracts and communication protocols between modules during an architectural review?

Yes, you can define API contracts and communication protocols between modules during an architectural review. Contract specification defines precise interfaces for communication, such as choosing between REST, gRPC, or message queues.