Frontend

Admin Dashboard

Designs secure, usable admin dashboards and client content-management interfaces.

What it does

Designs secure, usable admin dashboards and client content-management interfaces.

When to use it

Use for internal management screens, CRUD workflows, roles and permissions, tables, filters and reporting views.

Problems it prevents

Stops handover-day dashboards that are powerful but unusable by the client who actually has to run them.

Typical workflow

  1. Map roles and permissions
  2. Design CRUD and filter flows
  3. Build reporting views
  4. Check handover readiness

Example output

A management screen a non-technical client can operate on day one, with permissions that actually match their role.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/admin-dashboard/ to use it on every project, or in .claude/skills/admin-dashboard/ to scope it to one repository. Then invoke it directly:

/admin-dashboard

Read the official Claude Code skills guide

Works well with