web-kit
Skill0 starsChanged 2 days agoMITView on GitHub
Start a new website, or add/update the shared header and light/dark theme toggle in one of Sarah's 11ty sites, from ~/Documents/projects/web-kit. Use on "new site", "new website", "start a site", "add a header", "theme toggle", "dark mode toggle", "add web-kit", "update web-kit".
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- delegateSkill
- design-reviewSkill
- endSkill
- retroSkill
- review-gatesSkill
- reviewSkill
- startSkill
- working-modelSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Ask: name, slug, one-line description, folder (default ~/Documents/projects/<slug>), GitHub repo or not.
- Distinctive: line 30
Read the site's header, toggle, base layout, tokens and tests first.
- Very specific: line 34
Keep the site's icons/wordmark by moving them into wk-icon-* / wk-wordmark.
- Very specific: line 35
After the change: the site's gate, plus copy scripts/browser-check.mjs in and run it against a page that shows the header.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
web-kit
Source: ~/Documents/projects/web-kit (read its README.md for the file list and
contract). Plan, then wait, as always.
New site
- Ask: name, slug, one-line description, folder (default
~/Documents/projects/<slug>), GitHub repo or not. cp -R ~/Documents/projects/web-kit/starter <folder>, then~/Documents/projects/web-kit/scripts/copy-into.sh <folder>/src/_includes <folder>/src/assets/css/components <folder>/src/assets/js.- Replace placeholders:
SITE_NAME,SITE_SLUG,SITE_DESCRIPTION,CREATED_DATE,WEB_KIT_VERSION(grep -rlthem; none may remain). git init -b main,npm install,npm run gate(expect all pass), first commit.- Offer
frontend-designfor the visual direction; the palette intokens.cssis a placeholder until its contrast pairs are verified indocs/design-system.md.
Add to an existing site
- Read the site's header, toggle, base layout, tokens and tests first. List what the site's tests assert about them (labels, classes) — those change.
- Plan: which files to copy (
copy-into.sh, never overwrites), the token mapping block (tokens/mapping.example.css), include lines, what to delete, test updates. Keep the site's icons/wordmark by moving them intowk-icon-*/wk-wordmark. - After the change: the site's gate, plus copy
scripts/browser-check.mjsin and run it against a page that shows the header. Visual sign-off is Sarah's. - Record
web-kit <version>in the site'sPLAN.mdDecisions.
Update a site
Diff each web-kit-stamped file against web-kit; keep intentional local edits; bump the stamp; gate + browser check; record the version. Never overwrite blindly.
Change web-kit itself
Edit in ~/Documents/projects/web-kit, bump VERSION and all stamps, npm run gate,
run the browser check in a scratch site built from starter/, add a CHANGELOG line.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

