9 posts · page 1/1
Skills aren't a freeform format. The useful ones fit one of five shapes — sequential workflow, multi-MCP coordination, iterative refinement, context-aware selection, domain-specific intelligence. Picking the right shape is most of the design work. Picking the wrong one is most of the bugs.
Most teams ship one of these and call the job done. MCP gives the agent tools. Skills tell it which to use, in what order, with which fallbacks. Without skills, your MCP integration ends with users asking 'okay, what now?'
Skills load in three levels — frontmatter, body, linked references. Most authors compress all three into one. The result is a 12,000-word SKILL.md the agent reads top to bottom whether it needs to or not, paying for the whole thing in context every time.
Every skill lives or dies by a single line in the frontmatter. If the description doesn't trigger, the instructions never load. Most authors spend an hour on a beautiful body and ten seconds on the line that decides whether anyone ever reads it.
Memory, skills, hooks, subagents, plugins. Five layers in a strict order, each earning a specific payoff, each a mistake if you reach for it before a symptom asks for it. The honest part of the ladder is the rungs you don't climb yet.
Most Claude Code shortcut listicles rank commands alphabetically and call it a day. Half of them never earn the keystroke. Eight commands and four keyboard moves cover most sessions — the honest part of the list is which twenty you can skip.
Seven architectural layers sit between you and the model in Claude Code, and each one is load-bearing. Here's what every layer actually buys you when you're eight hours into a refactor — and what specifically breaks when a tool pretends it doesn't need one.
Anthropic shipped /fork in Claude Code v2.1.117 — a subagent that inherits the entire parent conversation instead of a compressed handoff prompt. The obvious read is "subagents but better." It's wrong. Forks and regular subagents sit at opposite ends of a single axis: context inheritance. The blank slate was never a bug. Here's the decision rule.
Ten repos that genuinely change how I work with Claude Code — and a suggested order for adopting them. Install one, use it for a week, keep only the ones that stuck. Never install a bundle.