system-design

Coordinate architectural design decisions across C4, PlantUML, DDD, NFR, and ADR modeling skills.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Tirael/cursor-template --skill system-design-tirael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/Tirael/cursor-template/tree/main/.cursor/skills/system-design
Command: npx skills add https://github.com/Tirael/cursor-template --skill system-design-tirael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates architectural design decisions across multiple modeling skills to ensure consistent usage of C4, PlantUML, DDD, NFR, ADR, and integration patterns.

Core Features & Use Cases

  • Orchestrates selecting the right skills for architectural tasks (C4 levels, DDD, NFR, ADR, integrations)
  • Defines canonical paths and recommended order of work to ensure consistent delivery
  • Guides startup activities: how to apply skills when starting a new system or module
  • Provides a structured playbook mapping tasks to skills

Quick Start

Define the system context and select the required skills for your architecture task.

Frequently Asked Questions about system-design

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

FAQPage Schema
How do I coordinate architectural design decisions across multiple modeling tools?

This system-design coordination applies a structured playbook mapping tasks to skills, enforcing a canonical workflow with guardrails to guide teams from context gathering to final architectural decisions.

What's the best way to apply C4 modeling and DDD when starting a new software module?

Define the system context first, then select the required skills for your architecture task, following the canonical paths and recommended order of work to ensure consistent delivery from startup activities onward.

How does architecture governance work with NFR design and ADR integration?

Architecture governance works by enforcing a defined workflow with canonical paths and guardrails, ensuring that NFR design and ADR integration are applied consistently across all architectural decisions.

Can I use this approach to scope project tool selection for integration patterns?

Yes, you can use it for project scoping and tool selection, applying it to choose the right architectural skills for C4 levels, DDD, NFR, ADR, and integration patterns based on your specific task.

Do I need prior architecture context before selecting C4, PlantUML, or DDD skills?

You need to define the system context and select the required skills for your architecture task before applying the structured playbook that maps specific architectural tasks to their corresponding modeling skills.