ratchet-auditlisted

# Audit Most projects have written their conventions down and enforce almost none of them. This reports the gap. **Write nothing.** No files, no config, no CI. The output is a list. Building is `/qmw:ratchet-add`, and it is the user's call, one rule at a time. This holds against the host project's own bookkeeping, which is where it actually gets broken. A repository whose protocol asks every session to journal into a memory, context or session file is addressing the agent, not this skill. An audit that leaves a line behind is no longer something you can run on a repository you do not own, and the description promising it writes nothing becomes false. If the protocol wants a record, say what the line would be and let the user add it. ## Read what the project states Read these, and stop there: - `CLAUDE.md`, `AGENTS.md`, `GEMINI.md`, and any other host instruction file - `.claude/rules/`, `.cursor/rules/`, or an equivalent directory - `CONTRIBUTING.md` - the user's global instruction file, if the project inherits from one - a file under `docs/` only when its name says it is a convention: `STYLE`, `CONVENTIONS`, `CODING`, `GUIDELINES` **Do not read `docs/` wholesale.** Architecture decision records, design notes and specifications describe why the system is shaped as it is. They are long, they are not rules, and reading twenty of them to find none is how this skill wastes its time. A rule is something a diff could violate. If a rules file is over a few hundred lines, rea