vinta

update-playbooks

(project) Use when updating install tasks in playbooks/roles/ against upstream docs — bumping a pinned version, adopting a newly recommended install method, repointing a doc link that moved, or realigning the community.general pin with the brew-installed ansible

blindspot

Use when the user asks for a blindspot pass or to find their unknown unknowns, or signals unfamiliarity with a domain, tool, or codebase area ("never used X", "first time doing Y", "no idea where to start", "don't know what I don't know") before working there. Turns unknown unknowns into known unknowns so the user can prompt well

Code & Development Featured

commit

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

refactor-claude-md

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

update-allowed-tools

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

write-like-me

Use when writing English prose the user will sign — READMEs, blog posts, docs, code comments, issues, PRs, PR and issue comments, emails — drafted or rewritten in their own voice at native fluency. Fires mid-task too: a comment drafted inside another skill's workflow, or text the user will approve before it ships

publish-plugins

(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests

magi

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"

bump-plugin-version

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

simple-english

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

best-practices

Use 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"

refactor-agents-md

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

brainstorm

Use when the user wants ideas rather than answers — what to build, do, or try ("give me ideas", "what could we build", "brainstorm this", "surprise me") on any topic, technical or not. Returns ~30 one-line ideas from independent perspectives, a quarter deliberately absurd; gathers options, never plans or judges them