agentleFS
its-shitzuits-shitzu/AgentStack/.claude/skills/add-dashboard-page/SKILL.md

add-dashboard-page

Skill1 starsChanged 5 months agoMITView on GitHub

Generate a new page under the authenticated dashboard that matches the existing layout, sidebar, and design system. Use when the user asks to add a new dashboard screen/page (e.g. "add an Analytics page to the dashboard", "create a Team page under settings").

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. JetBrains/ij-perf-report-aggregator★ 24same 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 repository3 other files it gives its agents.

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
  1. Very specific:

    Create src/app/(dashboard)/<path>/page.tsx as an async server component.

    line 20
  2. Very specific:

    If the page needs interactivity (forms, buttons with client state), split it: keep page.tsx a server component for data fetching, and put …

    line 26
  3. Very specific:

    Do not duplicate the sidebar, topbar, or auth check — those are inherited from (dashboard)/layout.tsx.

    line 28
  4. Distinctive:

    Keep the page focused on what was requested — no placeholder analytics charts or fake data unless asked for.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

add-dashboard-page

Adds a new route inside the (dashboard) route group, reusing the existing layout/sidebar/topbar and Shadcn UI primitives so the result is visually indistinguishable from hand-written pages. Read AGENTS.md for project-wide conventions.

Reference files (read these before generating anything)

  • src/app/(dashboard)/layout.tsx — the shared layout (auth guard via getCurrentUser, Sidebar + Topbar). New pages do NOT need to repeat this — they automatically inherit it by living under (dashboard)/.
  • src/app/(dashboard)/dashboard/page.tsx — canonical example of a server component page: heading + description block, then a grid of Cards.
  • src/app/(dashboard)/dashboard/settings/organization/page.tsx — example of a page that fetches data server-side with Drizzle, scoped by requireOrganization().
  • src/components/dashboard/nav-items.ts — sidebar registry.

Steps

  1. Determine the route path from the request (e.g. "Analytics page" → /dashboard/analytics, "Team page under settings" → /dashboard/settings/team).
  2. Create src/app/(dashboard)/<path>/page.tsx as an async server component. Always start with:
    const user = await requireUser(); // or requireOrganization() if org-scoped data is needed
    from @/lib/session.
  3. Structure the page body using the established pattern: a heading block (<h1 className="text-2xl font-semibold"> + a text-sm text-neutral-500 description paragraph), followed by content in Card/CardHeader/CardContent from @/components/ui/card. Use a grid gap-4 sm:grid-cols-* wrapper for multi-card layouts, matching dashboard/page.tsx.
  4. If the page needs interactivity (forms, buttons with client state), split it: keep page.tsx a server component for data fetching, and put the interactive part in a colocated "use client" component (mirror settings/billing/billing-actions.tsx).
  5. Register the page in src/components/dashboard/nav-items.ts with a lucide-react icon, unless the user explicitly says it's a sub-page that shouldn't appear in the sidebar (e.g. a detail/edit view).
  6. Do not duplicate the sidebar, topbar, or auth check — those are inherited from (dashboard)/layout.tsx.

Conventions to enforce

  • Server Components by default; only mark a file "use client" when it needs state, effects, or event handlers.
  • Reuse existing src/components/ui/* primitives before creating new ones. If a needed primitive doesn't exist yet (e.g. Tabs, Tooltip), say so explicitly and ask whether to add it via shadcn rather than hand-rolling it.
  • Keep the page focused on what was requested — no placeholder analytics charts or fake data unless asked for.

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.