Stop 3 of 9 · Weekly
The component library
studio-kit: what earns a place in it, the documentation Claude Code reads before it writes, and how one component changes on six sites without six arguments.
Five heroes, one studio
Across twenty sites Dany's studio has built the same six pieces over and over: the sticky header, the service card, the testimonial block, the opening-hours table, the contact form with its honeypot, and the footer with the map link. Each one exists in four or five slightly different versions, and every version has its own bug.
studio-kit is one repository holding the agreed version of each. Claude Code reads it before it writes anything, which means a new build starts at seventy percent instead of zero, and a fix lands in one place.
What earns a place
Three sites need it, the behaviour is the same on all three, and it is boring. Anything that is genuinely one client's idea stays in that client's repository. A kit that collects everything becomes a second codebase nobody maintains, which is worse than no kit.
The documentation Claude Code reads
A folder of files is not a library. Each component gets a short entry in the kit's doc file, and that file is the first thing the brief points at.
| The entry says | Because otherwise |
|---|---|
| What it is and when to use it | It gets rebuilt on the next site |
| The markup and the class names | Every site invents its own names |
| The accessibility rules it already handles | Someone adds a second aria label |
| When not to use it | It gets bent into a shape it was never for |
Read the header markup and CSS in calder-ortho/, peak-roofing/ and northgate-vets/. Show me a table of what is the same and what differs across the three, then propose one component that covers all three cases without adding an option for anything only one site does. List the differences you are proposing to drop and what each site loses.
Add the agreed header to studio-kit as header/, with the markup, the CSS and a demo page that shows it at 360, 768 and 1280 pixels wide. Then add its entry to the kit doc file: what it is, when to use it, the class names, the keyboard and screen reader behaviour it already handles, and two cases where it is the wrong choice. Work on a branch and open a pull request. Do not merge.
Northgate Vets need an emergency banner above the header on every page. Extend the studio-kit header rather than forking it: one optional banner slot, the banner announced to screen readers, and no change to the markup any existing site already uses. Show me the diff, the doc entry you updated, and the demo page with the banner on and off.
The change that touches six sites
The kit changes, then each site gets its own pull request with its own preview and its own merge. Dany does not push a kit update to six sites at once. Shared code is a reason for more review, not less, because one mistake now arrives six times on a Friday.
The measurable
Two numbers, recorded on every new build. The share of the finished site that came from the kit, counted in components not lines, and the number of kit components without a doc entry. The first should climb toward two thirds over a year. The second is only ever zero.