mikeparcewski/wicked-garden-engineering-architecture
skills/engineering/architecture/SKILL.md
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"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-engineering-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 12, 2026, 7:06 AM32.4s8 files scanned
SKILL.md
- name:
- wicked-garden-engineering-architecture
- description:
- |
- Use when:
- design the architecture", "what's the overall structure",
- portability:
- portable
- phase_relevance:
- ["design", "build"]
- archetype_relevance:
- ["*"]
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), dispatch the
wicked-garden-engineering-solution-architect fork 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 native tasks
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"
}
)
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
- 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
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026