mikeparcewski/wicked-garden-engineering-backend
skills/engineering/backend/SKILL.md
Backend engineering specialist for APIs, databases, server-side patterns, data modeling, scalability, and integrations. Use when: "design an API", "database schema", "how to handle auth", "backend performance", "REST endpoint", "query optimization", "server-side architecture"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-engineering-backendInstall 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 AM27.3s3 files scanned
SKILL.md
- name:
- wicked-garden-engineering-backend
- description:
- |
- Use when:
- design an API", "database schema", "how to handle auth",
- portability:
- portable
- phase_relevance:
- ["design", "build"]
- archetype_relevance:
- ["*"]
Backend Skill
Specialized backend engineering guidance for APIs, databases, and server-side systems.
When to Use
- Designing APIs (REST, GraphQL)
- Database schema or query questions
- Server-side architecture
- Data modeling
- Authentication and authorization
- Scalability and performance
- User says "backend", "API", "database", "server"
Key Focus Areas
API Design
- RESTful conventions (resources, methods, status codes)
- GraphQL schema design
- API versioning strategies
- Request/response validation
- Error handling and messaging
- Pagination and filtering
- Rate limiting
Database Patterns
- Schema design and normalization
- Indexing strategies
- Query optimization
- Transaction management
- Connection pooling
- Migration best practices
- N+1 query prevention
Data Modeling
- Entity definition
- Relationship modeling (1:1, 1:N, N:M)
- Data types and constraints
- Validation rules
- Audit trails
Authentication & Authorization
- Password hashing (bcrypt, argon2)
- JWT or session management
- OAuth2 / OIDC patterns
- RBAC (Role-Based Access Control)
- API key management
Performance & Scalability
- Query optimization and EXPLAIN plans
- Caching strategies (Redis, memcached)
- Background jobs (Celery, Bull)
- Database read replicas
- Horizontal scaling
Integration Patterns
- External API resilience (retry, timeout, circuit breaker)
- Webhook handling with retry
- Message queue patterns
- Idempotency for critical operations
Review Process
Use comprehensive checklists for:
- API quality (REST conventions, validation, versioning)
- Database quality (schema, indexes, transactions)
- Security (auth, validation, injection prevention)
See refs/checklists.md for detailed checklists, anti-patterns, and output templates.
Code Patterns
Common backend patterns for:
- API endpoints with auth and validation
- Query optimization and N+1 prevention
- Authentication and authorization
- External API integration with resilience
- Caching strategies
See refs/patterns.md for code examples and best practices.
Notes
- Always hash passwords (never plaintext)
- Validate all input at API boundaries
- Use transactions for multi-step operations
- Index foreign keys and query fields
- Use background jobs for slow operations
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