Operational guide for acceptance testing using ATDD principles. Activates when writing acceptance tests, implementing features with acceptance criteria, fixing acceptance test suites, or designing architecture for testability.
Guide Agile software development practices using Uncle Bob's teachings from the Clean Code series. Operational procedure for assessing team maturity, diagnosing Agile health, and fixing common anti-patterns. Activates when discussing Agile methodology, iteration planning, velocity, estimation, continuous integration, Definition of Done, or when user mentions Scrum, XP, sprint, velocity, planning game, or professional expectations.
Map Clean Architecture to your actual stack. Detect your framework, deployment model, and existing patterns. Convert architecture principles into decision rules you can verify. Draw boundaries the way your codebase needs — not from a textbook. Activate when designing system structure, defining use cases, placing modules, reviewing dependency direction, or choosing monolith vs microservices.
Comprehensive code review across 10 dimensions (Naming, Functions, Classes, Error Handling, Comments, Formatting, Tests, Architecture, Patterns, Professional Standards). Coordinates specialized skills for deep analysis. Final quality gate: code must pass with no critical issues.
Module boundaries, package organization, monorepo structure, dependency management, composer/npm/pip/cargo package design. Activate when defining package structure, managing coupling across module boundaries, or when the user mentions monorepo, package.json, composer.json, coupling, cohesion, circular dependency, or module design.
Apply functional programming principles to improve code quality. Activate when reviewing code with pure functions, immutability, state management, higher-order functions, functional composition, or when the user mentions FP, pure functions, immutability, map/filter/reduce, side effects, or functional architecture.
Write and refactor clean functions. Activate when writing new functions, refactoring existing ones, reviewing code for function quality, or when the user mentions function size, arguments, side effects, extract method, or complexity. Functions are the first unit of organization — if they're wrong, everything above them inherits the mess.
Operational guide for working with legacy code incrementally. Activates when dealing with untested, poorly structured, or difficult-to-change code. Use characterization tests, Boy Scout acts of kindness, clean module extraction, and strangulation technique to improve volatile code while protecting it with tests.