agentleFS
mikeparcewskimikeparcewski/wicked-garden/skills/engineering/architecture/SKILL.md

wicked-garden-engineering-architecture

Skill9 starsChanged 7 months agoMITView on GitHub

Complete solution architecture design with patterns, decisions, and diagrams. Define overall system structure, technology choices, and architectural trade-offs.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When reviewing changes (not greenfield):

    line 123
  2. Distinctive:

    Start Simple: - Don't over-engineer

    line 158

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Architecture Skill

Design end-to-end solutions with clear patterns, decisions, and visual documentation.

For genuinely structural greenfield design (system boundaries, cross-cutting design trade-offs, full ADR sets), hand off to the wicked-garden-engineering-solution-architect worker skill.

Purpose

Move from requirements to implementable architecture through:

  • Pattern selection and justification
  • Technology stack decisions
  • Cross-cutting concern planning
  • Architectural Decision Records (ADRs)

Process

1. Gather Context

  • Read outcome document
  • Analyze requirements
  • Identify constraints
  • Understand scale needs

2. Select Patterns

Choose architectural style:

  • Monolithic - Simple deployment, single codebase
  • Microservices - Independent scaling, team autonomy
  • Serverless - Event-driven, auto-scaling
  • Event-Driven - Loose coupling, async
  • Layered - Clear separation, traditional

3. Make Decisions

Recommend stack based on:

  • Requirements fit
  • Team expertise
  • Ecosystem maturity
  • Cost considerations

4. Document

Creates in phases/design/:

design/
├── architecture.md
├── decisions/
│   ├── 001-architecture-style.md
│   └── 002-tech-stack.md
└── diagrams/
    └── system-context.mmd

Output Format

See ADR Template for decision records.

See Architecture Template - Design and Architecture Template - Deployment for full structure.

Integration

With wicked-crew

Auto-engaged during design phase.

Publishes: [arch:design:completed:success]

With qe

Architecture informs test strategy:

  • Critical paths
  • Failure modes
  • Performance targets

With the harness's task list

Track work with ADR links as tasks — subject ADR-001, description Reference: phases/design/decisions/001.md, metadata event_type: task, chain_id: {project}.design, source_agent: solution-architect, phase: design; the field list and the harness-specific Hand-off live in the wicked-garden-workflow skill's refs/integration.md.

Architectural Thinking

Balance Trade-offs

  • Simplicity vs Flexibility - Easy now vs extensible later
  • Performance vs Maintainability - Fast vs readable
  • Coupling vs Duplication - DRY vs independent
  • Build vs Buy - Control vs speed

Apply Principles

  • SOLID - Single responsibility, dependency inversion
  • YAGNI - Build for now, not speculation
  • Separation of Concerns - Clear boundaries

Consider NFRs

  • Scalability - Users, growth rate
  • Security - Threats, compliance
  • Performance - Latency, throughput
  • Reliability - Uptime, DR
  • Maintainability - Team, skillset

Detect Scope Creep

When reviewing changes (not greenfield):

  • Flag unauthorized architectural changes (new boundaries, changed patterns)
  • Flag "while I'm here" improvements beyond the task scope
  • Flag components restructured beyond what was requested

Common Patterns

Layered

UI → Application → Domain → Infrastructure

Use: Traditional apps, clear separation

Microservices

API Gateway → Services

Use: Large teams, independent deployment

Event-Driven

Producers → Bus → Consumers

Use: Async workflows, loose coupling

See Structural Patterns and Advanced Patterns for detailed examples.

Events

  • [arch:design:completed:success] - Architecture done
  • [arch:decision:documented:success] - ADR created
  • [arch:diagram:generated:success] - Diagram created

Tips

  1. Start Simple - Don't over-engineer
  2. Document Decisions - Future you will thank you
  3. Show Alternatives - Explain your choices
  4. Use Diagrams - Visual communication
  5. Make it Scannable - Quick understanding

Reference Materials

  • ADR Template
  • Architecture Template - Design
  • Architecture Template - Deployment
  • Structural Patterns
  • Advanced Patterns
  • Example ADRs:
    • E-Commerce & Analytics
    • SaaS & Trading

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.