My Projects

Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.

Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the c...

Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.

Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.

Close out a session — summarise what changed, capture what was learned, and prepare the commit.

Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.

Run the project's own tests, linter, type checker and build, and report what actually failed.

The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.

Audit the code for vulnerabilities, leaked secrets and risky dependencies before it ships.

Save a project fact, decision or gotcha so your next session already knows it.

Hand off an unfinished session to the next one — what's done, what's next, what's blocked.

Write the spec before the code, then check the built thing against it — so agents build what was agreed, not what they invented.

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use...

Replace with description of the skill and when Claude should use it.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, ed...

Ask which skill or flow fits your situation. A router over the skills in this repo.

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize note...