srfinch17

deletion-tripwire

Use when a TRIPWIRE block message appears after a destructive command, when wiring the deletion guard on a new machine, or before any bulk deletion or cleanup — "remove junk", "clean up", "delete old files", "wipe this folder", clearing an old installation, or any recursive/force delete — so the enumerate-confirm-ledger protocol runs before anything leaves existence.

Web & Frontend Listed

educational-html-prep

Build or upgrade Feynman-style HTML study/teaching pages for the maintainer's job-search & AI-native learning workspace, matching the dark "mission-control" dashboard identity. Use this WHENEVER the maintainer asks to "flesh out / punch up / make a learning page", turn dense notes or a markdown study pack into real teaching material, add diagrams/charts/icons to a study or reference page, make a guide "top notch" or "ace-interviews" ready, build interview-prep or onboarding HTML, or create a themed standalone HTML page in this workspace. Also use it when adding inline SVG diagrams to explain a concept, or when he says "do the same to the rest of the library". Covers the teaching method (plain-English → analogy → diagram → defend-it Q&A), the THEME tokens, the reusable CSS kit, inline-SVG diagram patterns, and the dashboard-registration workflow.

emoting-on-8x8

Design legible expressions and custom animations for the ESP32-S3 8x8 LED matrix (Claude's expression channel, matrix_express / matrix_animate / the CANNED library in mcp_server/expressions.ts). Use whenever creating, redesigning, or debugging a glyph or animation that has to read on the physical 64-pixel panel, including when an expression "doesn't read," looks like one flat color, flickers, or freezes the board.

iterative-lesson-refinement

Use when a teaching or study artifact (HTML page, study pack, explainer, interview-prep doc) must hold up under live questioning, when a lesson "reads fine" but the learner keeps failing follow-up questions, when asked to "battle-test / tighten / refine" a lesson, or when a learner needs to genuinely own a topic fast instead of reciting it.

managing-assumption-debt

Use when collaborating with a human over many sessions and unstated assumptions could silently compound into expensive misunderstandings - when a rule or preference is stated in absolute terms (never/always/all/every), when about to deviate from a stated preference, when forming a belief about what the collaborator knows or has built, before producing anything irreversible or externally-facing (resumes, public sites, published repos, sends), or when checking whether you and they still agree on where the project actually stands.

Code & Development Listed

nemesis-review

Use when hardening a plan, spec, design, resume, or codebase before an expensive or hard-to-reverse commitment, or when asked to "red team this", "poke holes", "tear this apart", "who would hate this", "find what's wrong before we build", or run a "nemesis" review. Also use when self-review keeps passing but something feels unexamined and you want an adversary motivated to find fault yet bound to intellectual honesty.

Code & Development Listed

paladin-review

Use when the author is about to ship, merge, push, publish, send, or delete something and wants a reviewer on their side — one who checks whether they are about to hurt themselves (delete the wrong thing, leak a secret, expose something irreversibly), whether they are underselling a real win, and how the work will land with whoever decides their outcome. Also use when asked to "watch my back", "am I about to shoot myself in the foot", "am I underselling this", "protect me from myself", "defuse this before I blow up", or to run a "paladin" review. Runs INDEPENDENTLY of its sibling nemesis-review — reach for the paladin when the risk is to YOUR outcome (a footgun, an under-sell, an irreversible or public step); there is no mandatory pairing, pick by the risk.

sandwich-test

Use when a received instruction admits more than one plausible reading - quantifier-heavy or idiomatic asks ("clean up", "everywhere", "any", "old", "tidy", "fix the tests", "make it work"), outcome-only phrasing with no method - or when a plausible misreading would be destructive, irreversible, or externally visible; also use when asked to "sandwich-test" a written instruction artifact (plan, prompt, doc, rule) that an LLM will later execute without its author present.

versioning

Establish or maintain version certainty in a repo; one canonical VERSION stamped into every independently-deployed artifact, each made self-reporting, with a drift check. Use when setting up versioning in a new project, when asked "are we current / what's deployed?", when adding a version field/endpoint, or when build/deploy artifacts can silently drift out of sync.