hal-9000

Use when the user wants technical or developer writing (docs, issues, READMEs, comments, UI text) drafted or rewritten to be clear and simple for a global audience

Use when brainstorming ideas, features, or directions for a project where independent perspectives from different model families (Claude/Codex/Gemini) would surface blind spots and spark creative options the user hasn't considered — especially "what cool things can I add", "what should I build next", "give me ideas for X"

Use when refactoring a user-level or project-level CLAUDE.md for progressive disclosure

Use when refactoring a user-level or project-level AGENTS.md for progressive disclosure

Use when creating or editing a skill that uses Bash commands, external tools, or skill invocations and the allowed-tools frontmatter may be incomplete

(project) Use when bumping hardcoded tool versions in playbooks/roles/ to their latest releases

(project) Use when editing any file under skills/hal-skills/ or plugins/hal-voice/ to bump the plugin version before committing

Use when making any git commit. Always pass a brief description of what changed as the argument.

Use when the user asks about best practices, gotchas, common pitfalls, or recommended patterns for tools, libraries, config formats, API patterns, or project setup, or when setting up, configuring, choosing, or refining these where outdated guidance causes debugging pain. Also use when the user says "search online", "how should I", or "what's the best way to"