Skip to content

Thirteen plugins, one job each ​

Pick by problem, not by feature list — each plugin targets one distinct failure mode and refuses to speak outside it. Every card opens its full README in this site — same install instructions and licensing as the repo, without leaving for it.

befund

Makes a codebase describe its own health, with every finding tied to file:line evidence, and edits source only behind an authorization recorded on disk.

zeugnis

Audits code that looks right and is not, and counts a finding only after an independent pass has re-checked it.

zirkel

Makes sure a complex or ambiguous task is clarified, explored and decomposed before anyone starts executing it.

cupertino

A design and craft discipline rooted in Steve Jobs' documented decisions, run as a fixed lifecycle of stages from experience to ship, not a menu of design techniques.

arbeitsplan

Turns a described change into a budgeted workflow, builds it several independent ways at once, and lands exactly one result.

andon

Hardens a repository stage by stage, proving each handoff between stages and halting rather than advancing past one it cannot prove.

cli-scaffold

Generates a production-grade command-line application in one of 12 languages, built against one five-pillar architecture doctrine and checked against it before you see it.

passung

Finds a convention your codebase follows two or more valid ways, picks the one that should become canon, and aligns every divergent site to it with a provable equivalence check.

takt

Refuses an edit or dispatch that runs ahead of a step the repository said must come first.

lehre

Researches a code style, pattern and architecture doctrine, then denies the write that would violate it.

nacharbeit

Reviews a Claude Code plugin against the official Anthropic standard, then reworks the mechanical and local-rewrite share of what falls short.

matrize

Derives a design system once from reference exemplars you admire, names every element, and emits it to any target.

spur

Runs a pipeline once under a tracer and records, for each step, the functions it called, every file it read and wrote with its sha256, and whether it read exactly what the step before it wrote.