How do I install Claude Code Best Practice?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Claude Code Best Practice need an API key?

No required environment variable is listed on this record.

What transport does Claude Code Best Practice use?

Claude Code Best Practice runs locally over stdio.

Claude Code Best Practice MCP サーバー

Q: When was Claude Code Best Practice last checked?

Last checked 2026-11-12. from vibe coding to agentic engineering - practice makes claude perfect # claude-code-best-practice from vibe coding to agentic engineering - practice makes claude perfect ![updated with Claude Code](https://img.shields.io/badge/updated_with_Claude_Code-Nov%2008%2C%202026%209%3A36%20AM%20PKT-white?style=flat&labelColor=555) <a href="https://github.com/shanraisshan/claude-code-best-practice/starg

エージェントを強化

このサーバーを追加

Install from the publisher. Not a PlugMCP endpoint.

PlugMCP で実行

キーとログ付きでコピーをホスト。

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

PlugMCP で実行

キーとログ付きでコピーをホスト。

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

起動

Server facts

Local

Transport: stdio
Last checked: 2026-11-12

Stars: 69k
Tools: —
Uptime: —

Overview

About Claude Code Best Practice

from vibe coding to agentic engineering - practice makes claude perfect # claude-code-best-practice from vibe coding to agentic engineering - practice makes claude perfect ![updated with Claude Code](https://img.shields.io/badge/updated_with_Claude_Code-Nov%2008%2C%202026%209%3A36%20AM%20PKT-white?style=flat&labelColor=555) <a href="https://github.com/shanraisshan/claude-code-best-practice/starg

Tools

No tool list yet. Remote servers get one after the first health check.

Feature	Location	Description
Subagents	`.claude/agents/<name>.md`
Commands	`.claude/commands/<name>.md`
Skills	`.claude/skills/<name>/SKILL.md`	Official Skills · Skills for Mono-repos
Workflows	`.claude/commands/weather-orchestrator.md`
Hooks	`.claude/hooks/`	Guide
MCP Servers	`.claude/settings.json`, `.mcp.json`
Plugins	distributable packages	Marketplaces · Create Marketplaces
Settings	`.claude/settings.json`	Permissions · Model Config · Output Styles · Sandboxing · Keybindings · Auto Mode Config
Status Line	`.claude/settings.json`
Memory	`CLAUDE.md`, `.claude/rules/`, `~/.claude/rules/`, `~/.claude/projects/<project>/memory/`	Auto Memory · Auto Memory Deep-dive · Rules
Checkpointing	automatic (file-edit tracking)
Sessions	`--resume`, `--continue`, `/resume`, `/branch`
Context Window	`/compact`, `/clear`, `/context`
CLI Startup Flags	`claude [flags]`	Interactive Mode · Env Vars
AI Terms
Best Practices		Prompt Engineering · Extend Claude Code
Prompt Library

Feature	Location	Description
Ultrareview	`/code-review ultra`, `claude ultrareview [target]`	Tasks tracking
Devcontainers	`.devcontainer/`
Channels	`--channels`, plugin-based	Reference
No Flicker Mode	`/tui fullscreen`, `CLAUDE_CODE_NO_FLICKER=1`
Auto Mode	`--permission-mode auto`, `Shift+Tab`	Blog
Power-ups	`/powerup`
Fast Mode	`/fast`, `"fastMode": true`
Advisor	`/advisor`, `advisorModel`, `--advisor`	Blog
Computer Use	`computer-use` MCP server	Desktop
Agent SDK	`npm` / `pip` package	Quickstart · Examples
Ralph Wiggum Loop	plugin
Chrome	`--chrome`, extension
Claude Code Web	`claude.ai/code`	Routines
Artifacts	`/share`, `Artifact` tool
Slack	`@Claude` in Slack
Code Review	GitHub App (managed)	Blog Local /code-review
GitHub Actions	`.github/workflows/`	GitLab CI/CD
Remote Control	`/remote-control`, `/rc`	Headless Mode
Deep Links	`claude-cli://open?repo=…&q=…`
Dynamic Workflows	`/workflows`, `ultracode` keyword, `/effort ultracode`, `.claude/workflows/`	Deep Research
Agent Teams	built-in (env var)
Agent View	`claude agents`, `--bg`, `/bg`
Cross-Session Messaging	`SendMessage`, `ListAgents`, `/list-agents`
Scheduled Tasks	`/loop`, `/schedule`, cron tools	Desktop scheduled tasks · Announcement
Routines	`claude.ai/code/routines`, `/schedule`	Desktop Tasks
Tasks	`/tasks`, `~/.claude/tasks/`	Ultrareview tracking
Goal	`/goal <condition>`, `/goal clear`
Voice Dictation	`/voice`
Bundled Skills	`/code-review`, `/batch`
Git Worktrees	`--worktree`/`-w`, `.worktreeinclude`, `EnterWorktree`/`ExitWorktree`, `isolation: "worktree"`, `WorktreeCreate`/`WorktreeRemove` hooks

Name	★	Workflow
Matt Pocock Skills	318k	→ → → → → → →	0	0	39
Superpowers	314k	→ → → → → → →	0	0	15
Everything Claude Code	299k	→ → → → → →	71	112	314
Spec Kit	148k	→ → → → →	0	10	0
gstack	141k	→ → → → → → → → → →	0	0	64
agent-skills	99.7k	→ → → → →	3	7	21
OpenSpec	74.2k	→ → → →	0	12	12
Get Shit Done	64.2k	→ → → → → → →	33	85	0
BMAD-METHOD	55.1k	→ → → → → →	6	0	33
oh-my-claudecode	40.7k	→ → → → → → → →	19	21	48
Compound Engineering	26k	→ → → → →	0	1	37
HumanLayer	12.8k	→ → → → →	0	0	28

Name	★	Type	Bridges to	What it does
musistudio/claude-code-router	34k	Router	OpenRouter, DeepSeek, Ollama, Gemini, Kimi, Qwen, Groq, +more	Routes Claude Code's API to any compatible provider, with per-task model selection
router-for-me/CLIProxyAPI	32k	Router	Gemini CLI, Codex, Claude Code, Antigravity	Wraps each CLI as an OpenAI/Gemini/Claude/Codex-compatible API service
openai/codex-plugin-cc	18k	Plugin	Codex / GPT-5	Official OpenAI plugin: `/codex:review`, `/codex:adversarial-review`, `/codex:rescue` inside Claude Code
BeehiveInnovations/pal-mcp-server	12k	MCP	Gemini, OpenAI, Azure, Grok, Ollama, OpenRouter (50+ models)	Multi-model MCP server (formerly `zen-mcp-server`) — call other models as Claude tools

Name	★
mattpocock/skills	317k	31
anthropics/skills	188k	19
Egonex-AI/Understand-Anything	67k	8
scientific-agent-skills	56k	177
wshobson/agents	42k	185
awesome-agent-skills	37k	1,497+ (curated list)
impeccable	27k	1 (with 7 design domain references)
agent-skills	27k	21
claude-skills	15k	246 (across 9 domains)
shanraisshan/draw-json-architecture-skill	3	1

Claude Code Best Practice

このサーバーを追加

キーとログ付きでコピーをホスト。

Server facts

About Claude Code Best Practice

Tools

Questions

How do I install Claude Code Best Practice?

Does Claude Code Best Practice need an API key?

What transport does Claude Code Best Practice use?

When was Claude Code Best Practice last checked?

Documentation

claude-code-best-practice

Key features

🧠 CONCEPTS

🔥 Hot

⚙️ DEVELOPMENT WORKFLOWS

Others

🔀 CROSS-MODEL WORKFLOWS

🧰 SKILL COLLECTIONS

🤖 AGENT COLLECTIONS

💡 TIPS AND TRICKS (83)

Tips from Claude code CLI binary

🎬 VIDEOS / PODCASTS

🔔 SUBSCRIBE

☠️ STARTUPS / BUSINESSES

🤔 Does code matter?

REPORTS

Star History

Other Repos

Developed by

Extras

Sponsor My Work

Name	★
msitarzewski/agency-agents	167k	283
VoltAgent/awesome-claude-code-subagents	26k	170 (curated list)

Tip	Source
challenge Claude — "grill me on these changes and don't make a PR until I pass your test." or "prove to me this works" and have Claude diff between main and your branch 🚫👶
after a mediocre fix — "knowing everything you know now, scrap this and implement the elegant solution" 🚫👶
Claude fixes most bugs by itself — paste the bug, say "fix", don't micromanage how 🚫👶

Tip	Source
always start with plan mode
start with a minimal spec or prompt and ask Claude to interview you using AskUserQuestion tool, then make a new session to execute the spec
always make a phase-wise gated plan, with each phase having multiple tests (unit, automation, integration)
break PRDs into vertical slices (tracer bullets) that cross all layers (DB + service + UI) — AI defaults to horizontal phasing (DB phase, then API phase, then frontend phase) which delays end-to-end feedback until the last phase. From the Pragmatic Programmer 🚫👶
spin up a second Claude to review your plan as a staff engineer, or use cross-model for review
write detailed specs and reduce ambiguity before handing work off — the more specific you are, the better the output
prototype > PRD — build 20-30 versions instead of writing specs, the cost of building is low so take many shots

Tip	Source
context rot kicks in around ~300-400k tokens on the 1M context model — don't let sessions drift past that for intelligence-sensitive work
dumb zone kicks in around ~40% context — "you hit this point where you have degrading results". Newcomers: "shoot to keep it under 40%, and if you get up to 60%, think about wrapping it up". Experienced: "aggressively keep it below 30%" — push to 60% only on simple tasks. Manual /compact or /clear to reset when switching tasks
rewind > correct — double-Esc or /rewind back to before the failed attempt and re-prompt with what you learned, instead of leaving failed attempts + corrections polluting context 🚫👶
/compact with a hint (/compact focus on the auth refactor, drop the test debugging) beats letting autocompact fire — the model is at its least intelligent point when auto-compacting due to context rot
use subagents for context management — ask yourself "will I need this tool output again, or just the conclusion?" — 20 file reads + 12 greps + 3 dead ends stay in the child's context, only the final report returns 🚫👶

Tip	Source
every turn is a branching point — after Claude ends a turn, pick between Continue, /rewind, /clear, /compact, or Subagent based on how much existing context you need to carry forward
new task = new session — related tasks (e.g. writing docs for what you just built) can reuse context for efficiency, but genuinely new tasks deserve a fresh session
use "summarize from here" before rewinding to have Claude write a handoff message — like a note to the previous iteration of Claude from its future self
/compact vs /clear — compact is lossy but momentum-friendly (mid-task, fuzzy details ok); /clear + brief is more work but you control exactly what carries forward (high-stakes next step)
use recaps for long-running sessions — short summaries of what Claude did and what's next, useful when returning after minutes or hours. Disable with recaps in /config
/rename important sessions (e.g. [TODO - refactor task]) and /resume them later — label each instance when running multiple Claudes simultaneously

Tip	Source
CLAUDE.md should target under 200 lines per file. 60 lines in humanlayer (still not 100% guaranteed)
.claude/rules/*.md auto-load into every session like CLAUDE.md — add paths: YAML frontmatter to lazy-load them only when Claude touches files matching the glob
wrap domain-specific CLAUDE.md rules in <important if="..."> tags to stop Claude from ignoring them as files grow longer
use multiple CLAUDE.md for monorepos — ancestor + descendant loading
use .claude/rules/ to split large instructions
any developer should be able to launch Claude, say "run the tests" and it works on the first try — if it doesn't, your CLAUDE.md is missing essential setup/build/test commands
keep codebases clean and finish migrations — partially migrated frameworks confuse models that might pick the wrong pattern
use settings.json for harness-enforced behavior (attribution, permissions, model) — don't put "NEVER add Co-Authored-By" in CLAUDE.md when attribution.commit: "" is deterministic

Tip	Source
have feature specific sub-agents (extra context) with skills (progressive disclosure) instead of general qa, backend engineer
say "use subagents" to throw more compute at a problem — offload tasks to keep your main context clean and focused 🚫👶
agent teams with tmux and git worktrees for parallel development
use test time compute — separate context windows make results better; one agent can cause bugs and another (same model) can find them

Tip	Source
use commands for your workflows instead of sub-agents
use slash commands for every "inner loop" workflow you do many times a day — saves repeated prompting, commands live in .claude/commands/ and are checked into git
if you do something more than once a day, turn it into a skill or command — build /techdebt, context-dump, or analytics commands

Tip	Source
use context: fork to run a skill in an isolated subagent — main context only sees the final result, not intermediate tool calls. The agent field lets you set the subagent type
use skills in subfolders for monorepos
skills are folders, not files — use references/, scripts/, examples/ subdirectories for progressive disclosure
build a Gotchas section in every skill — highest-signal content, add Claude's failure points over time
skill description field is a trigger, not a summary — write it for the model ("when should I fire?")
don't state the obvious in skills — focus on what pushes Claude out of its default behavior 🚫👶
don't railroad Claude in skills — give goals and constraints, not prescriptive step-by-step instructions 🚫👶
include scripts and libraries in skills so Claude composes rather than reconstructs boilerplate
embed !command in SKILL.md to inject dynamic shell output into the prompt — Claude runs it on invocation and the model only sees the result

Tip	Source
use on-demand hooks in skills — /careful blocks destructive commands, /freeze blocks edits outside a directory
measure skill usage with a PreToolUse hook to find popular or undertriggering skills
use a PostToolUse hook to auto-format code — Claude generates well-formatted code, the hook handles the last 10% to avoid CI failures
route permission requests to Opus via a hook — let it scan for attacks and auto-approve safe ones 🚫👶
use a Stop hook to nudge Claude to keep going or verify its work at the end of a turn

Tip	Source
use /model to select model and reasoning, /context to see context usage, /usage to check plan limits, /extra-usage to configure overflow billing, /config to configure settings — use Opus for plan mode and Sonnet for code to get the best of both
always use thinking mode true (to see reasoning) and Output Style Explanatory (to see detailed output with ★ Insight boxes) in /config for better understanding of Claude's decisions
use ultrathink keyword in prompts for high effort reasoning
/focus mode hides all intermediate work and shows only the final result — trust the model to run the right commands and just look at the outcome (toggle with /focus)
tune effort level with Opus 4.7's adaptive thinking — low for speed and fewer tokens, max for most intelligence (slider: low · medium · high · xhigh · max)

Tip	Source
keep PRs small and focused — p50 of 118 lines (141 PRs, 45K lines changed in a day), one feature per PR, easier to review and revert
always squash merge PRs — clean linear history, one commit per feature, easy git revert and git bisect
commit often — try to commit at least once per hour, as soon as task is completed, commit
tag @claude on a coworker's PR to auto-generate lint rules for recurring review feedback — automate yourself out of code review 🚫👶
use /code-review for multi-agent PR analysis — catches bugs, security vulnerabilities, and regressions before merge

Tip	Source
make it a habit to take screenshots and share with Claude whenever you are stuck with any issue
use mcp (Claude in Chrome, Playwright, Chrome DevTools) to let claude see chrome console logs on its own
always ask claude to run the terminal (you want to see logs of) as a background task for better debugging
/doctor to diagnose installation, authentication, and configuration issues
use a cross-model for QA — e.g. Codex for plan and implementation review
agentic search (glob + grep) beats RAG — Claude Code tried and discarded vector databases because code drifts out of sync and permissions are complex

Tip	Source
iTerm/Ghostty/tmux terminals instead of IDE (VS Code/Cursor)
/voice or Wispr Flow for voice prompting (10x productivity)
claude-code-hooks for claude feedback
status line for context awareness and fast compacting
explore settings.json features like Plans Directory, Spinner Verbs for a personalized experience

Tip	Source
use ASCII diagrams a lot to understand your architecture
use /loop for local recurring monitoring (up to 7 days) · use /schedule for cloud-based recurring tasks that run even when your machine is off
use Ralph Wiggum plugin for long-running autonomous tasks
/permissions with wildcard syntax (Bash(npm run ), Edit(/docs/*)) instead of dangerously-skip-permissions
/sandbox to reduce permission prompts with file and network isolation — 84% reduction internally
invest in product verification skills (signup-flow-driver, checkout-verifier) — worth spending a week to perfect
use auto mode instead of dangerously-skip-permissions — a model-based classifier decides if each command is safe and auto-approves, pauses and asks if risky. Shift+Tab to cycle Ask → Plan → Auto modes 🚫👶
use /less-permission-prompts skill to scan session history for safe bash/MCP commands that repeatedly prompt, then get a recommended allowlist to paste into settings
build a /go skill that (1) tests end-to-end via bash/browser/computer use (2) runs /simplify (3) puts up a PR — so when you come back, you know the code works 🚫👶

Tip	Source
update Claude Code daily
start your day by reading the changelog

Article / Tweet	Source
6 Tips for Getting More Out of Opus 4.7 (Boris) \| 16/Apr/26	Tweet
Session Management & 1M Context (Thariq) \| 16/Apr/26	Tweet
15 Hidden & Under-Utilized Features in Claude Code (Boris) \| 30/Mar/26	Tweet
Squash Merging & PR Size Distribution (Boris) \| 25/Mar/26	Tweet
Lessons from Building Claude Code: How We Use Skills (Thariq) \| 17/Mar/26	Article
Code Review & Test Time Compute (Boris) \| 10/Mar/26	Tweet
/loop — schedule recurring tasks for up to 3 days (Boris) \| 07 Mar 2026	Tweet
AskUserQuestion + ASCII Markdowns (Thariq) \| 28 Feb 2026	Tweet
Seeing like an Agent - lessons from building Claude Code (Thariq) \| 28 Feb 2026	Article
Git Worktrees - 5 ways how boris is using \| 21 Feb 2026	Tweet
Lessons from Building Claude Code: Prompt Caching Is Everything (Thariq) \| 20 Feb 2026	Article
12 ways how people are customizing their claudes (Boris) \| 12/Feb/26	Tweet
10 tips for using Claude Code from the team (Boris) \| 01/Feb/26	Tweet
How I use Claude Code — 13 tips from my surprisingly vanilla setup (Boris) \| 03/Jan/26	Tweet
Ask Claude to interview you using AskUserQuestion tool (Thariq) \| 28/Dec/25	Tweet
Always use plan mode, give Claude a way to verify, use /code-review (Boris) \| 27/Dec/25	Tweet

Video / Podcast	Source	YouTube
From Vibe Coding to Agentic Engineering (Andrej) \| 02 May 2026 \| AI Engineer		YouTube
Full Walkthrough: Workflow for AI Coding (Matt) \| 24 Apr 2026 \| Matt Pocock		YouTube
Everything We Got Wrong About Research-Plan-Implement (Dex) \| 24 Mar 2026 \| MLOps Community		YouTube
Building Claude Code with Boris Cherny (Boris) \| 04 Mar 2026 \| The Pragmatic Engineer		YouTube
Head of Claude Code: What happens after coding is solved (Boris) \| 19 Feb 2026 \| Lenny's Podcast		YouTube
Inside Claude Code With Its Creator Boris Cherny (Boris) \| 17 Feb 2026 \| Y Combinator		YouTube
Boris Cherny (Creator of Claude Code) On What Grew His Career (Boris) \| 15 Dec 2025 \| Ryan Peterman		YouTube
The Secrets of Claude Code From the Engineers Who Built It (Cat) \| 29 Oct 2025 \| Every		YouTube

Source	Name	Badge
	r/ClaudeAI, r/ClaudeCode, r/Anthropic
	Claude, Claude Devs, Anthropic, Boris, Thariq, Cat, Lydia, Noah, Anthony, Alex, Kenneth
	Jesse Kriss (Superpowers), Affaan Mustafa (ECC), Garry Tan (gstack), Dex Horthy (HumanLayer), Kieran Klaassen (Compound Eng), Tabish Gilani (OpenSpec), Brian McAdams (BMAD), Lex Christopherson (GSD), Matt Pocock (Skills), Dani Avila (CC Templates), Dan Shipper (Every), Andrej Karpathy (AutoResearch), Peter Steinberger (OpenClaw), Sigrid Jin (claw-code), Yeachan Heo (oh-my-claudecode)
	Anthropic
	Lenny's Podcast, Y Combinator, The Pragmatic Engineer, Ryan Peterman, Every, MLOps Community

Claude	Replaced
Code Review	Greptile, CodeRabbit, Devin Review, OpenDiff, Cursor BugBot
Voice Dictation	Wispr Flow, SuperWhisper
Remote Control	OpenClaw
Claude in Chrome	Playwright MCP, Chrome DevTools MCP
Computer Use	OpenAI CUA
Cowork	ChatGPT Agent, Perplexity Computer, Manus
Tasks	Beads
Plan Mode	Agent OS
Design	Figma, Framer, Sketch, v0
Agent SDK	LangChain, LangGraph, CrewAI, AutoGen, OpenAI Assistants API
Skills / Plugins	YC AI wrapper startups (reddit)

#	Workflow	Description
1	/workflows:development-workflows	Update the DEVELOPMENT WORKFLOWS table and cross-workflow analysis report by researching all 10 workflow repos in parallel
2	/workflows:skill-collections	Update the SKILL COLLECTIONS table by researching all 5 skill-collection repos in parallel
3	/workflows:agent-collections	Update the AGENT COLLECTIONS table by researching all agent-collection repos in parallel
4	/workflows:best-practice:workflow-concepts	Update the README CONCEPTS section with the latest Claude Code features and concepts
5	/workflows:best-practice:workflow-claude-settings	Track Claude Code settings report changes and find what needs updating
6	/workflows:best-practice:workflow-claude-subagents	Track Claude Code subagents report changes and find what needs updating
7	/workflows:best-practice:workflow-claude-commands	Track Claude Code commands report changes and find what needs updating
8	/workflows:best-practice:workflow-claude-skills	Track Claude Code skills report changes and find what needs updating