Skip to content

mikeparcewski/wicked-garden / skills/engineering

wicked-garden-engineering

Verified

Engineering domain skill: code review, architecture analysis, debugging, implementation planning, documentation, release PRs and scaffolds. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" / "evaluate component boundaries, coupling, or layer violations" (--scope module|service|system); "debug this error / bug / unexpected behavior" (root cause, reproduction, fix, prevention); "plan this change" / "implementation plan with file changes, risks and tests before writing code"; "generate API docs / README / guide / inline comments" (--type api|readme|guide|inline) or "docs drifted from code"; "prepare a release PR" (never tags or publishes); "scaffold a new CLI / service / library". NOT for reviewing an AI agent system (agentic review), a UI (product ux-review), a go/no-go verdict (archetype review), greenfield design (the solution-architect worker) or scaffolding a new MCP server (wicked-garden-mcp-scaffold).

FileKindSize
SKILL.mdskill md12.7 KB
refs/arch.mdmarkdown4.5 KB
refs/conformance.mdmarkdown3.8 KB
refs/debug.mdmarkdown4.0 KB
refs/docs.mdmarkdown5.8 KB
refs/engineering-checklists.mdmarkdown2.7 KB
refs/engineering-templates.mdmarkdown1.2 KB
refs/plan.mdmarkdown4.1 KB
refs/release.mdmarkdown7.4 KB
refs/review.mdmarkdown7.4 KB
refs/scaffold.mdmarkdown5.6 KB

refs/engineering-templates.md

View on GitHub
---
phase_relevance: ["design", "build"]
archetype_relevance: ["*"]
---
# Engineering Output Templates

## Implementation Guidance Template

```markdown
## Implementation Plan: {Feature}

### Approach
{High-level strategy}

### Steps
1. {Step with rationale}
2. {Step with rationale}

### Key Patterns
- {Pattern and why it fits}

### Considerations
- {Important notes or tradeoffs}
```

## Code Review Template

```markdown
## Engineering Review

### Strengths
- {Good practices observed}

### Issues
| Severity | Issue | Location | Fix |
|----------|-------|----------|-----|
| HIGH/MEDIUM/LOW | {Description} | file:line | {Recommendation} |

### Recommendations
1. {Priority item}
2. {Secondary item}
```

## Key Focus Areas

### Code Quality
- Clear naming and organization
- DRY (Don't Repeat Yourself)
- SOLID principles
- Consistent style
- Appropriate comments

### Architecture
- Design patterns
- Separation of concerns
- Abstraction levels
- Component boundaries
- Dependency management

### Maintainability
- Easy to understand
- Easy to modify
- Easy to test
- Well-documented
- Error handling

### Performance
- Efficient algorithms and data structures
- Resource management
- Caching strategies
- Database query optimization
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall