Use after non-trivial changes under core/, modules/, or host/ to review the changes against the ABP/DDD rules and three-layer architecture constraints…
Scores
78 out of 100 · grade B+
2026-08-04
Works
40% of the score
100/100
Loads cleanly: valid frontmatter, required fields present, no dangling references.
Maintained
25% of the score
100/100
no commits in the last 12 weeks
Adopted
20% of the score
12/100
6 stars on the source repo.
Documented
15% of the score
73/100
1,156 words with worked examples.
Loads cleanly. Every structural check Claude Code needs to register this passed. Last commit today.
What it says it does
Use after non-trivial changes under core/, modules/, or host/ to review the changes against the ABP/DDD rules and three-layer architecture constraints declared in .claude/rules/ and CLAUDE.md. Invoke proactively when the user asks whether a change is architecturally correct, whether it follows the rules, or whether it breaks dependency direction, and before committing large changes.
Every number above came out of reading the file and its repository. Nothing is a judgement call, nothing is a model’s opinion, and nothing can be paid for. The full method is published. Source last committed 2026-08-04.
Also in dignite-projects/vault-extract
Other artifacts published from the same repository.
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.