Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-17 · source-backed
A GitHub repo cataloging Claude Code tips doesn't normally warrant a top story. But shanraisshan/claude-code-best-practice at 53.4K stars isn't a tips list anymore. It's the de facto reference for how an entire generation of developers is learning to work with AI coding agents.
The subtitle tells the story: "From Vibe Coding to Agentic Engineering." That framing captures something real. Twelve months ago, people were prompting AI and hoping for the best. Now the repo documents 83+ patterns for deliberate agent orchestration: subagent architecture, MCP server integration, git worktree workflows, cross-model pipelines (running Claude alongside Codex or Gemini), and progressive skill disclosure. Updated for Claude Code v2.1.142 as of this month.
The pattern I keep pulling from it is Command, Agent, Skill. Commands for one-shot operations. Agents for multi-step work requiring judgment. Skills for reusable domain-specific workflows that encode your team's best practices. This three-tier architecture has quietly become the standard for anyone doing serious work with coding agents.
What makes 53K stars significant isn't the number itself. It's what it represents: tens of thousands of developers actively shifting from "type a prompt and see what happens" to "architect how the agent thinks, acts, and recovers from errors." That's a different discipline. It's closer to systems design than prompt engineering.
For builders who haven't looked at this repo yet, start with the subagent orchestration section. The pattern of running parallel exploration on cheaper models (Sonnet), then converging to single-threaded editing on Opus, has saved me real money and real time.
Each link below shares sources, entities, or timing with this story.
Cursor uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cursor uses Opus); both cover Claude Code, Codex, Gemini, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Cursor uses Opus); both cover Claude Code, Codex, GitHub, MCP; reported by the same outlet (github.com).
Cursor uses Opus / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses Opus); both cover Claude, Claude Code, GitHub, SKILL; reported by the same outlet (github.com).
Linked by a graph relationship (Cursor uses Opus); both cover Claude, Claude Code, Codex, GitHub; reported by the same outlet (github.com).
Cursor uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cursor uses Opus); both cover CLAUDE, Claude Code, Codex, SKILL; reported by the same outlet (github.com).
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, Codex, GitHub, MCP; reported by the same outlet (github.com).
Cursor uses Opus / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Cursor uses Opus); both cover Claude Code, Codex, GitHub, Stars; reported by the same outlet (github.com).
Cursor uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cursor uses Opus); both cover CLAUDE, Claude Code, Codex, GitHub; reported by the same outlet (github.com).