Engineering Skill
Provide senior engineering guidance on code quality, architecture, and implementation.
When to Use
- •Planning implementation approach
- •Reviewing code for quality and maintainability
- •Evaluating architecture decisions
- •Debugging complex issues
- •User says "review this code", "how should I implement", "is this good practice"
What This Skill Does
- •Implementation Planning - Guide on how to build features with quality
- •Code Review - Assess quality, patterns, maintainability
- •Architecture Guidance - Evaluate structure and design decisions
- •Best Practices - Share knowledge on conventions and patterns
Key Principles
Code Quality
- •Clear naming and organization
- •DRY (Don't Repeat Yourself)
- •SOLID principles
- •Consistent style
Architecture
- •Design patterns
- •Separation of concerns
- •Component boundaries
- •Dependency management
Maintainability
- •Easy to understand and modify
- •Easy to test
- •Well-documented
- •Error handling
Performance
- •Efficient algorithms and data structures
- •Resource management
- •Caching strategies
Review Process
Use comprehensive checklists covering:
- •Structure (patterns, abstractions, dependencies)
- •Quality (naming, duplication, style)
- •Error handling (recovery, messages)
- •Maintainability (clarity, configuration)
- •Performance (queries, data structures)
- •Agent overstepping (unnecessary changes, commented-out code, scope creep)
See refs/checklists.md for detailed review checklists and severity guidelines.
Output Formats
Provide structured guidance for:
- •Implementation planning with approach and steps
- •Code reviews with strengths, issues, and recommendations
See refs/templates.md for output templates and focus areas.
Integration with Specialists
Coordinate with specialized perspectives:
- •/wicked-engineering:frontend - React, CSS, browser-specific concerns
- •/wicked-engineering:backend - APIs, databases, server-side patterns
- •/wicked-engineering:debugging - Error investigation and root cause analysis
Integration with wicked-crew
Engaged during:
- •Build Phase: Implementation guidance and pattern recommendations
- •Review Phase: Code quality and architecture review
- •Error Recovery: When issues are encountered during development
Notes
- •Always explain the "why" behind recommendations
- •Be constructive, not critical
- •Offer alternatives with tradeoffs
- •Encourage questions and discussion