dashboard-layout-patterns
Skill4 starsChanged 2 months agoMITView on GitHub
Choose and configure the application shell, grid, and responsive behavior for data-dense layouts. Use when dashboard layout, admin panel, management interface, data grid layout, sidebar layout, or topbar vs sidebar.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
(c) Full-bleed content: no persistent nav, used for single-purpose tools (analytics viewer, editor, report viewer).
≈ “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.
Files
A management-type layout — dashboard, admin panel, back-office tool — is not a website. It is a workspace. Users spend hours inside it, not minutes. Layout must optimize for efficiency, scan-ability, and navigation density — not for storytelling or first impressions.
1. Select the shell pattern
Four patterns — choose based on nav complexity from information-architecture:
(a) Sidebar + topbar (default for 5+ nav sections): collapsible sidebar for primary nav, topbar for user/search/notifications. The standard for complex management tools.
(b) Topbar only: horizontal nav for simple tools with ≤5 primary sections. Maximizes vertical content space.
(c) Full-bleed content: no persistent nav, used for single-purpose tools (analytics viewer, editor, report viewer). Navigation is contextual or back-button only.
(d) Bottom-nav shell (mobile-first or mobile-primary products): primary navigation lives in a 4–5 item bottom navigation bar. Used when the product is primarily used on touch devices. Pairs with a slide-over or modal for secondary navigation. Coordinate with adaptive-component-behavior when the same product needs a sidebar on desktop and a bottom-nav on mobile.
2. Define the grid system
Dashboard content area uses a grid: 12-column for wide layouts, 6-column for medium, stack for mobile. Widget sizes: 1/4, 1/3, 1/2, 2/3, full-width. Grid gaps use spacing tokens.
3. Define widget/card placement
Priority placement: most-used widgets top-left (F-pattern reading). Summary/KPI cards at the top, detail tables below, charts in the middle band. Action buttons in the topbar or card headers, never floating.
4. Responsive behavior
Sidebar: collapses to icons at breakpoint-md, becomes a drawer at breakpoint-sm. Grid: reflows from 3-column → 2-column → 1-column. Tables: horizontal scroll or card view on mobile. Define each behavior explicitly.
5. Fixed vs scrollable regions
Sidebar and topbar are fixed. Content area scrolls. Sticky table headers for long data tables. Sticky action bars at the bottom of form pages.
6. Density controls
Dashboards benefit from density options: compact (small padding, smaller text) vs comfortable (default). Reference spacing tokens for each density level.
Output
Layout spec: shell pattern + grid system + widget placement + responsive breakpoint behavior + density settings.
Anti-patterns
- Landing-page layouts on dashboard pages (hero images, excessive whitespace).
- Hiding primary actions in hamburger menus on desktop.
- Sidebars that can't collapse.
- Data tables without sticky headers.
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
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.