a11y-pass
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Write safe, reversible database migrations for this repo's conventions. Use for any schema change.
$ npx -y skills add Archive228/loopkit --skill migration-writer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/migration-writerContext preview
The summary Claude sees to decide when to auto-load this skill.
Write safe, reversible database migrations for this repo's conventions. Use for any schema change.
name: migration-writer description: Write safe, reversible database migrations for this repo's conventions. Use for any schema change. when_to_use: add/alter a table, column, index, or constraint
1. Read the current schema first. Match the repo's migration tool and naming (`NNN_<verb>_<noun>`). 2. Write BOTH up and down. A migration you can't reverse is a migration you can't deploy safely. 3. **Live-safe**: on a hot table, adding a NOT NULL column with no default, or an index without CONCURRENTLY, takes a blocking lock. Split into steps: add nullable → backfill → add constraint. 4. Backfill large tables in batches, not one statement. 5. Never edit an already-merged migration — add a new one. Test with a dry-run before committing. Output the migration + the exact deploy order.
33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI).
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt…
Review a diff against the goal spec assuming the code is BROKEN. The reviewer
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything…