Automated summary
Guides the design and implementation of analytics dashboards with KPI cards, responsive grids, charts, data tables, and admin navigation.
Strengths
- Provides concrete, reusable React and Tailwind examples
- Emphasizes visual hierarchy and quick scanning of key metrics
- Covers common admin layouts and responsive grid patterns
Limitations
- Strongly oriented toward React and Tailwind CSS
- Does not cover data integration, authentication, or server-side rendering
- Offers limited guidance on accessibility and chart library selection
Use it when designing or improving an analytics, admin, or monitoring dashboard interface.
Avoid it when the main need is data modeling, analytics pipelines, or a non-React/Tailwind interface.
Security analysis
SafeThe skill contains only design guidance and illustrative frontend code (React/JSX) with no executable commands, network access, or destructive operations. It does not declare or use any tools, and the content is purely instructional for building dashboard interfaces.
No concerns found
How this analysis is madeExamples
Design an admin analytics dashboard in React and Tailwind with four KPI cards at the top, a revenue line chart, and a recent orders table.Create a responsive monitoring dashboard layout with a sticky header, sidebar navigation, and KPI cards that show trend indicators.Improve this dashboard layout so users can scan key metrics quickly and compare current values to previous periods.name: dashboard-design description: Design effective dashboards with clear layouts, KPI displays, data grids, and real-time updates. Covers dashboard patterns, information hierarchy, responsive grids, widget design, and admin panel layouts. Use for building analytics dashboards, admin interfaces, and monitoring displays.
Dashboard Design
Create effective, information-rich dashboards that surface key data clearly.
Instructions
- Prioritize information - Most important metrics at top-left
- Use consistent card layouts - Same styling for similar data types
- Design for scanning - Users glance, not read; make data obvious
- Show context - Compare to previous periods, show trends
- Enable action - Dashboards should lead to decisions
Dashboard Layout Patterns
Standard Admin Dashboard
function AdminDashboard() {
return (
<div className="min-h-screen bg-gray-100 dark:bg-gray-900">
{/* Top Navigation */}
<header className="sticky top-0 z-50 bg-white dark:bg-gray-800 border-b shadow-sm">
<div className="flex items-center justify-between h-16 px-6">
<Logo />
<div className="flex items-center gap-4">
<SearchInput />
<NotificationBell />
<UserMenu />
</div>
</div>
</header>
<div className="flex">
{/* Sidebar Navigation */}
<aside className="hidden lg:block w-64 bg-white dark:bg-gray-800 border-r min-h-[calc(100vh-4rem)] sticky top-16">
<nav className="p-4 space-y-2">
<SidebarLink icon={HomeIcon} label="Overview" active />
<SidebarLink icon={ChartIcon} label="Analytics" />
<SidebarLink icon={UsersIcon} label="Customers" />
<SidebarLink icon={SettingsIcon} label="Settings" />
</nav>
</aside>
{/* Main Content */}
<main className="flex-1 p-6">
{/* Page Header */}
<div className="mb-6">
<h1 className="text-2xl font-bold text-gray-900 dark:text-white">
Dashboard Overview
</h1>
<p className="text-gray-500">Welcome back, here's what's happening</p>
</div>
{/* KPI Cards Row */}
<div className="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-4 gap-6 mb-6">
<KPICard
title="Total Revenue"
value="$45,231"
change="+12.5%"
trend="up"
/>
<KPICard
title="Active Users"
value="2,345"
change="+5.2%"
trend="up"
/>
<KPICard
title="Conversion Rate"
value="3.2%"
change="-0.4%"
trend="down"
/>
<KPICard
title="Avg. Order Value"
value="$127"
change="+8.1%"
trend="up"
/>
</div>
{/* Charts Row */}
<div className="grid grid-cols-1 lg:grid-cols-2 gap-6 mb-6">
<ChartCard title="Revenue Over Time">
<LineChart data={revenueData} />
</ChartCard>
<ChartCard title="Sales by Category">
<BarChart data={categoryData} />
</ChartCard>
</div>
{/* Data Table */}
<Card>
<CardHeader>
<CardTitle>Recent Orders</CardTitle>
<Button variant="outline" size="sm">View All</Button>
</CardHeader>
<DataTable
columns={orderColumns}
data={recentOrders}
pagination
/>
</Card>
</main>
</div>
</div>
);
}
KPI Card Component
interface KPICardProps {
title: string;
value: string | number;
change?: string;
trend?: 'up' | 'down' | 'neutral';
icon?: React.ComponentType;
subtitle?: string;
}
function KPICard({ title, value, change, trend, icon: Icon, subtitle }: KPICardProps) {
return (
<div className="bg-white dark:bg-gray-800 rounded-xl p-6 shadow-sm border border-gray-200 dark:border-gray-700">
<div className="flex items-start justify-between">
<div>
<p className="text-sm font-medium text-gray-500 dark:text-gray-400">
{title}
</p>
<p className="mt-2 text-3xl font-bold text-gray-900 dark:text-white">
{value}
</p>
{change && (
<div className="mt-2 flex items-center gap-1">
{trend === 'up' && (
<ArrowUpIcon className="w-4 h-4 text-green-500" />
)}
{trend === 'down' && (
<ArrowDownIcon className="w-4 h-4 text-red-500" />
)}
<span className={`text-sm font-medium ${
trend === 'up' ? 'text-green-600' :
trend === 'down' ? 'text-red-600' :
'text-gray-500'
}`}>
{change}
</span>
<span className="text-sm text-gray-400">vs last month</span>
</div>
)}
</div>
{Icon && (
<div className="p-3 bg-blue-50 dark:bg-blue-900/20 rounded-lg">
<Icon className="w-6 h-6 text-blue-600 dark:text-blue-400" />
</div>
)}
</div>
</div>
);
}
Chart Card Component
interface ChartCardProps {
title: string;
subtitle?: string;
action?: React.ReactNode;
children: React.ReactNode;
}
function ChartCard({ title, subtitle, action, children }: ChartCardProps) {
return (
<div className="bg-white dark:bg-gray-800 rounded-xl shadow-sm border border-gray-200 dark:border-gray-700 overflow-hidden">
<div className="flex items-center justify-between px-6 py-4 border-b border-gray-200 dark:border-gray-700">
<div>
<h3 className="font-semibold text-gray-900 dark:text-white">{title}</h3>
{subtitle && (
<p className="text-sm text-gray-500">{subtitle}</p>
)}
</div>
{action}
</div>
<div className="p-6">
{children}
</div>
</div>
);
}
Dashboard Grid Patterns
Responsive Dashboard Grid
// 12-column grid system
<div className="grid grid-cols-12 gap-6">
{/* Full width */}
<div className="col-span-12">
<PageHeader />
</div>
{/* 4 equal KPI cards */}
<div className="col-span-12 sm:col-span-6 lg:col-span-3">
<KPICard />
</div>
<div className="col-span-12 sm:col-span-6 lg:col-span-3">
<KPICard />
</div>
<div className="col-span-12 sm:col-span-6 lg:col-span-3">
<KPICard />
</div>
<div className="col-span-12 sm:col-span-6 lg:col-span-3">
<KPICard />
</div>
{/* 2/3 + 1/3 layout */}
<div className="col-span-12 lg:col-span-8">
<MainChart />
</div>
<div className="col-span-12 lg:col-span-4">
<SidePanel />
</div>
{/* 50/50 split */}
<div className="col-span-12 md:col-span-6">
<ChartA />
</div>
<div className="col-span-12 md:col-span-6">
<ChartB />
</div>
</div>
Real-Time Dashboard
function RealTimeDashboard() {
const [metrics, setMetrics] = useState<Metrics | null>(null);
useEffect(() => {
// WebSocket for real-time updates
const ws = new WebSocket('wss://api.example.com/metrics');
ws.onmessage = (event) => {
const data = JSON.parse(event.data);
setMetrics(data);
};
return () => ws.close();
}, []);
return (
<div className="space-y-6">
{/* Live indicator */}
<div className="flex items-center gap-2">
<span className="relative flex h-3 w-3">
<span className="animate-ping absolute inline-flex h-full w-full rounded-full bg-green-400 opacity-75" />
<span className="relative inline-flex rounded-full h-3 w-3 bg-green-500" />
</span>
<span className="text-sm text-gray-500">Live</span>
<span className="text-sm text-gray-400">
Updated {formatRelativeTime(metrics?.timestamp)}
</span>
</div>
{/* Real-time metrics */}
<div className="grid grid-cols-4 gap-4">
<LiveMetric
label="Active Users"
value={metrics?.activeUsers}
sparkline={metrics?.userHistory}
/>
<LiveMetric
label="Requests/sec"
value={metrics?.requestsPerSecond}
unit="req/s"
/>
<LiveMetric
label="Avg Response"
value={metrics?.avgResponseTime}
unit="ms"
/>
<LiveMetric
label="Error Rate"
value={metrics?.errorRate}
unit="%"
alert={metrics?.errorRate > 1}
/>
</div>
</div>
);
}
Data Table for Dashboards
interface DataTableProps<T> {
columns: ColumnDef<T>[];
data: T[];
pagination?: boolean;
searchable?: boolean;
actions?: (row: T) => React.ReactNode;
}
function DataTable<T>({ columns, data, pagination, searchable }: DataTableProps<T>) {
const [search, setSearch] = useState('');
const [page, setPage] = useState(1);
const pageSize = 10;
const filteredData = useMemo(() => {
if (!search) return data;
return data.filter(row =>
Object.values(row).some(val =>
String(val).toLowerCase().includes(search.toLowerCase())
)
);
}, [data, search]);
const paginatedData = useMemo(() => {
if (!pagination) return filteredData;
const start = (page - 1) * pageSize;
return filteredData.slice(start, start + pageSize);
}, [filteredData, page, pagination]);
return (
<div>
{searchable && (
<div className="mb-4">
<input
type="search"
placeholder="Search..."
value={search}
onChange={(e) => setSearch(e.target.value)}
className="px-4 py-2 border rounded-lg w-full max-w-sm"
/>
</div>
)}
<div className="overflow-x-auto">
<table className="w-full">
<thead className="bg-gray-50 dark:bg-gray-800">
<tr>
{columns.map(col => (
<th key={col.key} className="px-6 py-3 text-left text-xs font-medium text-gray-500 uppercase tracking-wider">
{col.header}
</th>
))}
</tr>
</thead>
<tbody className="divide-y divide-gray-200 dark:divide-gray-700">
{paginatedData.map((row, i) => (
<tr key={i} className="hover:bg-gray-50 dark:hover:bg-gray-800">
{columns.map(col => (
<td key={col.key} className="px-6 py-4 whitespace-nowrap text-sm">
{col.render ? col.render(row) : row[col.key]}
</td>
))}
</tr>
))}
</tbody>
</table>
</div>
{pagination && (
<Pagination
page={page}
totalPages={Math.ceil(filteredData.length / pageSize)}
onPageChange={setPage}
/>
)}
</div>
);
}
Best Practices
- 5-second rule - Key metrics should be understood in 5 seconds
- Above the fold - Critical data visible without scrolling
- Consistent time ranges - All charts use same time period
- Progressive disclosure - Summary → details on demand
- Empty states - Show meaningful content when no data
- Loading states - Skeleton screens while loading
When to Use
- Building admin panels and back-office tools
- Creating analytics dashboards
- Monitoring systems and real-time displays
- Data-heavy business applications
- Internal tools and management interfaces
Notes
- Consider user role - executives vs analysts have different needs
- Mobile dashboards need different layouts, not just responsive
- Performance matters - virtualize long lists, lazy load charts
- Allow customization - users can arrange their own dashboards
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/dashboard-design-ms47vpxx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/dashboard-design-ms47vpxx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dashboard-design-ms47vpxx/download' --output '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md.part' && mv '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md.part' '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && test -s '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dashboard-design' && cp -R '.skill-downloads/dashboard-design-ms47vpxx' '.claude/skills/dashboard-design'Cursor
test -f '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && test -s '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/dashboard-design' && cp -R '.skill-downloads/dashboard-design-ms47vpxx' '.cursor/skills/dashboard-design'Codex
test -f '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && test -s '.skill-downloads/dashboard-design-ms47vpxx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/dashboard-design' && cp -R '.skill-downloads/dashboard-design-ms47vpxx' '.agents/skills/dashboard-design'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/dashboard-design-ms47vpxx'openskills read 'dashboard-design-ms47vpxx'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/dashboard-design-ms47vpxx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.