Best Practices
vinta/hal-9000Use when about to choose, configure, or refine a tool, library, config format, API pattern, or project setup, or before proposing a design of your own — research current guidance, pitfalls, and prior art first; already knowing an approach, or assuming no prior art exists, is not an exemption. Also use when the user asks about best practices, gotchas, or recommended patterns, or says "search online
At a glance
/plugin marketplace add vinta/hal-9000
/plugin install best-practices
Setup, runtime and requirements describe vinta/hal-9000, the repo this skill ships in.
Also in vinta/hal-9000
View the repoUse when auditing Claude Code settings and env vars against the latest docs and suggest tailored changes
Use when the user asks for a blindspot pass or to find their unknown unknowns, or signals unfamiliarity with a domain, tool, or codebase are...
Use when making any git commit. Always pass why the changes were made as the argument; when no reason was stated, pass the request that prom...
Use when refactoring a user-level or project-level AGENTS.md for progressive disclosure
Use when refactoring a user-level or project-level CLAUDE.md for progressive disclosure
Use when you want docs, issues, READMEs, comments, or UI text written in Global English — plain words, translation-friendly grammar, still n...
Use when creating or editing a skill that uses Bash commands, file writes, or external tools and the allowed-tools frontmatter may be incomp...
Use when writing English prose the user will sign — READMEs, blog posts, docs, code comments, issues, PRs, emails — drafted or rewritten in...