Loading...
Loading...
Found 10 Skills
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Clean Code principles (DRY, KISS, YAGNI), naming conventions, function design, and refactoring. Use when user says "clean this code", "refactor", "improve readability", or when reviewing code quality.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Apply Test-Driven Development workflow for new features and bugfixes.
Apply Andrej Karpathy-inspired coding-agent guidelines in Codex. Use when writing, reviewing, debugging, or refactoring code to surface assumptions, avoid overengineering, keep edits surgical, and define verifiable success criteria.
AI SDLC reusable quality-lens workflow. Use when an AI assistant needs to challenge a requirement, design, plan, test strategy, change, or delivery artifact through pre-mortem, adversarial, edge-case, stakeholder-conflict, reversibility, abuse-case, operational-failure, or assumption lenses and finalize evidence-backed findings with ownership and traceability. Supports `--quick-flow` for selected high-value lenses and `--full-flow` for the complete applicable registry.
Develop software with validation requirements first. Emphasizes writing tests before implementation to guide design decisions.
Audit a feature spec against the actual implementation to find where behaviours or user-flow contracts no longer match the code. Use when the user says "is this spec still accurate", "check the spec against the code", "I think this wizard bypasses the documented flow", or before relying on a spec that hasn't been touched in a while. Reports only. Pairs with spec-assess-coverage, which asks whether tests exist.
Apply repository-grounded senior engineering judgment to substantial JavaScript or TypeScript work and bounded JS/TS changes with production or cross-boundary risk. Do not use for trivial syntax questions, generic tutoring, or tasks with no JS/TS artifact unless explicitly invoked. Use for Node, browser, frontend, worker, and edge work where correctness, contracts, state, effects, concurrency, compatibility, security, reuse, runtime alignment, or long-term ownership materially matters.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals