airwaylab

Use this skill when reviewing or auditing the AI insights system prompt for hallucination risk, prompt quality, output reliability, and cost. MDR language is delegated to the mdr-compliance-check skill + mdr-string-check CI. Don't use for general MDR audits (use mdr-compliance-check) or code review (use code-review).

Use this skill when implementing API routes, Supabase integration, authentication, webhooks, database migrations, or server-side functionality. Don't use for UI components (use frontend-feature), bug fixes (use bug-triage), or code review (use code-review).

Use this skill when auditing project dependencies for security vulnerabilities, outdated packages, or unnecessary bloat. Use on a monthly cadence or when a security advisory is reported. Complements the dependency-review CI gate (which only blocks high-severity new deps on PRs) with a proactive audit. Don't use for feature development or bug fixes.

Use this skill when triaging, investigating, or fixing a reported bug. Covers reproduction, root cause analysis, fix implementation, and regression testing. Use when assigned a bug report or when investigating unexpected behavior. Don't use for new features (use backend-feature or frontend-feature) or reviews (use code-review).

Use this skill when implementing UI components, dashboard features, landing page changes, chart visualizations, or client-side functionality. Don't use for API routes or backend work (use backend-feature), bug fixes (use bug-triage), or code review (use code-review).

Use this skill when auditing code changes for GDPR compliance, privacy policy accuracy, data flow verification, or consent mechanism review. Don't use for MDR SaMD compliance (use mdr-compliance-check) or general code review (use code-review).

Use this skill when preparing a release, updating the changelog, or managing the deployment pipeline. Use after a set of features have been merged and are ready for production. Don't use for individual feature PRs or bug fixes.

Use this skill when auditing test coverage, identifying untested code paths, or planning test writing priorities. Use periodically or after significant code changes. Don't use for implementing individual bug fix tests (use bug-triage) or build verification (run checks directly).