How do I invoke the architecture-patterns skill?

This skill is designed to be loaded by planner and code-reviewer agents via the cc10x-router; it should not be invoked directly by the user.

What is the 'Iron Law' of this skill?

The Iron Law mandates that no architectural design can occur before functionality flows—including user, admin, and system paths—are fully mapped and documented.

Does it support the C4 diagramming model?

Yes, it includes structured templates for C4 Level 1 (System Context), Level 2 (Container), and Level 3 (Component) architectural views.

Can I use this skill for API design?

Yes, it specifically maps user flows to REST/GraphQL endpoints, helping you define request/response schemas and error modes that match real-world usage.

Architecture Patterns & System Design

Name: Architecture Patterns & System Design
Author: romiluz13

byromiluz13

•

API 개발

Enforces a functionality-first architectural design process that maps user flows to robust system components and API structures.

소개

Architecture Patterns provides a rigorous framework for designing software systems based on actual functionality requirements rather than abstract technical patterns. It guides developers through the 'Iron Law' of architecture—mapping user, admin, and system flows into concrete components, data models, and API endpoints before writing code. This skill is essential for planning new features, auditing existing systems for technical debt, and ensuring every architectural decision traces back to a specific user need, effectively preventing over-engineering and complex architectural drift.

주요 기능

C4 model templates for system, container, and component views
API endpoint design directly aligned with functional requirements
Structured decision framework for trade-off analysis
Predefined integration patterns for resilient system design
Functionality-first mapping for user, admin, and system flows
18 GitHub stars

사용 사례

Auditing existing codebases for architectural alignment and technical debt
Designing a new feature's end-to-end system flow and API contract
Documenting complex system integrations and error handling strategies

소개

주요 기능

C4 model templates for system, container, and component views
API endpoint design directly aligned with functional requirements
Structured decision framework for trade-off analysis
Predefined integration patterns for resilient system design
Functionality-first mapping for user, admin, and system flows
18 GitHub stars

사용 사례

Auditing existing codebases for architectural alignment and technical debt
Designing a new feature's end-to-end system flow and API contract
Documenting complex system integrations and error handling strategies