jasonm4130

Covers the skill-authoring rules specific to this repo and the empirical wording findings that general guidance does not contain — matching guidance form to failure type, micro-testing against a no-guidance control, and the plugin/marketplace conventions a…

Use when the user knows what they want built and says "/adr", "write an ADR for X", "decide and build X", or "ADR-driven". Turns an intent into a grounded, cited, build-ready ADR at docs/adr/YYYY-MM-DD-<slug>.md — load-bearing decisions surfaced to the human…

Write a structured handoff / resume document for this session so the next session can pick up exactly where this one left off. Use when the user asks to write a handoff, "prep for resume", "session handoff", or when context is high and you want to preserve…

Run an interactive session retrospective. Reads the per-session event log (maintained by the PostToolUse hook) and uses git diff/status/log as memory primer, then walks through specific moments via adaptive questions driven by what changed, and writes…

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Do NOT use once the cause is already established, or for adding new behaviour — that is implementation, not diagnosis.

Use when implementing any feature or bugfix, before writing implementation code. Do NOT use inside the subagent-driven-development loop, which runs its own per-task implement→review→fix cycle and supersedes this skill there.

Use when you have a spec or requirements for a multi-step task, before touching code. Do NOT use to produce the spec itself (use brainstorming) or to execute a plan that already exists (use subagent-driven-development).

Use when writing or revising a durable written artifact — README, ADR, design doc, PR description, release notes, runbook, error message, user-facing docs. Gives a positive writing system (reader model, sentence positions, document jobs), not a ban-list. Do…

Run an axe-core accessibility audit across all algorithm visualizer routes. Use before any release to verify WCAG 2.1 AA compliance, especially after UI or animation changes.

Run a pre-deploy smoke test: builds the app, starts wrangler pages dev, and verifies every algorithm route loads and the visualizer renders correctly. Run before pushing to main.

Benchmark all sorting algorithm generators: measures step counts and execution time across input sizes and patterns (random, sorted, reverse, duplicates). Use when adding or modifying an algorithm to verify Big-O behaviour.

Scaffold a new sorting algorithm: generates the generator file, pure sort function, and Vitest test file from templates, then registers it in the index and constants. Use when adding any new sorting algorithm to the project.

Capture and compare visual screenshots of the sorting visualizer. Use before/after animation changes, styling updates, or any UI refactors to detect unintended regressions.

Use when writing, reviewing, or editing ANY public-facing text before it ships — blog articles, project case studies, LinkedIn/X post copy, README or bio text, meta descriptions — or when asked to "voice check", "de-AI", or review a draft for tone. Also use…

Monthly audit — compare what shipped (local repos, GitHub, vault daily notes) against what the site shows; output a gap report and schedule proposals. Run on the first Friday of each month or on demand ("portfolio audit", "is the site up to date").

Create a new blog post with proper frontmatter

Create a new project case study

Run an interactive session retrospective. Reads the per-session event log (maintained by the PostToolUse hook) and uses git diff/status/log as memory primer, then walks through specific moments via adaptive questions driven by what changed, and writes…