mikeparcewski/wicked-garden-engineering-system-design
skills/engineering/system-design/SKILL.md
Use when decomposing a system into components with clear boundaries, module organization, and interface contracts — the "how do we slice this?" question at design time. NOT for reviewing an existing system's health (use the architecture skill or engineering:arch).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-engineering-system-designInstall 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:07 AM98.6s18 files scanned
SKILL.md
- name:
- wicked-garden-engineering-system-design
- description:
- |
- NOT for reviewing an existing system's health (use the architecture skill or engineering:
- arch).
- portability:
- portable
- phase_relevance:
- ["design", "build"]
- archetype_relevance:
- ["*"]
System Design Skill
Decompose systems into well-defined components with clear boundaries and interfaces.
Purpose
Transform architecture into concrete components:
- Component identification and boundaries
- Interface definition
- Dependency management
- Module organization
Process
1. Identify Components
Ask:
- What are major capabilities?
- What changes together?
- What has different scaling needs?
- What domain concepts exist?
2. Define Boundaries
Apply:
- High Cohesion - Related functionality together
- Low Coupling - Minimal dependencies
- Single Responsibility - One reason to change
- Information Hiding - Encapsulate internals
3. Design Interfaces
For each component:
- Public API (what it exposes)
- Dependencies (what it needs)
- Events (what it publishes/subscribes)
- Data contracts (I/O structures)
4. Document
Creates in phases/design/:
design/
├── components/
│ ├── overview.md
│ ├── auth-component.md
│ └── dependencies.mmd
└── interfaces/
└── component-api.md
Component Patterns
Layered - Presentation → Application → Domain → Infrastructure Hexagonal - Business logic with adapter ports Plugin - Core system with pluggable extensions
See component patterns in refs/ (patterns-layered-pattern.md, patterns-facade-pattern.md).
Dependency Management
Rules
- Acyclic - No circular dependencies
- Unidirectional - Dependencies flow one way
- Stable - Depend on stable abstractions
- Explicit - Declare in constructor/config
Common Anti-Patterns
God Object - One component does everything Fix: Split by responsibility
Feature Envy - Component uses another's data extensively Fix: Move functionality to data owner
Circular Dependencies - A depends on B, B depends on A Fix: Extract shared logic or use events
Leaky Abstraction - Internal details exposed Fix: Refine public interface
See dependency guides in refs/ (dependencies-dependency-principles.md, dependencies-best-practices.md).
Integration
With Architecture Skill
Implements high-level architecture:
- Takes architectural decisions
- Maps to concrete components
- Validates feasibility
With Integration Skill
Provides boundaries for:
- API design
- Service contracts
- Event schemas
With wicked-crew
Called during design phase after architecture.
Events
[arch:components:defined:success]- Components designed[arch:interface:defined:success]- Interface documented[arch:dependency:analyzed:success]- Dependencies validated
Tips
- Start with Boundaries - Define what's in/out first
- Think in Interfaces - Design API before implementation
- Keep It Simple - Don't over-decompose
- Test Boundaries - Use contract tests
- Refactor Gradually - Small, safe steps
- Document Dependencies - Make them explicit
Reference Materials
- Component Template:
- Structure & API
- Lifecycle & Deployment
- Maintenance & Examples
- Interface Template:
- Structure & Contracts
- Testing & Operations
- Examples & Tips
- Component Patterns:
- Layered
- Plugin Architecture
- Facade
- Dependency Injection
- Dependencies:
- Principles
- Tracking
- Best Practices
- Anti-Patterns:
- God Object
- Big Ball of Mud
- Circular Dependencies
- Feature Envy
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