What problem does it solve? Teams often rely on vague "best practices" essays or unverified assumptions when defining code quality standards, leading to generic checklists that don't match the actual codebase. This Skill produces project-specific, research-grounded quality harnesses where every status claim is verified against the real repository. ## Core Features & Use Cases - Four scoped harness areas: Frontend (Core Web Vitals, WCAG accessibility), Backend/API (OWASP API Top 10, data-layer safety), Security (OWASP Top 10, secrets, supply chain), and Deploy/Release (rollout strategies, CI/CD structure), each in its own doc tracked by a docs/harnesses.md index. - Two-pass process: A delegated research pass gathers cited standards (OWASP, WCAG, Kubernetes docs) with every status cell flagged NEEDS REPO VERIFICATION, followed by a verification pass that greps the real codebase, confirms or corrects each claim, and applies cheap in-scope fixes immediately. - Standardized doc format: Dense tables with Dimension / Source / Measurable bar / Why it matters / Status here columns, plus workflow checklists, implemented-fixes lists, and explicit non-goals. - Use Case: Ask to build a security harness for a Node.js API project — the Skill researches OWASP guidance, verifies each control against the actual code (e.g. confirming a /health endpoint exists), fixes a missing Dependabot config, and ships a cited, verified checklist doc. ## Quick Start Build a backend API quality harness for this project, verify every checklist item against the actual codebase, and fix any cheap gaps you find.
