Takeaways

Docs are for humans. Skills are for agents. And the skill is extracted from your docs and code: not written instead of them. You keep writing docs the way you always have. The skill is what an agent reads when it builds.

The real value

The most useful thing a design-system skill encodes isn't the components: it's the anti-patterns. Anyone can list 19 components. The skill proves its worth when it says don't do this, and here is what to do instead.

You saw this in The Audit: a citation resolved to a real file and still said the wrong thing. That false claim is exactly the kind of anti-pattern the skill should encode. Catch it once, write it down, and no future run repeats it.

Your next move

You're somewhere on the Three Frames curve. Find where you are, then take one step.

• No skill yet → Adaptation. Point the meta-skill at your design system this week. Get a first draft on disk.
• Thin skill → Extraction. You have a stub. Fill it in: components, props, the anti-patterns you keep hitting.
• Alive but the loop's open → Cultivation. It works, but nothing feeds fixes back in. Close that loop.

A living document

A skill is a living document. Find a false claim, fix it, and the skill gets better. The next run is grounded where the last one drifted.