From wicked-garden
Complete solution architecture design with patterns, decisions, and diagrams. Define overall system structure, technology choices, and architectural trade-offs. Use when: "design the architecture", "what's the overall structure", "architecture patterns", "technology stack", "system architecture"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Design end-to-end solutions with clear patterns, decisions, and visual documentation.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Design end-to-end solutions with clear patterns, decisions, and visual documentation.
Move from requirements to implementable architecture through:
Choose architectural style:
Recommend stack based on:
Creates in phases/design/:
design/
├── architecture.md
├── decisions/
│ ├── 001-architecture-style.md
│ └── 002-tech-stack.md
└── diagrams/
└── system-context.mmd
See ADR Template for decision records.
See Architecture Template - Design and Architecture Template - Deployment for full structure.
Auto-engaged during design phase.
Publishes: [arch:design:completed:success]
Architecture informs test strategy:
Track work with ADR links via native TaskCreate:
TaskCreate(
subject="ADR-001",
description="Reference: phases/design/decisions/001.md",
metadata={
"event_type": "task",
"chain_id": "{project}.design",
"source_agent": "solution-architect",
"phase": "design"
}
)
When reviewing changes (not greenfield):
UI → Application → Domain → Infrastructure
Use: Traditional apps, clear separation
API Gateway → Services
Use: Large teams, independent deployment
Producers → Bus → Consumers
Use: Async workflows, loose coupling
See Structural Patterns and Advanced Patterns for detailed examples.
[arch:design:completed:success] - Architecture done[arch:decision:documented:success] - ADR created[arch:diagram:generated:success] - Diagram created