011 file · 6 KB
How I make a new skill
Tell your agent the job, the look and the stack, so it can write a skill you improve through use.
Turn repeated styles into shared tokens, typed components and written rules your agent can follow.
1 file · 13 KB
Why I keep it
A product can have a recognisable look while its CSS keeps repeating the same decisions. I keep design-system for that job: extracting tokens, promoting repeated styles into typed components and writing down their contracts, so the existing design becomes something an agent can extend consistently.
I’ve included the whole procedure in SKILL.md, from splitting the stylesheet into layers to naming spacing and motion values. It can also prepare a component registry, so you have a route from a working codebase to reusable pieces without asking the agent to invent another visual language.
How I use it: Turn repeat work into a skill →1 file · 13 KB
011 file · 6 KB
Tell your agent the job, the look and the stack, so it can write a skill you improve through use.
021 file · 9 KB
Keep a build moving from a plan in your repo to checks against the work running in production.
038 files · 68 KB
Rebuild a live design from its DOM, styles and motion, with evidence for each section.
043 files · 24 KB
Give your landing page one clear visual idea, with a written brief and measured type and spacing.
052 files · 14 KB
Build from a screenshot’s measured colours, type and geometry, with a tool to inspect the image.
0639 files · 419 KB
Turn sourced research into a branded PDF, with real interface captures and checks for overflowing pages.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.