Skip to content
Skills Library
Design & UX · Building & coding

dashboard-layout

/dashboard-layout

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.

Repository
deskstudio ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content17 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Arguments

/dashboard-layout <what decisions it serves and what data exists> [--density monitoring|analysis] [--sizes ...]
Original author description

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.

How it works

SKILL.md has no level-two headings · 37 lines, 447 words

SKILL.md preview
---
name: dashboard-layout
description: 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.
argument-hint: "<what decisions it serves and what data exists> [--density monitoring|analysis] [--sizes ...]"
---

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.md` comes 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.
- `--density` defaults to analysis (light, airy) unless the ask says monitoring or live.

The ask: **$ARGUMENTS**

Versions

The database has no other skills named dashboard-layout.

Database snapshot: 13.11.2026 · package version 02d3f8e92f81 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90dashboard-design
    Clean, honest dashboard UI for web and SwiftUI — KPI tiles, charts, comparison periods, ranked breakdowns, date range pickers, filters, insights, empty and loading states, wide and phone layouts, plus a screenshot QA pass. Use when building, redesigning or critiquing an…
  • 100dashboard
    Admin / analytics dashboard in a single HTML file. Fixed left sidebar, top bar with user/search, main grid of KPI cards and one or two charts. Use when the brief asks for a "dashboard", "admin", "analytics", or "control panel" screen.
  • 100responsive-paradigms
    Mobile, tablet and desktop are different paradigms, not one layout scaled. Use when designing responsive layouts or deciding what each breakpoint shows.
  • 96admin-dashboard-widget
    Use when adding a card, KPI, chart or table to Beranda (the dashboard) for a module.
  • 90ux-tablet
    Apply medium-specific UX reasoning for TABLET applications: the hybrid medium that is touch-first but large-screen, often two-handed, sometimes with an attached keyboard/pointer, and capable of multi-pane and split-view multitasking. Use alongside ux-first-principles when the…
  • 98test-as-user
    Make this session's test account on the Neon dev branch, sign in, and click-test the app at desktop, tablet and phone widths. Use whenever a change needs checking in a real browser.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.