System Design & Architecture Standards
Provides foundational architectural principles, patterns, and standards for building maintainable systems.
Install
mkdir -p .claude/skills/system-design-architecture-standards && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10765" && unzip -o skill.zip -d .claude/skills/system-design-architecture-standards && rm skill.zipInstalls to .claude/skills/system-design-architecture-standards
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Universal architectural standards for building robust, scalable, and maintainable systems.Key capabilities
- →Apply SoC principles
- →Implement SSOT
- →Enforce Fail Fast
- →Design for scalability
How it works
It provides a set of foundational principles and patterns for building reliable, scalable, and maintainable systems.
Inputs & outputs
When to use System Design & Architecture Standards
- →Review system design
- →Apply clean architecture patterns
- →Implement circuit breakers
About this skill
System Design & Architecture Standards
Priority: P0 (FOUNDATIONAL)
Architectural Principles
- SoC: Divide into distinct sections per concern.
- SSOT: One source, reference elsewhere.
- Fail Fast: Fail visibly when errors occur.
- Graceful Degradation: Core functional even if secondary fails.
Modularity & Coupling
- High Cohesion: Related functionality in one module.
- Loose Coupling: Use interfaces for communication.
- DI: Inject dependencies, don't hardcode.
Common Patterns
- Layered: Presentation → Logic → Data.
- Event-Driven: Async communication between decoupled components.
- Clean/Hexagonal: Core logic independent of frameworks.
- Statelessness: Favor stateless for scaling/testing.
Distributed Systems
- CAP: Trade-off Consistency/Availability/Partition tolerance.
- Idempotency: Operations repeatable without side effects.
- Circuit Breaker: Fail fast on failing services.
- Eventual Consistency: Design for async data sync.
Documentation & Evolution
- Design Docs: Write specs before major implementations.
- Versioning: Version APIs/schemas for backward compatibility.
- Extensibility: Use Strategy/Factory for future changes.
When not to use it
- →When building simple, non-distributed applications
- →When project constraints forbid modularity
Limitations
- →Principles require adaptation to specific project needs
How it compares
It focuses on universal architectural standards rather than specific implementation details or framework-specific guides.
Compared to similar skills
System Design & Architecture Standards side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| System Design & Architecture Standards (this skill) | 0 | 6mo | No flags | Advanced |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| architect-review | 109 | 4mo | No flags | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by fierzone
View all by fierzone →You might also like
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.