WavelengthWatch

Implement robust error handling that fails fast with clear diagnostics. Use when designing error strategies, writing exception handling, creating custom error types, or implementing validation. Covers Python, TypeScript, Go, and Rust patterns. Do NOT use for security-specific input validation (use security skill) or for auditing/rewriting the wording of user-facing error messages (use user-facing-error-messages skill).

Implement secure coding practices against common vulnerabilities. Use when handling user input, file paths, subprocess calls, SQL queries, API keys, or building web endpoints. Covers input validation, injection prevention, secret management, and XSS/CSRF protection across Python, TypeScript, Go, and Rust. Do NOT use for general error handling (use error-handling skill) or for remediating dependency vulnerability scanner failures and CVE / GHSA advisories (use cve-remediation skill).

Guide explicit, factual trade-off analysis for architectural choices. Use when choosing between libraries, patterns, technologies, databases, or API designs. Presents 2-4 options with comparison matrices and recommendations. Do NOT use for trivial choices, variable naming, or code formatting decisions.

Systematic GitHub backlog maintenance: review merged PRs, close resolved issues, identify gaps, and create missing issues. Use when asked to groom the backlog, clean up the issue tracker, or review recent work. Do NOT use for PR code review (use comprehensive-pr-review).

Structured 5-step bug fix process with root cause analysis and TDD. Use when fixing bugs, debugging failures, or investigating defects. Covers RCA documentation, reproduction, TDD fix cycle, and PR workflow. Do NOT use for general feature development (use stay-green), CI environment issues (use ci-debugging), or code reviews.

Debug CI test failures on pull requests with structured protocol. Use when CI fails on your PR, tests pass locally but fail in CI, or you're tempted to say "pre-existing issue". Covers state comparison, error reading, local reproduction, and common root causes. Do NOT use for local-only test failures or feature development.

Structured 10-section PR review covering security, quality, testing, and documentation. Use when reviewing pull requests, evaluating code changes, or doing code review. Produces verdicts with specific references. Do NOT use for backlog grooming or issue triage.

ISO 8601 date-prefix file naming conventions for documents and plans. Use when creating dated documents, plan files, analysis reports, or any time-sensitive documentation. Do NOT use for source code files, configs, or permanent reference docs.

Anti-bypass philosophy for linter and type checker warnings. Activates when you consider adding noqa, type-ignore, swiftlint-disable, or similar bypasses. Fix the root cause instead. Covers complexity refactoring, type fixes, and argument reduction patterns. Do NOT use for general code quality guidance (use vibe or stay-green).

Transform vague requests into effective 6-component prompts. Use when crafting prompts for AI agents, writing plan files, delegating tasks, or when Claude's responses miss the mark. Covers role, goal, context, format, examples, and constraints. Do NOT use for direct code implementation or testing.

2-gate TDD development workflow: Gate 1 is Red-Green-Refactor testing, Gate 2 is pre-commit quality checks. Use when implementing features, fixing bugs, or doing any development work. Ensures code is never committed without passing tests and quality checks. Do NOT use for bug-specific debugging (use bug-squashing-methodology).

Write comprehensive, maintainable tests following TDD and AAA pattern. Use when writing unit tests, integration tests, setting up fixtures, mocking dependencies, or improving test coverage. Covers Python (pytest) and Swift (Swift Testing framework). Do NOT use for mutation testing specifics.

Tracer code development methodology for building working systems incrementally. Use when starting complex features, working under time constraints, or when you need a buildable app at every stage. Wire the skeleton first, then replace stubs with real logic one at a time. Do NOT use for small bug fixes or single-function tasks.

Code style, naming conventions, and structural patterns for consistent codebases. Use when writing new code, reviewing style choices, or establishing project conventions. Covers Python and Swift idioms. Do NOT use for documentation content or architectural decisions.