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.
Defer to Codex
Give Codex a full writing brief and have Claude check the result against the sources before applying it.
2 files · 4 KB
Why I keep it
I prefer the words I get from Codex, so I give it the writing brief while Claude gathers the facts and checks the result. That is how I made the copy you’re reading. The split gives the writing and the evidence separate attention before anything reaches the repo.
I’ve included SKILL.md and brief-template.md, so Claude has a procedure for the handover. It checks the installed Codex CLI, writes a full brief and sends the output to scratch; Claude applies what survives the review. Codex needs to be installed and signed in.
How I use it: Let one model write and another check →Take the files
2 files · 4 KB
- SKILL.md3 KB
- brief-template.md1 KB
Keep building your setup: Skills
Back to the shelves →021 file · 9 KB
Tech lead
Keep a build moving from a plan in your repo to checks against the work running in production.
038 files · 68 KB
Carbon copy
Rebuild a live design from its DOM, styles and motion, with evidence for each section.
041 file · 13 KB
Design system
Turn repeated styles into shared tokens, typed components and written rules your agent can follow.
053 files · 24 KB
Hero writer
Give your landing page one clear visual idea, with a written brief and measured type and spacing.
062 files · 14 KB
Image parity
Build from a screenshot’s measured colours, type and geometry, with a tool to inspect the image.
See what I ship
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.