marnickvda

Use when reviewing, tightening, shortening, rewriting, or drafting professional decision-carrying documents for a specific reader, especially when text is too long, unscannable, repetitive, vague, detail-heavy, inaccessible, or AI-sounding.

Given a bug report and a Go source file, writes a mutation-tested regression proof on a bugfix branch using gremlins. Invoke when asked to mutation-test a bug, validate a bugfix, or prove a regression test is meaningful.

Use when creating or updating a pull request description — adds a "Checklist" section with checkmarks proving tests pass and the change was reviewed against DRY, KISS, YAGNI, SOLID, and scope discipline.

Use when the user wants to be quizzed or tested on work that was just built for them. Triggers include "quiz me", "test my understanding", "do I actually get this", "pop quiz on what you built", "test me on this branch". Not for explaining or re-teaching the work — only when they want to be tested on it.

Use when the user wants to be quizzed, tested, or "overhoord" on work that was just built for them. Triggers include "quiz me", "overhoor me", "test my understanding", "give me an SO", "do I actually get this", "pop quiz on what you built", "test me on this branch". Not for explaining or re-teaching the work — only when they want to be tested on it.