Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
Dashboard Design gives a coding agent a structured way to build or critique a data-heavy screen. It starts with the decision the screen should support, then works through metric definitions, chart choices, visual hierarchy and interaction states. The supplied references cover browser interfaces and SwiftUI dashboards.
The useful distinction is between a monitoring screen, where a reader needs to spot a problem quickly, and a view for exploring data in more detail. The skill asks the agent to choose the layout around that purpose rather than filling a page with interchangeable cards.
Use this skill when
- You are building a revenue, analytics or operational dashboard and need to decide which metrics should lead.
- A dashboard looks polished but uses inconsistent totals, misleading comparisons or colours that hide the important values.
- You need charts, date controls and ranked lists that remain usable on a phone or a wide desktop screen.
- You want a specific critique of an existing implementation, using screenshots or the running interface as evidence.
What it can do
- Define a screen question, a small set of headline metrics and explicit conditions that need attention.
- Choose suitable forms for the data, including lines, ranked bars, target comparisons and threshold-based heatmaps.
- Specify shared tokens, comparable time windows and number formatting so repeated metrics agree.
- Plan loading, stale-data, error, empty and small-sample states instead of treating every missing value as zero.
- Guide screenshot checks at wide, laptop and phone widths, with keyboard, contrast and colour-independent cues.
The package includes Markdown design references and illustrative React/Tailwind and SwiftUI snippets. It does not supply a working dashboard, a data connector or a charting runtime. You still need an implementation environment, trustworthy data and a way to render or inspect the result. Its compact, low-text style is a default to adapt to your audience; it is not a substitute for required explanations or accessibility support.
Typical workflows
- Build from a brief. Supply the users, the decision they need to make, metric definitions and a small fixed dataset with expected totals. Ask the agent to propose a hierarchy, build the components and compare the displayed figures with those expected answers.
- Review an existing dashboard. Provide screenshots or an authorised local preview. Request issues ranked by data accuracy, visibility of problems, hierarchy and interaction, then review the resulting changes on new screenshots.
- Adapt a screen across devices. Supply the current layout and target widths or Apple device sizes. Check how controls, charts and long labels behave in each state, including dark mode and larger text.
Examples describe intended workflows, not tests performed by this catalogue. Use an authorised test environment for account creation and seeded data; do not apply development-only testing shortcuts to a public service.
What is inside the skill
Section headings from the original SKILL.md (about 1,298 words of instructions). Read the full text in the source repository before installing.
- Leading words
- Build or redesign
- Critique ("is this a good design?")
- Rules that apply everywhere
- Sign-off
- House style (default taste)
Bundled files
references/case-study-datafast.mdreferences/case-study-school-dashboard.mdreferences/components.mdreferences/layout.mdreferences/perception.mdreferences/qa.mdreferences/snippets.mdreferences/sources.mdreferences/swiftui.mdreferences/tokens.mdLICENSE
Example prompts
- Build a revenue dashboard for our support manager using the supplied metric definitions and 14-day fixture. Start with the decision the screen should support, compare equal-length periods, and verify that each KPI, chart and ranked list agrees with the fixture totals.
- Review these desktop and phone screenshots of our analytics dashboard. Rank problems by data accuracy, visibility of warning conditions and hierarchy. Explain which chart or component should change and provide a concrete acceptance check for each recommendation.
- Adapt this SwiftUI attendance dashboard for a small iPhone, iPad and resizable Mac window. Keep missing attendance distinct from zero, add non-colour warning cues, and check dark mode, large Dynamic Type and VoiceOver descriptions against the supplied sample data.
How to install Dashboard Design
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Dashboard Design FAQ
What does the Dashboard Design skill do?
Design and critique data-heavy dashboards around clear decisions, consistent metrics and usable charts. Includes web and SwiftUI patterns plus a screenshot-based review workflow.
Which AI agents can use Dashboard Design?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Dashboard Design in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Dashboard Design and what is the license?
Dashboard Design is published by Otabek Abdiraimov under the MIT license. The source is https://github.com/abdiraimov-otabek/dashboard-design-skill/tree/main/skills/dashboard-design. The catalog keeps the original attribution.
What permissions does Dashboard Design need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.