dashboard-layout
Skill43 starsChanged 23 days agoMITView on GitHub
A dashboard screen laid out from the decisions it serves: KPI row, charts, filter bar, table, sidebar, every state, at phone, tablet and desktop. Use when a product or a team needs a screen of numbers that reads.
In this repository25 other files it gives its agents.
- adapters/agents.mdAGENTS.md
- accessibility-auditSkill
- brand-kitSkill
- chart-designSkill
- dashboardSkill
- design-critiqueSkill
- design-handoffSkill
- design-qaSkill
- design-reviewSkill
- designSkill
- design-systemSkill
- design-templateSkill
- studioSkill
- email-campaignSkill
- email-templateSkill
- helpSkill
- initSkill
- motion-designSkill
- presentation-designSkill
- social-campaignSkill
- social-contentSkill
- statusSkill
- tasteSkill
- variantsSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.
≈ “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
Make a dashboard as the Design Manager.
Deliverable and standard. A dashboard to ${CLAUDE_PLUGIN_ROOT}/skills/desk/standards/dashboard.md: decisions first, KPI row, charts to standards/chart.md, filter bar, table, sidebar, four states, three breakpoints. Labels and empty states to standards/copy.md.
Desks.
| Desk | Agent | Tier | Does |
| Dashboard Architect | desk:dashboard-architect | senior | the decisions, questions and metrics, then three layout roughs, then the layout through polish |
| Data Viz Designer | desk:data-viz-designer | builder | every chart tile as inline SVG, sample data marked |
| Interaction Designer | desk:interaction-designer | senior | the filter bar, table sorting, the four states, what happens on a phone |
| Content Designer | desk:content-designer | builder | tile labels, empty and error state copy, timestamps |
| UI Designer | desk:ui-designer | builder | polish rounds on the file |
| Art Director | desk:art-director | director | the pick and the notes |
| Creative Director | desk:creative-director | director | sign-off |
Inputs. Text (the decisions, the audience, the data that exists), a file (a schema, a CSV, a metrics list), a URL or screenshot of the current dashboard to replace.
Proof sizes. phone,tablet,desktop for the ready state, desktop for loading, empty, error and stale. desktop-wide when asked.
Output under .desk/out/<id>/:
final.html: the dashboard per the file contract, states as[data-state]variants.decisions.md: decision, question, metric, where it sits on the screen, three to eight lines.renders/per size and state.
Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: dashboard-layout. Changes to the loop for this command:
decisions.mdcomes first from the Dashboard Architect and sets the KPI count and the chart list before any layout. The Content Designer writes every label and state line into the brief's copy block.- Roughs are three layouts by the Dashboard Architect at the senior model in patterns from the standard, with grey chart placeholders of the right shape. The pick is of the layout. The Data Viz Designer then fills the tiles in the picked layout, and polish moves to the UI Designer.
- Proof renders every state. A state that is missing or identical to ready is a proof failure.
- The Creative Director gets the ready renders at every size each round, and the four state renders only in the round they changed. A sign-off that rereads seven unchanged screens is director money spent on nothing.
--densitydefaults to analysis (light, airy) unless the ask says monitoring or live.
The ask: $ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.