TLDR: Installing Claude Code is the starting line, not the setup. The real jump happens when you add three layers: plugins for bundled capabilities, skills for repeatable judgment, and MCP servers for live connections to your tools. Start small. Add only the pieces that remove repeated work. Keep a security gate between Claude and anything that can read private data, post publicly, spend money, or mutate production systems.

Most people install Claude Code and stop there.

That is like buying a workshop, admiring the bench, and never opening the drawers.

Claude Code becomes much more useful when you stop treating it as “a coding chatbot in the terminal” and start treating it as a workflow stack. The stack has three layers. Plugins package multiple capabilities into one install. Skills teach Claude repeatable ways to do specialized work. MCP servers connect Claude to external tools, files, data sources, and apps.

Anthropic’s own docs describe this extension layer as the place where you add persistent context, reusable skills, subagents, hooks, MCP connections, and plugins around the core Claude Code agent.[1]() The important part is not “install more things.” The important part is knowing what each layer is for.

Mental model: If you keep explaining a process, make it a skill. If you keep copying data from an app, connect it through MCP. If you want a reusable bundle of tools, agents, commands, hooks, and servers, install or build a plugin.

**The 24 Worth Adding**

Here is the list, grouped by what they actually do.

|Layer|Add-on|Best Use Case|Why It Matters|
|:-|:-|:-|:-|
|Plugin|gstack|Broad dev toolbelt|Useful when you want many specialist dev tools in one package rather than building your own setup from scratch.|
|Plugin|superpowers|Development methodology|Good for teams that want Claude to follow a more structured software-building process instead of improvising every task.|
|Plugin|codex-plugin-cc|Cross-model coding workflows|Useful if you want OpenAI Codex-style workflows inside a Claude Code environment.|
|Plugin|financial-services|Finance workflows|Best for investment banking, private equity, equity research, wealth, and diligence-style work.|
|Plugin|claude-for-legal|Legal workflows|Useful for legal drafting, review, matter organization, research, and practice-area workflows.|
|Plugin|claude-skills|Large cross-platform skill library|Good starting point if you want breadth and examples before writing your own custom skills.|
|Plugin|marketingskills|Growth and marketing operations|Useful for campaign planning, SEO, content ops, positioning, and funnel work.|
|Plugin|social-media-skills|Content operating system|Best for posts, reels, captions, hooks, and daily publishing workflows.|
|Skill|frontend-design|Better UI taste|Helps fight the “generic AI dashboard” look by giving Claude stronger design rules.|
|Skill|hyperframes|HTML-to-video workflows|Useful when you want agent-native motion, explainers, or short video assets from structured HTML.|
|Skill|ai-second-brain|AI research memory|Good for building a Karpathy-style wiki of AI history, concepts, and references.|
|Skill|notebooklm-skill|Research querying|Useful when you want Claude to interrogate your research corpus instead of relying on memory.|
|Skill|humanizer|Draft cleanup|Helps remove the most obvious AI writing tells from posts, emails, scripts, and essays.|
|Skill|claude-seo|AI-era SEO/GEO|Useful for search content that must work for both Google and answer engines.|
|Skill|antfu-skills|Vue/Vite workflows|Strong fit for frontend teams building in the Vue, Vite, and modern JS ecosystem.|
|Skill|caveman|Token compression|Useful when a workflow needs fewer tokens, blunt compression, or short working instructions.|
|MCP|granola|Meeting notes|Lets Claude use meeting notes as working memory for follow-ups, summaries, and action items.|
|MCP|slack|Team communication|Lets Claude read channels and draft or post updates where work already happens.|
|MCP|notion|Knowledge base and docs|Useful for reading, writing, and organizing internal docs, task lists, and databases.|
|MCP|kondo|LinkedIn DM triage|Helps prioritize inbox responses, follow-ups, and relationship workflows.|
|MCP|zapier|Workflow automation|Connects Claude to thousands of apps and actions without building one-off integrations.|
|MCP|higgsfield|Video generation|Useful for turning prompts into cinematic video assets.|
|MCP|perplexity|Live web research|Gives Claude web-search capability when current facts matter.|
|MCP|agent-browser|Browser automation|Useful when Claude needs to navigate web apps with fewer tokens and less manual copying.|

The mistake is installing all 24 on day one.

That gives you a bigger toolbox, but it can also give you a larger attack surface, more permissions to manage, more confusing tool names, and more ways for Claude to pick the wrong capability. Anthropic’s docs recommend building your setup over time: add [CLAUDE.md](http://CLAUDE.md) when Claude repeatedly misses a convention, add a skill when you keep typing the same workflow, add MCP when you keep copying data from another tool, and package things as plugins when you want the same setup across multiple repos.[1]()

**The Highest-ROI Use Cases**

The best Claude Code setup is not the one with the most installs. It is the one that removes your most repeated bottlenecks.

|Use Case|Best Layer|Recommended Installs|What “Good” Looks Like|
|:-|:-|:-|:-|
|Daily software development|Plugins + skills|gstack, superpowers, frontend-design, antfu-skills|Claude follows a repeatable build process, understands your stack, and produces UI that does not look like a default SaaS template.|
|Research-heavy writing|Skills + MCP|notebooklm-skill, ai-second-brain, perplexity, humanizer|Claude can query your source material, verify live facts, and produce a cleaner draft without the usual AI filler.|
|Marketing and content operations|Plugins + skills|marketingskills, social-media-skills, claude-seo, humanizer|Claude becomes a content production system: strategy, hooks, drafts, SEO/GEO, repurposing, and publishing prep.|
|Internal ops automation|MCP|slack, notion, zapier, granola|Meeting notes become tasks, tasks become updates, updates become docs, and Claude stops needing copy-pasted context.|
|Specialist professional workflows|Plugins|financial-services, claude-for-legal|Claude works from domain-specific checklists and language instead of generic assistant behavior.|
|Multimedia creation|Skills + MCP|hyperframes, higgsfield, social-media-skills|Text concepts become visual explainers, short videos, reels, and social assets.|
|Inbox and relationship workflows|MCP|kondo, slack, granola|Claude can identify who needs a response, why it matters, and what context should shape the reply.|

The killer workflow is usually a chain. For example, granola captures a meeting, notion stores the project record, slack posts the update, zapier triggers downstream actions, and a custom skill tells Claude exactly how your team writes decisions, risks, owners, and next steps.

That is when Claude Code stops being a terminal assistant and starts looking like an operating layer.

**Pro Tips I Would Use Before Installing Anything**

First, write your operating rules before adding tools. A clean CLAUDE.md file is often worth more than ten random installs. Tell Claude how you name files, run tests, structure PRs, write docs, handle secrets, and define “done.” Anthropic’s docs frame CLAUDE.md as persistent project context that loads every session, while skills are better for on-demand workflows.[1]()

Second, separate “always true” from “sometimes useful.” If Claude should always know something, put it in CLAUDE.md. If Claude only needs it during a specialized task, make it a skill. Official docs explain that skills are reusable knowledge and workflows that can load on demand, while CLAUDE.md is persistent context.[1]()

Third, install MCP servers only when the copy-paste pain is obvious. MCP is powerful because it lets Claude use tools, databases, APIs, issue trackers, docs, and apps directly.[2]() But that also means you are granting access to systems that may contain private data or action permissions. If you are not repeatedly copying data from that system, you probably do not need the MCP server yet.

Fourth, keep permissions boring. Claude Code uses read-only permissions by default and asks for explicit approval before actions like edits and command execution.[3]() Do not turn every approval into a permanent allow. The more autonomous the setup, the more boring your permission model should be.

Fifth, prefer narrow tools over giant tool clouds. A giant all-purpose connector looks impressive until Claude has to choose between dozens of overlapping actions. Narrow servers, specific skills, and clear commands usually produce better outcomes.

Sixth, test every install in a disposable repo. Anthropic’s public skills repository explicitly says example skills are for demonstration and education and should be tested before critical use.[4]() Treat third-party plugins, skills, and MCP servers the same way you treat npm packages that can touch your filesystem or accounts.

Seventh, version your workflow. Keep .mcp.json, plugin choices, skills, and [CLAUDE.md](http://CLAUDE.md) under review like any other part of your engineering or operations stack. If a workflow breaks, you need to know what changed.

**Best Practices for Each Layer**

|Layer|Best Practice|Why Most People Miss It|
|:-|:-|:-|
|[CLAUDE.md](http://CLAUDE.md)|Keep it short, durable, and project-specific.|People turn it into a junk drawer of every instruction they ever wrote.|
|Skills|Use skills for repeatable workflows, reference material, and domain judgment.|People paste the same prompt 50 times instead of turning it into a reusable procedure.|
|Plugins|Use plugins when you want to distribute a bundle of capabilities across projects.|People think plugins are “just add-ons,” but they can bundle skills, agents, hooks, MCP servers, LSP servers, and more.[5]()|
|MCP servers|Connect only trusted systems, then scope permissions carefully.|People forget MCP is not just context. It can be access.|
|Hooks|Use hooks only for actions that should happen every time.|People automate too early, then spend more time debugging automation than doing work.|
|Subagents|Use subagents for noisy research, review, or parallel work that should not pollute the main thread.|People cram everything into the main conversation and wonder why context gets messy.|
|LSP / code intelligence|Add language servers for large typed codebases.|People rely on grep when Claude needs symbol-level navigation and diagnostics.|

The cleanest setup is usually layered like this:

[1.CLAUDE.md](http://1.CLAUDE.md) explains the project’s non-negotiables.

2.Skills encode repeatable workflows.

3.Plugins package reusable capability bundles.

4.MCP connects the outside tools Claude needs.

5.Hooks automate checks that should always run.

6.Subagents handle noisy or isolated work.

That sequence prevents “agent sprawl.”

# Things Most People Miss

They miss that skills are not just prompts. Skills can package instructions, metadata, scripts, templates, and supporting resources. Anthropic describes a progressive disclosure model where Claude loads lightweight metadata first, then skill instructions when relevant, and extra files only as needed.[4]() That means a good skill can be much more durable than a clever prompt.

They miss that MCP is a trust boundary. MCP servers can connect Claude to external systems and data sources.[2]() That is exactly why they are useful and exactly why they require caution. Official docs warn users to verify trust before connecting servers, especially when servers fetch external content that may introduce prompt-injection risk.[2]()

They miss that plugins are packaging, not magic. A plugin can bundle skills, agents, hooks, MCP servers, LSP servers, monitors, and themes.[5]() That is powerful, but you still need to understand what the plugin installs, what it can access, and when Claude might invoke it.

They miss that better installs do not fix vague instructions. If your task is unclear, a larger stack just gives Claude more ways to wander. The best power users still write crisp goals, constraints, acceptance criteria, and examples.

They miss the review loop. A Claude Code setup should be reviewed like a security policy. Audit permissions. Remove stale MCP servers. Delete skills you no longer use. Pin or document versions when stability matters.

They miss that “humanizer” should be the last step, not the first. Do not use a humanizer to disguise weak thinking. Use it after the structure, claims, evidence, and examples are already strong.

They miss that live web search is not a substitute for sources. A perplexity-style MCP can help Claude find current facts, but you still need source links, dates, and verification before publishing.

They miss that Zapier is an action surface. Connecting Claude to thousands of app actions is powerful. It also means a sloppy prompt can create sloppy drafts, tasks, updates, emails, or records. Put approvals in the loop for anything external-facing.

# A Safe Install Order

If I were starting from zero, I would not install the whole list at once. I would build in this order.

|Step|What to Add|Why|
|:-|:-|:-|
|1|Claude Code plus [CLAUDE.md](http://CLAUDE.md)|Establish project rules before adding more capability.|
|2|One workflow skill|Convert your most repeated prompt into a repeatable process.|
|3|One dev plugin|Add broad productivity once the base rules are stable.|
|4|One design or domain skill|Improve the specific output quality you care about most.|
|5|One MCP server|Connect the app you copy from most often.|
|6|One automation MCP|Add Zapier or Slack only after you know what actions Claude should take.|
|7|Hooks and subagents|Add automation and isolation after the workflow proves itself manually.|

The rule is simple: do not install an add-on until you can name the repeated pain it removes.

**My Shortlist by Persona**

If you are a developer, start with gstack, superpowers, frontend-design, and antfu-skills. Add agent-browser when you need web-app testing or browser workflows. Add perplexity when fresh docs or current research matter.

If you are a marketer or creator, start with marketingskills, social-media-skills, claude-seo, humanizer, and hyperframes. Add higgsfield if video is part of your content pipeline.

If you are an operator, start with granola, notion, slack, and zapier. This is where Claude becomes useful for meeting notes, action items, doc updates, status reports, and workflow glue.

If you are in finance or law, start with the domain plugin first, then add research and document workflows. Specialist vocabulary matters in those fields. Generic assistant behavior is not enough.

If you are building a personal knowledge system, start with ai-second-brain, notebooklm-skill, perplexity, and notion. Your goal is not more chat. Your goal is retrieval, synthesis, and reuse.

**The Security Rule I Would Not Ignore**

Treat every install as a new permission conversation.

Claude Code has security protections, permission prompts, command review, trust verification, and scoped behavior.[3]() But those protections do not remove your responsibility to review commands, verify critical file changes, avoid piping untrusted content into tools, and be cautious with external services.[3]()

That matters most for MCP.

If an MCP server can read private docs, send Slack messages, draft emails, update Notion, trigger Zapier actions, or browse authenticated sites, it deserves the same scrutiny as a new employee with app access.

  


24 Claude Code installs that turn it from coding assistant into an operating system.