add-page
Skill2 starsChanged 22 days agoMITView on GitHub
Add or change a page (route) in this repo's UI, with its accessibility, keyboard and Lighthouse obligations. Use when creating a file in src/routes, adding a form or a new UI state to a page, or when the routes gate of pnpm check fails.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- davision0102/fabriktheir own version, first seen Nov 15, 2026
- getvibekits/vibe-coding-rulestheir own version, first seen Oct 25, 2026
- DailybotHQ/deepworkplan-websitetheir own version, first seen Oct 9, 2026
- astashov/liftosaurtheir own version, first seen Oct 8, 2026
- AnitChaudhry/10x-development-teamtheir own version, first seen Mar 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- astashov/liftosaur★ 775same name
- DailybotHQ/deepworkplan-website★ 15same name
- davision0102/fabrik★ 3same name
- AnitChaudhry/10x-development-team★ 0same name
- getvibekits/vibe-coding-rules★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-featureSkill
- api-changeSkill
- auth-changeSkill
- database-changeSkill
- shadcnSkill
- upgrade-prerelease-depsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Static page: add its path to nitro({ prerender: { routes } }) in vite.config.ts (ADR 0004).
- Very specific: line 25
Every control has a visible label.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add a page
Steps
- Route file in
src/routes/(kebab-case; TanStack prefixes such as_authed/for signed-in pages). It holds the route definition (loader,beforeLoad,head,headers,validateSearch) and a small page component that composes features. Forms, buttons with behavior and lists live insrc/features/<name>/components/, data access insrc/features/<name>/api/. - Head: a
<title>throughhead(). Head scripts and styles also go throughhead()so the router adds the CSP nonce. Style with Tailwind classes only: no policy allows'unsafe-inline', sostyleattributes and inline event handlers fail the prerender build and are blocked on SSR pages (ADR 0010). - Errors: a route with a loader sets
errorComponenttoRouteErrorwith its owntitleandaction(as/dashboard,/account). A section that can fail on its own is wrapped inSectionErrorBoundary, and reads its suspense query inside the boundary (MyPostList). - Static page: add its path to
nitro({ prerender: { routes } })invite.config.ts(ADR 0004). - Forms:
useAppFormvalidating with the input's Effect Schema, loaded on first interaction throughlazyFormSchema(see "Forms" insrc/features/AGENTS.md). Every control has a visible label. A button whose action is pending setsaria-disabledand ignores presses, so it keeps focus (adisabledbutton loses it). - Accessibility tests (
tests/unit/route-coverage.test.tsinpnpm checkfails without all three):- an entry in
STATESintests/e2e/a11y.spec.tsfor the page and each new UI state (axe, WCAG 2.2 AA); - a landmark snapshot in the
landmarksblock oftests/e2e/landmarks.spec.ts; - a row in the tab-order table of
tests/e2e/keyboard.spec.tsif the page has controls.
- an entry in
- Component tests for pending, disabled, error and limit states:
renderInApp(ui, { route })mounts the real route file (readtests/component/AGENTS.mdandtests/e2e/AGENTS.md). - Lighthouse: a page users land on goes in
PAGESinscripts/lighthouse-policy.ts(SEO off for noindex pages). Accessibility, best practices and SEO must score 100, performance a median of 99; the policy is in docs/agents/gates.md.
Done when
pnpm check passes, pnpm build && pnpm verify:app passes, and for a page in PAGES,
pnpm build && pnpm lighthouse --page=<name> passes.
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.

