Skip to content

Standards Over Skills ​

When a standard and a skill from outside the project conflict, such as a plugin's, the standard wins. Such a skill is a starting point. The standards are the source of truth for the project's conventions.

Why ​

The standards hold how the project works, so they come first.

How To Apply ​

  • On conflict, follow the standard and ignore the skill's advice for that point.
  • When you notice the skill is wrong (contradicts a standard or contradicts what the repo does), the right way goes into a standard, which wins, so the next session doesn't re-hit the same friction. The skill itself is never edited.
  • The standard is a change to the harness, so it goes the way healing says, and the report names it (Always Make No Mistakes).