Skills — teach it once and it knows forever
Do the task, get it right, then say "turn what we just did into a skill." The work becomes the training material.
Not filmed yet
The lesson is written out below. The video comes after.
The instinct is to sit down and write the perfect instructions before starting. That is the hardest possible way to do it, because you are describing a process you have not run yet.
Do it backwards. Do the task for real, in a conversation, correcting as you go until the result is actually right. Then say: turn what we just did into a skill.
What you get is a file capturing the process that genuinely worked — including the three corrections you made, which are the valuable part and the part you would never have thought to write in advance. The work was the training material all along.
After that, any future session produces the same quality by name, without you re-explaining anything. And because it is a file, you can read it, argue with it, and change one line when the process changes.
The one thing to keep
Stop writing instructions from scratch. Promote the session that worked.
More in Claude Code
Next to this one
Hooks — rules that fire without asking
Automatic tripwires, so the discipline is not left to your memory.
Claude CodePlan mode — make it think before it builds
A read-only mode where it can study and propose but cannot touch anything.
Claude CodeWhy a fresh chat beats a long one
Two reasons — cost and quality — and they both go the same direction.