skills2026

Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.

Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.

Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.

Use when React components are too large or complex and need extraction, simplification, or separation of concerns.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.

Use when implementing or reviewing football data logic, pitch coordinates, event modeling, or sports vision pipelines.

Use when reviewing frontend code changes for correctness, quality, performance, and maintainability risks.

Use when writing or improving frontend tests with Vitest and React Testing Library using reliable patterns and coverage checks.

Use when preparing commits, branch naming, changelog summaries, or pull request descriptions from current changes.

Use when coordinating multi-step project work that needs planning, execution tracking, and status handoffs.

Use when starting or resuming work to quickly understand project state, active decisions, and immediate next steps.

Use when designing high-fidelity UI/UX flows or converting design artifacts into production-ready frontend implementations.

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when executing substantial coding tasks to maintain planning discipline, quality checks, and risk-aware delivery without blocking straightforward requests.

Use when major refactors or feature additions may have changed behavior, APIs, setup, or plans and documentation needs to be validated against the current repo.

Use when starting a task to discover and apply relevant skills before substantial work, while adapting to the current agent environment and available tools.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification