Ask Demon
You don't remember every skill, so ask. This pack complements Matt's engineering skills: Matt owns the engineering loop (grill → spec → tickets → implement → code-review — the single review entry point) and the writing skills; this pack owns the documentation and Agent-Note maintenance loop and game-domain work. The full absorption map and seams are in the pack's skills map (
in the source repository).
A flow is a path through the skills. One main flow carries the documentation work; a governance run brings a whole repository's docs in line with its standard; everything else is standalone, or a prose-and-docs tool layer that runs underneath.
Session discipline
Four standing-order lines in the host repository's root
gate every action;
writes them into a repository. Operationally:
- Before acting — answer questions and analyze proposals without writing; treat only an explicit execution signal with a confirmed scope as authorization; unclear intent gets one clarifying question first.
- Before committing — stop on any red check; the fix or its explanation ships in the same turn, and the final report names every failed check.
- Before claiming — inspect files before editing or describing them; report only work that was actually done.
- Before destructive moves — deletions, history rewrites, and force-push wait for the user to name the action.
Every flow in this pack obeys the gate: findings and plans come first, fixes run after confirmation.
The main flow: maintain a change
The route documentation work travels: review a change, simplify what it surfaces, archive what it supersedes, sync the bilingual pairs.
- — review a PR or branch against the repository's standards (skill frontmatter and body, docs, bilingual pairs, Agent Notes, scripts). Produces blockers plus suggestions. Run when a change is ready for review, or as a pre-push gate.
- — when the change touches documentation, run the structural pass and audit probes so the docs land in the right home, at the right detail, under budget. The review hands off here for doc changes.
- — take the dead, duplicated, speculative, or over-built surface the review surfaced, and turn the worthwhile ones into proposed Agent Notes or TODO markers. The review and docs steps hand off here.
- — when a change makes an owning note obsolete, classify and archive the superseded records. A simplification hands off here.
- — after the earlier steps touched docs or notes, sync their English↔Chinese pairs. The archive step hands off here when link repair edited a bilingual doc.
The flow cascades —
repo-standards-review → doc-standards (when docs touched) → find-simplifications → archive-agent-notes → translate-docs
— and each step is also independently invocable.
The governance run
A whole-repository pass when asked to govern, standardize, or audit the repository's documentation:
- Foundation — the root pointer, the documentation standard, the Agent Note tree, the bilingual pairing contract, the session-discipline lines, and the documentation budget gate must exist; missing ones come from .
- Audit — runs the structural pass and the six corpus probes; report a non-compliance list naming each document, the violated clause, and the owning fix skill.
- Fix by domain, after the user confirms scope — structure, placement, budgets → ; prose → ; leakage → ; dead surface → ; pairs → ; superseded notes → .
- Close out — the documentation gates and , re-record touched pairs, one Agent Note per non-trivial change, word deltas in the PR body — then the main flow takes the change home.
Every step confirms with the user before writing; a fix that changes promised behavior goes through a proposed Agent Note first.
Prose and docs tool layer
Four skills run beneath the flow and are reachable on their own when the prose or document structure, not the process, is the problem:
- — the base: preserve the complete proposition, then remove reasoning transcripts, repetition, and decoration. Owns editorial judgment and coverage.
- — one smell: prose whose vantage is the authoring session (dead citations, change narration, review choreography). Restate the facts, delete the transcript.
- — another smell: negation priming, absence declarations, stale meta-narrative, strawman warnings. Restate the positive target or the consequence.
- — the structure side: placement, tutorial/reference classification, corpus audits, and budget-gate probes. Owns where documents live and how they are shaped; prose-standard owns how they read.
Standalone
Off the main flow; reach for each on its own trigger.
- — before pushing, select the narrowest checks that cover the outgoing diff; protect history-rewriting pushes with .
- — land a stack of dependent GitHub PRs through ; layers with Matt's
resolving-merge-conflicts
- — turn a proven or requested workflow into a reusable skill.
- — record browser/Web UI demos as evidence GIFs for GUI-changing PRs.
- — install hook-based desktop/audio reminders for agent stop and attention events.
- — DOTA2 custom game addons.
- — Roblox Luau development, debugging, and Rojo sync.
roblox-typescript-developer
unreal-blueprint-analyzer
Setup
The maintenance flow needs a repository's conventions in place first — the Agent Note tree, the bilingual pairing contract, the documentation standard, the session-discipline lines, and the documentation budget gate. Run
once to scaffold them and record where they live.