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".
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. ### Step 2: Build the Data Table The data table is the core of most dashboards: - **Columns:** define typed columns with appropriate formatters (dates, numbers, status badges, truncated text) - **Sorting:** server-side or client-side sorting on relevant columns - **Filtering:** practical filters — status dropdowns, date ranges, search text — not a filter for every column - **Pagination:** server-side pagination for large datasets — show total count, page size selector - **Row actions:** contextual actions per row (view, edit, delete) — use a dropdown menu for more than 2 actions - **Bulk actions:** select multiple rows for bulk operations if applicable (delete, export, status change) - **Loading state:** skeleton rows while data loads, not a spinner replacing the entire table - **Empty state:** helpful message when filters return no results vs. when there's genuinely no data ### Step 3: Build Detail Views For entities that need more than a table row: - **Detail page/modal:** show full entity data with clear layout — don't dump raw JSON - **Related data:** show associated entities (e.g., user's orders, project's members) - **Edit form:** inline editing or edit page with validation, loading states, and error handling - **Delete confirmation:** always confirm destructive actions — show what will be affected ### Step 4: Add Charts (if needed) Only add charts if they serve a purpose: - **KPI cards:** key numbers at the top — total users, revenue today, active incidents - **Time series:** trends that help with decisions — traffic over time, error rates, signups - **Distribution:** breakdowns that reveal patterns — status distribution, usage by plan Use the project's chart library or default to Recharts (React) / Chart.js (general). Don't add charts for the sake of having charts. ### Step 5: Wire Up Real Data Connect to real APIs, not mocks: - Use the project's data fetching pattern — server components, API routes, direct DB access - Implement optimistic updates for better UX on mutations - Handle concurrent editing if multiple admins use the dashboard - Add appropriate caching and revalidation - Ensure proper error handling for every API call — network errors, 401s, 403s, validation errors ### Step 6: Summarize ``` ## Dashboard Summary **Path:** [route/URL] **Stack:** [framework, component library, table/chart libraries] ### Pages - [page]: [purpose] — [key features] ### Data Tables - [entity]: [columns, sorting, filtering, pagination, row actions] ### CRUD Operations - Create: [form with validation] - Read: [list + detail views] - Update: [edit form/inline editing] - Delete: [with confirmation] ### Data Integration - [API endpoints/data sources used] - [caching/revalidation strategy] ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.