agentleFS
fpindejfpindej/netrock/.claude/skills/new-page/SKILL.md

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

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.
  • violacaseSkill

    new-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

  • CloudflareSkill

    security-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

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
  1. Distinctive:

    Use these as starting points - fill in the specifics from context:

    line 12
  2. Very specific:

    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.

    line 17
  3. Very specific:

    Create feature folder: src/frontend/src/lib/components/{feature}/

    line 23
  4. Very specific:

    Create components with interface Props + $props()

    line 24
  5. Very specific:

    Create barrel index.ts exporting all components

    line 25
  6. Very specific:

    Create route directory: src/frontend/src/routes/(app)/{feature}/

    line 29
  7. Very specific:

    Create +page.svelte with <svelte:head> using i18n title

    line 31
  8. Very specific:

    If server data needed: create +page.server.ts using createApiClient(fetch, url.origin)

    line 32
  9. Very specific:

    If admin page: add entry to adminRoutes in $lib/config/routes.ts with path and permission

    line 33
  10. Very specific:

    If permission-guarded: add check in +page.server.ts:

    line 34
  11. Distinctive:

    Add i18n keys to the correct feature file in all locale directories

    line 41
  12. Very specific:

    Add navigation entry in AppSidebar.svelte (using adminRoutes.feature.path and .permission for admin pages)

    line 42
  13. Very specific:

    Add matching entry in CommandPalette.svelte (using adminRoutes.feature.path and .permission for admin pages)

    line 43
  14. Very specific:

    If public page: add route to publicRoutes in src/frontend/src/routes/sitemap.xml/+server.ts

    line 44

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-auto with wrapper flex flex-col gap-2 sm:flex-row sm:justify-end. Default size only (no size="sm" or size="lg").

Steps

Components (if needed):

  1. Create feature folder: src/frontend/src/lib/components/{feature}/
  2. Create components with interface Props + $props()
  3. Create barrel index.ts exporting all components

Page:

  1. Create route directory: src/frontend/src/routes/(app)/{feature}/
    • Or (public)/{feature}/ for unauthenticated pages
  2. Create +page.svelte with <svelte:head> using i18n title
  3. If server data needed: create +page.server.ts using createApiClient(fetch, url.origin)
  4. If admin page: add entry to adminRoutes in $lib/config/routes.ts with path and permission
  5. If permission-guarded: add check in +page.server.ts:
    if (!hasPermission(user, adminRoutes.feature.permission)) throw redirect(303, routes.dashboard);

Integration:

  1. Add i18n keys to the correct feature file in all locale directories
  2. Add navigation entry in AppSidebar.svelte (using adminRoutes.feature.path and .permission for admin pages)
  3. Add matching entry in CommandPalette.svelte (using adminRoutes.feature.path and .permission for admin pages)
  4. If public page: add route to publicRoutes in src/frontend/src/routes/sitemap.xml/+server.ts

Verify and commit:

  1. cd src/frontend && pnpm run format && pnpm run lint && pnpm run check - fix errors, loop until green
  2. Commit: feat({feature}): add {feature} page

Paraglide module errors (~32) are expected at check time - ignore those. Fix everything else.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.