skills.rest
microscaler
microscalerOFFICIAL
Explore all skills by this author →
GitHub

System Design

Translate product requirements into system topologies, ADRs, and Mermaid diagrams.

1|Updated Apr 5, 2026
Search Tags:#architecture#system design#mermaid#adr#topology#diagram#boundary
One-click install
npx skills add https://github.com/microscaler/cylon-skills --skill system-design-microscaler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: System Design
Source: https://github.com/microscaler/cylon-skills/tree/main/skills/system-design
Command: npx skills add https://github.com/microscaler/cylon-skills --skill system-design-microscaler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural planning teams need a method to translate high-level requirements into scalable system topologies, clear integration boundaries, and lightweight diagrams that guide subsequent design work.

Core Features & Use Cases

  • Generate macro-level system topologies and service boundaries from requirements.
  • Produce architectural decisions records (ADRs) and Mermaid diagrams for visualization.
  • Support design validation and boundary refinement across microservice ecosystems.

Quick Start

Analyze the provided requirements to produce a Mermaid topology and an ADR set.

Frequently Asked Questions about System Design

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

FAQPage Schema
How do I translate product requirements into a scalable system topology?▼

To translate product requirements into a scalable system topology, you provide high-level functional needs to generate macro-level service boundaries, data flow models, and integration contracts for microservice ecosystems.

Can I generate Mermaid diagrams for microservice boundaries?▼

Yes, you can generate Mermaid diagrams for microservice boundaries. The process analyzes your requirements to produce visual topology representations that map service decomposition and integration points.

How do I create architectural decision records for system design?▼

You create architectural decision records (ADRs) by submitting your system requirements. The output includes a structured ADR set that documents design guidance and validates boundary refinement decisions.

What is the best way to model data flow across microservices?▼

The best way to model data flow across microservices is by mapping architectural boundaries from high-level requirements. This approach produces integration contracts and visual diagrams that clarify service decomposition.

Does this approach write implementation code for the designed services?▼

No, this approach does not write implementation code. It focuses strictly on macro-level design guidance, producing topology diagrams, boundary definitions, and architectural decision records without generating code.

Do I need predefined integration contracts to design system architecture?▼

No, you do not need predefined integration contracts. You can derive integration contracts and service boundaries directly from high-level product requirements to establish scalable system topologies.

Related Skills

Explore More Software Engineering Skills→
pekralpekral

product-capability

Transform product requirements into engineering specifications with Laravel architectural constraints.

Community
Advanced
matt-fell-aimatt-fell-ai
1

visionary

Converts text-based system descriptions into Mermaid diagram code and architectural sketches.

Community
Intermediate
ghufronbagaskaraghufronbagaskara

architecture-diagram

Generate self-contained HTML files with inline SVG architecture diagrams.

Community
Intermediate
kcenonkcenon
2

performance-review

Identify software performance bottlenecks and provide optimization guidance.

Community
Advanced