惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
The Cloudflare Blog
大猫的无限游戏
大猫的无限游戏
小众软件
小众软件
V
Visual Studio Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
酷 壳 – CoolShell
酷 壳 – CoolShell
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
月光博客
月光博客
The GitHub Blog
The GitHub Blog
L
LangChain Blog
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
F
Fortinet All Blogs
博客园 - Franky
阮一峰的网络日志
阮一峰的网络日志
GbyAI
GbyAI
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
Engineering at Meta
Engineering at Meta
V
V2EX
MyScale Blog
MyScale Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Building a Complete Developer Terminal Setup for Claude C...
Avinash Seet · 2026-04-26 · via DEV Community

By Avinash, GenAI Practice Lead | Part 1 | Part 2 | Part 3 | Part 4 of 6


Claude Code has a growing plugin ecosystem. The temptation is to install everything — more agents, more skills, more coverage. This is the wrong approach, especially on a Pro plan.

Every plugin injects instructions into your session context at startup. A plugin with 38 agents and 156 skills adds a meaningful token overhead to every single session, whether you use those skills or not. On Pro where you're paying per input token, a bloated plugin stack is a recurring tax on every conversation.

I installed, evaluated, and removed several plugins before settling on 9 that earn their place. Here's the final stack and the reasoning behind each.


The 9 Plugins

caveman — strips filler from Claude's responses. No pleasantries, no hedging, just signal. The benchmarks show ~65% output token reduction on coding tasks. In practice the savings are real and the response style actually improves for tight coding loops — you get code and decisions, not explanations you didn't ask for. Activate with /caveman, deactivate with "normal mode" before switching to documentation or client-facing writing.

claude-mem — persistent memory across sessions. This is the most impactful plugin in the stack. Without it every Claude Code session starts completely blank — no knowledge of what you built yesterday, no context on architectural decisions made last week. With it, the session opens with a compressed summary of relevant past work injected automatically. For multi-week projects this eliminates the re-establishment overhead that quietly consumes 10-15 minutes of every session. It runs a background worker on port 37777 with a web viewer for your observation history.

code-review — 5 parallel Sonnet agents reviewing your code before pushes. Covers CLAUDE.md compliance, bug detection, historical context, PR history, and code comments simultaneously. Trigger with /code-review after any meaningful change.

pr-review-toolkit — deeper review covering tests, error handling, type design, code quality, and simplification. Use this before anything that goes into a production codebase or published whitepaper. Run with /pr-review-toolkit:review-pr all.

feature-dev — three-agent workflow for new features: explore codebase → architect solution → review quality. Reserve it for moments where you'd naturally step back and think about design before writing code. Overkill for bug fixes, well-suited for new model wrappers or evaluation dimensions.

commit-commands — auto-generates meaningful commit messages from staged changes. Replaces the cognitive overhead of writing commit messages at the end of a long session when you're tired and just want to push.

context7 — pulls current SDK documentation into context automatically when you're working with external libraries. When your code references a LiteLLM function or a Boto3 call, context7 fetches the current docs rather than relying on Claude's training data which may be stale on specific SDK versions.

taches-cc-resources — a collection of workflow commands worth knowing: /create-plans for structured project planning with PLAN.md, /debug-like-expert for systematic debugging with evidence gathering, and /ask-me-questions for requirement clarification before starting a large ambiguous task.

pyright-lsp — Python language server via Pyright. Gives Claude real-time type errors, import resolution, and go-to-definition across your codebase. Without it Claude reads files reactively when something breaks. With it, it sees problems as they exist in your code continuously.


What I Removed

everything-claude-code — 38 agents, 156 skills, 72 legacy command shims. The context footprint is enormous and the coverage largely duplicates what the targeted plugins above already handle. Removed.


Installing the Stack

Add the marketplaces first — these commands run inside a Claude Code session, not in your terminal:

/plugin marketplace add anthropics/claude-code
/plugin marketplace add anthropics/claude-plugins-official
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin marketplace add thedotmack/claude-mem
/plugin marketplace add JuliusBrussee/caveman

Enter fullscreen mode Exit fullscreen mode

Then install:

/plugin install code-review@claude-code-plugins
/plugin install pr-review-toolkit@claude-code-plugins
/plugin install feature-dev@claude-code-plugins
/plugin install commit-commands@claude-code-plugins
/plugin install context7@claude-plugins-official
/plugin install pyright-lsp@claude-plugins-official
/plugin install taches-cc-resources@taches-cc-resources
/plugin install claude-mem@thedotmack
/plugin install caveman@caveman

Enter fullscreen mode Exit fullscreen mode

Reload with /reload-plugins. Expected output: 9 plugins · 35 skills · 18 agents · 10 hooks · 2 plugin MCP servers · 1 plugin LSP server.


Quick Reference

Plugin Trigger When to use
caveman /caveman All coding sessions
claude-mem Auto Always on
code-review /code-review Before any meaningful push
pr-review-toolkit /pr-review-toolkit:review-pr Before production or published code
feature-dev /feature-dev New features requiring design thinking
commit-commands /commit-commands:commit Every commit
context7 Auto Working with external SDKs
taches-cc-resources /create-plans, /debug-like-expert Planning and complex debugging
pyright-lsp Auto Always on for Python projects

Back to Part 3 | Continue to Part 5 → Terminal Environment