new-page
Skill234 starsChanged 3 months agoMITView on GitHub
Create a frontend page with routing, i18n, and navigation
10 other projects use a version of this.
Adopted by
Most recently taken up by
- 5hirish/ducttheir own version, first seen Nov 8, 2026
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- Anglesite/anglesite-skillstheir own version, first seen Oct 27, 2026
- fangyuting/skillstheir own version, first seen Oct 11, 2026
- justrach/merjstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use new-component and security-audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
violacaseSkillnew-component
Scaffold a new Vue 3 component using reka-ui primitives and Tailwind CSS. Use when the user asks to create a component, UI element, widget, or any .vue file in the components/ directory.
Also in 3 projects that use this
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- ethereum/ethereum-org-website★ 6ksame name
- justrach/merjs★ 357same name
- Anglesite/anglesite-skills★ 15same name
- robritacca-dotcom/rift-ds★ 9same name
- 5hirish/duct★ 8same name
- kkhh26864/claude-skills★ 3same name
- agamarora/second-brain★ 2same name
- fangyuting/skills★ 1same name
- robritacca-dotcom/design-system★ 1same name
- mark2685/agent-tools★ 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 repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-options-classSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- init-verifySkill
- manage-file-storageSkill
- new-endpointSkill
- new-entitySkill
- new-featureSkill
- polish-uiSkill
- review-dependabotSkill
- review-designSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 2 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use these as starting points - fill in the specifics from context:
- Very specific: line 17
Button layout: All action/submit buttons use w-full sm:w-auto with wrapper flex flex-col gap-2 sm:flex-row sm:justify-end.
- Very specific: line 23
Create feature folder: src/frontend/src/lib/components/{feature}/
- Very specific: line 24
Create components with interface Props + $props()
- Very specific: line 25
Create barrel index.ts exporting all components
- Very specific: line 29
Create route directory: src/frontend/src/routes/(app)/{feature}/
- Very specific: line 31
Create +page.svelte with <svelte:head> using i18n title
- Very specific: line 32
If server data needed: create +page.server.ts using createApiClient(fetch, url.origin)
- Very specific: line 33
If admin page: add entry to adminRoutes in $lib/config/routes.ts with path and permission
- Very specific: line 34
If permission-guarded: add check in +page.server.ts:
- Distinctive: line 41
Add i18n keys to the correct feature file in all locale directories
- Very specific: line 42
Add navigation entry in AppSidebar.svelte (using adminRoutes.feature.path and .permission for admin pages)
- Very specific: line 43
Add matching entry in CommandPalette.svelte (using adminRoutes.feature.path and .permission for admin pages)
- Very specific: line 44
If public page: add route to publicRoutes in src/frontend/src/routes/sitemap.xml/+server.ts
“Common” is measured: kept by at least 6 in 10 of the 8 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
Creates a new frontend page with routing, i18n, and navigation.
Infers route, route group, components needed, and data requirements from context. Defaults to (app) (authenticated). Asks only if genuinely ambiguous.
Templates
Use these as starting points - fill in the specifics from context:
- Page and component templates
Conventions
- Button layout: All action/submit buttons use
w-full sm:w-autowith wrapperflex flex-col gap-2 sm:flex-row sm:justify-end. Default size only (nosize="sm"orsize="lg").
Steps
Components (if needed):
- Create feature folder:
src/frontend/src/lib/components/{feature}/ - Create components with
interface Props+$props() - Create barrel
index.tsexporting all components
Page:
- Create route directory:
src/frontend/src/routes/(app)/{feature}/- Or
(public)/{feature}/for unauthenticated pages
- Or
- Create
+page.sveltewith<svelte:head>using i18n title - If server data needed: create
+page.server.tsusingcreateApiClient(fetch, url.origin) - If admin page: add entry to
adminRoutesin$lib/config/routes.tswith path and permission - If permission-guarded: add check in
+page.server.ts:if (!hasPermission(user, adminRoutes.feature.permission)) throw redirect(303, routes.dashboard);
Integration:
- Add i18n keys to the correct feature file in all locale directories
- Add navigation entry in
AppSidebar.svelte(usingadminRoutes.feature.pathand.permissionfor admin pages) - Add matching entry in
CommandPalette.svelte(usingadminRoutes.feature.pathand.permissionfor admin pages) - If public page: add route to
publicRoutesinsrc/frontend/src/routes/sitemap.xml/+server.ts
Verify and commit:
cd src/frontend && pnpm run format && pnpm run lint && pnpm run check- fix errors, loop until green- Commit:
feat({feature}): add {feature} page
Paraglide module errors (~32) are expected at check time - ignore those. Fix everything else.
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.

