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.
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
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
- Distinctive: line 123
When reviewing changes (not greenfield):
- Distinctive: line 158
Start Simple: - Don't over-engineer
≈ “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.
Files
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.mmdOutput 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 → InfrastructureUse: Traditional apps, clear separation
Microservices
API Gateway → ServicesUse: Large teams, independent deployment
Event-Driven
Producers → Bus → ConsumersUse: 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
- Start Simple - Don't over-engineer
- Document Decisions - Future you will thank you
- Show Alternatives - Explain your choices
- Use Diagrams - Visual communication
- 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
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
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.

