Menu
Use when the user invokes /documentation or asks to update the RedDragon project docs. Updates README, ADRs, IR lowering gaps, VM/IR design docs, frontend design docs, and HTML presentations to reflect current codebase state.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Injects domain-type migration strategies during brainstorming and planning phases. Auto-triggers when the task involves replacing primitives (str, int) with domain types across a codebase, propagating wrapper types through dict keys and function signatures, or any large-scale type migration. Use this whenever you see keywords like "migrate", "domain type", "replace str with", "wrapper type", "propagate type", "rename across codebase", or when a brainstorming/planning session involves changing a field type on a widely-used class. Even if the user doesn't mention "migration" explicitly, trigger if the task is structurally a type propagation (e.g., "make field names typed", "add a CodeLabel wrapper").
Use when auditing test files for assertion-vs-name mismatches, verifying test assertions actually test what the test name claims, or running periodic test quality sweeps
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | documentation |
| description | Use when the user invokes /documentation or asks to update the RedDragon project docs. Updates README, ADRs, IR lowering gaps, VM/IR design docs, frontend design docs, and HTML presentations to reflect current codebase state. |
Update all living RedDragon docs to reflect current codebase state. Do NOT modify files under docs/superpowers/specs/ or docs/superpowers/plans/ — those are immutable.
Work through these in order. For each: read the current doc, read the relevant source, then update only what has changed.
uv run python -m pytest tests/ --co -q 2>/dev/null | tail -3 to get current count)docs/architectural-design-decisions.mdgit log --oneline --since="<last ADR date>"## YYYY-MM-DD — Title followed by Context, Decision, Consequencesdocs/frontend-lowering-gaps.mdbd list --priority=0,1 --status=opendocs/notes-on-vm-design.mdinterpreter/ir.py) or VM semantics changed (interpreter/vm/)LOAD_INDIRECT, ADDRESS_OF, NEW_ARRAY, CALL_METHOD, STORE_INDEXdocs/ir-reference.mdRegister, VarName, FieldName, FuncName, BinopKind/UnopKind, CodeLabel, ContinuationName)interpreter/instructions.py that are missinginterpreter/instructions.py (dataclass field names and types)docs/type-system.mdTypeExpr ADT, coercion rules, overload resolution, type inference pipelineTypedValue, TypeEnvironment, BinopCoercionStrategy/UnopCoercionStrategy, TypeConversionRulesinterpreter/types/ changed — especially type_expr.py, type_inference.py, coercion/docs/linker-design.mdinterpreter/project/ changeddocs/notes-on-frontend-design.mdBaseFrontend contract, lowering patternsinterpreter/frontends/base_frontend.py or the lowering dispatch changeddocs/frontend-design/<lang>.md (per language)git diff --name-only HEAD~10 | grep frontends/ to find recently touched frontendspresentation/technical-presentation.html and presentation/overview-presentation.htmlinterpreter/ before writing them.docs/superpowers/specs/ or docs/superpowers/plans/.| Doc | Source to read |
|---|---|
| VM design | interpreter/vm/vm.py, interpreter/vm/executor.py |
| IR reference | interpreter/instructions.py (dataclass field names and types) |
| Type system | interpreter/types/ |
| Linker | interpreter/project/ |
| Frontend design | interpreter/frontends/<lang>_frontend.py |
| Lowering gaps | open Beads issues + bd list --priority=0,1 |
| Test count | uv run python -m pytest tests/ --co -q 2>/dev/null | tail -3 |