6 posts · page 1/1
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.
Most AI-built apps die in the gap between 'works on my laptop' and 'ten real users on Monday.' The gap is nine specific lines, almost none of them about the model. Where each line sits, and the cheapest move that crosses it.
Implementation got fast, and the cheap alignment touchpoints went with it. Now every 'should we be building this?' fight lands on the PR review — which was never built to carry it. Patterns that shift alignment back to the left without waiting for new tools.