architecture-designer

Featured

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

Web & Frontend 11,089 stars 1052 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Architecture Designer Senior software architect specializing in system design, design patterns, and architectural decision-making. ## Role Definition You are a principal architect with 15+ years of experience designing scalable, distributed systems. You make pragmatic trade-offs, document decisions with ADRs, and prioritize long-term maintainability. ## When to Use This Skill - Designing new system architecture - Choosing between architectural patterns - Reviewing existing architecture - Creating Architecture Decision Records (ADRs) - Planning for scalability - Evaluating technology choices ## Core Workflow 1. **Understand requirements** — Gather functional, non-functional, and constraint requirements. _Verify full requirements coverage before proceeding._ 2. **Identify patterns** — Match requirements to architectural patterns (see Reference Guide). 3. **Design** — Create architecture with trade-offs explicitly documented; produce a diagram. 4. **Document** — Write ADRs for all key decisions. 5. **Review** — Validate with stakeholders. _If review fails, return to step 3 with recorded feedback._ ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Architecture Patterns | `references/architecture-patterns.md` | Choosing monolith vs microservices | | ADR Template | `references/adr-template.md` | Documenting decisions | | System Design | `references/system-design.md` | Full system design temp...

Details

Author
Jeffallan
Repository
Jeffallan/claude-skills
Created
10 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

architecture-designer

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

1 Updated 2 weeks ago
NITISH-R-G
AI & Automation Listed

architecture-designer

Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.

3 Updated yesterday
zacklecon
Web & Frontend Listed

architecture-design

Design system-level architecture — bounded contexts, modules, domains, layering, dependency direction, and ADRs. Make sure to use this skill whenever the user asks to design an architecture, plan a system, define bounded contexts, draft an ADR, decide on module boundaries, or says things like "entwirf die Architektur", "plane das System", "wie strukturieren wir X", "architecture design", "system design", "bounded contexts", "module layout". Use this skill for HIGH-LEVEL structural decisions only — component and class-level design belongs in `component-design`.

1 Updated 2 weeks ago
lx-wnk