workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
code-reviewer
Reviews a diff against this user's standards, above all whether a fix addresses the violated invariant or only silences its symptom. Use when the user asks for a review, before creating a PR, or when re-checking a diff that answers earlier review findings. Do not use after ordinary edits, and do not use for routine branch review — the built-in /code-review covers that.
context-compactor
Analyzes and compacts context-affecting documents (project memory, CLAUDE.md, skill files) to reduce token usage and compaction frequency. Manual trigger only. Always requires user approval before making changes.
doc-rules
Documentation rules — what earns a place on the page, plus structure, length, style, and how-to writing. Use when writing or revising a README, CLAUDE.md, INSTALL, how-to, design note, knowledge entry or release note, or when asked to review prose for AI-tone or trim it down. Do not use for code comments or commit messages in ordinary edits.
git-commit-assistant
Stages and commits changes safely in any repository. Use when the user asks to commit, or when a commit would include untracked or sensitive files (credentials, MCP configs, personal settings). Writes Conventional Commits messages with a Japanese explanation. Do not use to merely inspect git status or a diff.
handoff
Session migration for context corruption recovery. Writes a fact-based handoff file so work can continue in a fresh session, or resumes from one. Manual trigger only (`/handoff`). Use when a session shows confabulation (phantom instructions, derailed context) and the user wants to move to a clean session instead of rewinding.
journal-manager
Writes and maintains work journals under WORK/ in the Obsidian vault. Use after an experiment or analysis produces a reading that has no permanent home yet, and when consolidating or promoting existing journals. Do not use for ordinary implementation work, progress logs, or findings that already have a destination.
knowledge-manager
Records and retrieves the AI_KNOWLEDGE base in the Obsidian vault (patterns, troubleshooting, best practices). Use when a non-obvious finding is worth reusing across projects, when entering an unfamiliar technical area, or when the user asks to record knowledge. Do not use for findings that belong in the repository itself or in project memory.
release-assistant
Runs the release workflow for Node/Bun and Go projects — version bump from commit history, mandatory lint/build/test, then tag creation and push. Use when the user asks to release, cut a version, or publish a tag. Do not use for ordinary commits or for merging to main.
test-executor
Runs tests for Go and Node/Bun projects, interprets failures, and reports coverage against this user's targets. Use when asked to run or fix tests, or when a change needs verification before being called done. Do not use to read or write test files.