daily-prevention

Use this skill to help a developer keep day-to-day code simple, maintainable, and robust — through automatable prevention (linters, type checkers, static analysis, and — for what static analysis structurally can't catch — AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how do I keep this codebase maintainable", "what linter should I use", "which linting rules should we enable", "set up static analysis for us", "reduce cognitive load in code review", "our code keeps rotting", or when the user wants day-to-day engineering hygiene rather than a full team assessment. Standalone — no prior audit is required. Primarily advisory — recommends tools, specific rule sets, and how to wire them into editor/pre-commit/CI, adapting first to whatever is already configured in the repo — but may run a linter/type-checker command when the user explicitly authorizes it; it never executes anything on its own initiative.