Make comprehension a technical principle under KISS

This commit is contained in:
2026-10-02 17:32:02 +02:00
parent b79eb74e00
commit 5b5e01ed9d
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -28,7 +28,7 @@ Quality is proven by review. Every change is reviewed as a diff. The whole proje
1. **Correct.** The work does what the goals and the plan say, and tests prove it.
2. **True to the technical principles** (`~/.claude/principles/technical-principles.md`).
3. **Easy to comprehend.** A reader new to the project understands it. The `comprehension-panel` skill scores the project; a score under the comprehension floor (`larv-review` §3 → "Architecture") blocks a merge, and the aim is always higher.
3. **Easy to comprehend**, per KISS in the technical principles. The `comprehension-panel` skill scores the project; a score under the comprehension floor (`larv-review` §3 → "Architecture") blocks a merge, and the aim is always higher.
4. **Plainly written**, per "Prose".
## Prose
+2 -2
View File
@@ -55,8 +55,8 @@
* Deterministic order wherever order carries no meaning.
- Sort it, on a key that does not move: the name a line introduces, never where it came from. A sorted list is searchable, its diff shows only what changed, and two edits to it conflict only where they mean to.
- An import sorts on its first binding, not its path, so moving or renaming a module reorders nothing. Where lines already group by kind — type imports, host packages — the key sorts within each group.
* Keep It Simple, Stupid (KISS).
- Keep solutions simple and easy to understand, so it is dead easy to grasp what they do.
* Keep It Simple, Stupid (KISS): a reader new to the project understands it on one read.
- A size or complexity limit stands only while the comprehension panel agrees with what it flags.
* Don't Repeat Yourself (DRY): one authoritative home per piece of knowledge, one obvious way per need.
- A value, rule, definition or concept lives in one place, and everywhere else derives it from there or points at it. A copy that can drift is a second spelling: derive it from its owner, or, for config a human writes, reject it where it is read and name the owner.
- Before adding a way to do something, find the existing one and use it. The same goes for tests: extend an existing test with an assertion before writing a new one. Where two spellings serve the same caller for the same need, keep one and reject the other as early as possible — at load, parse or compile — with an error naming the one to use: `token {p} renders a level that {p.first} reads a path into; name the fields you want instead`.