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.
Keep a build moving from a plan in your repo to checks against the work running in production.
1 file · 9 KB
Why I keep it
I keep build decisions beside the code in DECISIONS.md, BACKLOG.md and individual PRDs, so a new session can pick up the next agreed piece. Tech-lead gives that work its routine. I use its plan layout for WithSeismic and the skill for product work on Vouchernaut.
I’ve kept the workflow in one SKILL.md, from acceptance criteria to deployment order and live checks. It reads the diff and checks the surface rather than accepting an agent’s report, so finishing a task includes seeing the result where a user will meet it.
How I use it: Keep the plan with the work →1 file · 9 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.
028 files · 68 KB
Rebuild a live design from its DOM, styles and motion, with evidence for each section.
031 file · 13 KB
Turn repeated styles into shared tokens, typed components and written rules your agent can follow.
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.