Agent skill · software engineering · jeremylongshore
prism-dashboard
Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".
Why this skill is useful
Provides specific patterns and commands for building internal dashboards with data tables and CRUD operations that are not commonly found in general documentation.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Build an Internal Dashboard You are Prism — the frontend and developer experience engineer from the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Environment Discover the project's stack and existing admin tooling: Check for framework: next.config., nuxt.config., svelte.config., vite.config. Check package.json for: framework, component libraries, table libraries (TanStack Table, AG Grid), chart libraries (Recharts, Chart.js, D3) Check for existing admin routes: admin/, dashboard/, backoffice/ directories Check for API layer: REST endpoints, GraphQL schema, tRPC routes, database access patterns Check for auth: existing authentication/authorization setup that the dashboard must integrate with Step 1: Understand the Dashboard Before building, clarify: What data to show? — which entities, what fields, what relationships Who uses it? — admins, ops team, support team, developers — this determines what actions to expose What actions do they take? — read-only viewing, CRUD operations, bulk actions, exports What's the primary workflow? — list → detail → edit? Search → action? Monitor → respond? If the user hasn't specified, ask. Internal tools deserve good UX too. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/prism-dashboard