skills.rest
bRRRITSCOLD
bRRRITSCOLDCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Design and review software architecture with C4 diagrams and ADRs.

2|Updated Jun 26, 2026
Search Tags:#architecture#software design#DDD#ADR#non-functional requirements#C4 diagrams
One-click install
npx skills add https://github.com/bRRRITSCOLD/compainy --skill architecture-brrritscold
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/bRRRITSCOLD/compainy/tree/main/skills/architecture
Command: npx skills add https://github.com/bRRRITSCOLD/compainy --skill architecture-brrritscold

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides structured guidance for engineers and architects to design, implement, and maintain robust software systems. It helps in defining architecture, choosing technologies, and adhering to best practices.

Core Features & Use Cases

  • Define Boundaries: Establish clear service and bounded-context boundaries for modular systems.
  • Communicate Architecture: Utilize C4 diagrams for effective communication and documentation.
  • Record Decisions: Capture architectural decisions as ADRs for traceability and team alignment.
  • Non-Functional Requirements: Ensure system design is driven by performance, security, and scalability needs.
  • Technology Selection: Evaluate and choose technologies with explicit trade-offs.
  • Evolutionary Architecture: Design for change and maintain flexibility over time.

Quick Start

Invoke the architecture skill to design a new system and follow the step-by-step process outlined in the SKILL.md guide.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I design software architecture using bounded contexts and DDD?▼

C4 diagrams communicate software architecture through structured visual contexts, containers, components, and code levels. They provide effective documentation for team alignment and system understanding without overwhelming technical details.

What is an ADR and when should I record architectural decisions?▼

An ADR, or Architecture Decision Record, captures architectural decisions for traceability and team alignment. You should record decisions whenever making significant technology selections or structural changes to maintain clear documentation.

How do non-functional requirements drive system design and technology selection?▼

Non-functional requirements drive system design by enforcing performance, security, and scalability constraints. They guide technology selection by providing explicit trade-off evaluation criteria, ensuring the chosen stack meets operational demands.

Do I need to understand SOLID and KISS principles to review software architecture?▼

Yes, reviewing software architecture requires understanding SOLID and KISS principles to evaluate structural integrity and simplicity. These foundational principles ensure the system design adheres to maintainability and evolutionary flexibility standards.

What is the best way to define service boundaries for modular systems?▼

The best way to define service boundaries is by applying bounded contexts from Domain-Driven Design. This establishes clear logical separations between domain areas, ensuring modular systems remain scalable and independently deployable.

Related Skills

Explore More Software Engineering Skills→
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate
williamzujkowskiwilliamzujkowski
6

Architecture Decision Framework

Generate ADRs, MADRs, Y-statements, and C4 diagrams from requirements.

Community
Advanced
hidonguyenhidonguyen

ck:ask

Analyze system designs and recommend technology stacks with trade-offs.

Community
Advanced
tianjianjiangtianjianjiang
1

smith-principles

Apply DRY, KISS, YAGNI, SOLID, and HHH principles to code reviews and refactoring.

Community
Intermediate