|
// you commented setup
the official plugin that fixes your claude code (full setup guide)
The reel showed you what Claude Code Setup does. Here is the part that did not fit in 41 seconds: the exact install, the three prompts that run it, and a decision guide so you accept the right recommendations instead of hoarding plugins again.
| > install_it 2 MINUTES |
Inside Claude Code, run these two commands: /plugin marketplace add anthropics/claude-plugins-official
/plugin install claude-code-setup@claude-plugins-official |
Or grab it from the official page: claude.com/plugins/claude-code-setup (179k+ installs, by Anthropic). |
| > run_it 3 PROMPTS |
It is a skill, so you just ask. These are the three official prompts, straight from the README: "recommend automations for this project"
"help me set up Claude Code"
"what hooks should I use?" |
It scans your codebase and suggests the top 1 to 2 automations per category. Read-only: it never touches your files, so it is safe to run on anything, including client work. |
| > what_to_accept DECISION GUIDE |
The whole point is tailored, not more. My accept rules per category: MCP servers — accept if you touch that tool weekly. context7 for docs is a near-always yes. Hooks — accept auto-format and lint. They fix the boring stuff forever. Subagents — accept security-reviewer the moment you have auth or payments code. Skills — accept one, not five. The one matching what you build most. Slash commands — accept /test if you have a test runner. Skip the rest until you miss them. |
| > pro_tips FROM MY OWN SETUP |
1. Re-run it per project. Recommendations change with the codebase, that is the point. 2. Run it on a fresh repo AFTER your package.json and folder structure exist. It reads those to decide. 3. If you already hoard plugins (I had 97 skills installed), run it and remove what it never mentions. Less is faster. 4. Uninstalling later is one command: /plugin uninstall claude-code-setup |
I read every reply, and the best plays come from your answers.
Talk soon,
Mike
|