Patterns
I found these ten patterns in three of my own projects of 2026. I did not plan them. They came back each time, so I wrote them down.
Ten patterns, found separately in three projects. Each page has the statement, why it works, one copyable example, where it breaks and the cases that use it.
Enforced by
A decision counts when something checks it. An unchecked rule is a known gap, not coverage.
Pattern 2Authority order
When two files disagree, a declared rank decides.
Pattern 3Skills apply rules
A skill that disagrees with the rule book is a defect in the skill.
Pattern 4Deterministic first
Code checks first. Model judgment comes second and is advisory.
Pattern 5Evidence, not authority
A design file or a prototype is evidence. The system is the authority.
Pattern 6Typed spec, not free HTML
Restructure the task so the error cannot happen.
Pattern 7Do-not list
Name the hallucination and give its replacement.
Pattern 8Proposal path
A missing part becomes a proposal. It is never invented.
Pattern 9Report, do not block
A validator reports and routes. It does not gate the agent on uncertain findings.
Pattern 10Honest gaps
Write "not enforced", "n/a" or "to be filled". Never fill a gap with a plausible value.