What problem does it solve? Teams struggle to document coding conventions that both humans and LLM agents can objectively enforce, resulting in vague rules like "write clean code" that no reviewer or tool can consistently check. ## Core Features & Use Cases - Enforceability Testing: Apply a three-question test to determine whether a convention can be objectively verified by reviewers, linters, or LLM agents. - Aspiration-to-Rule Conversion: Transform vague quality goals into observable, measurable conventions using concrete examples and a conversion table. - Convention Categorization: Organize rules by naming, file structure, error handling, documentation, dependencies, and testing, with guidance on what to exclude. - Use Case: When drafting the Context section of HARNESS.md during /harness-init, use this Skill to write stack declarations and conventions that the harness-gc agent and /harness-audit command can later validate against the actual codebase. ## Quick Start Ask the agent to help write enforceable conventions for the Context section of HARNESS.md based on your project's current stack and coding standards.
