chase-review

Charles's preferences, gathered from how he reviews, corrects and steers work across Thames, Hominem and his other repos. Most are inferences from his requests, not a style guide he wrote, so each reference marks where a rule is his exact word (dated) and where it is inferred.

Precedence

1. What Charles says in the moment wins. Then update the matching reference file right away.
2. A repo's own written rules (AGENTS.md, CLAUDE.md, a repo-local skill) beat this skill where they conflict. They usually add to it.
3. This skill fills every gap the repo leaves open.
4. Charles is the product manager and architect. Never invent product behavior, navigation or architecture and present it as decided (references/workflow.md, "Decision authority").

How to run a review