joao-aires/agent-skills-public/saas-dashboard-design

Claude Code and agent skill by joao-aires/agent-skills-public

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Design or improve SaaS customer and operator dashboards around decisions,

Install

npx vskill@latest install joao-aires/agent-skills-public/saas-dashboard-design

SKILL.md

The same SKILL.md was published earlier as joao-aires/agent-skills-public/saas-dashboard-design.

Design dashboards for decisions and work

Identify the audience, their recurring tasks, the decisions this surface should support and the cost of acting on the wrong context. Separate customer workspaces, customer administration and internal operator tools.

Reuse sufficient product evidence and accepted visual direction. A dashboard request does not automatically reopen branding or select a UI library. Read dashboard decisions for data/interaction tradeoffs and the source review for inspected open-source examples.

Establish context and hierarchy

Begin with the work this audience returns to do. Determine what needs attention, what information explains the situation, and which action follows. Use that relationship to choose the starting view and navigation. An overview is useful when it helps prioritize work; a task list or detailed workspace may be the better starting point when users already know what they need to do.

Make organization/workspace, time range, environment and relevant resource scope recognizable before consequential actions. Preserve that context through drill-downs and return navigation so a user can investigate a record without rebuilding their filters or losing their place.

Give each summary or metric a decision it supports. Establish what a change in the value would lead the user to do, then choose the surrounding explanation and route to detail. Compare layouts using realistic data distributions, including long names, large counts and uneven activity, rather than arranging identical cards around invented metrics.

Domain facts shape the interface before visual synthesis: define the objects, tenant/resource scope, evidence and consequential decisions that the experience must make legible. Contribute candidate task/overview/list/detail structures and data-interaction contracts to available general interface design reasoning. Let that method refine hierarchy, navigation and visual consistency without replacing these domain semantics. The selected technical platform also informs feasible layout and state behavior before decisions are finalized. When generic design expertise is unavailable, preserve a coherent task-oriented design using the accepted system, real data and these domain requirements. Use the accepted stack's components/tokens; the skill does not require a framework, design tool or chart library.

Make data and actions interpretable

Define units, denominators, aggregation, time zone, comparison period, freshness and missing-data meaning for consequential metrics.

  • Distinguish zero, unavailable, stale and incomplete results.
  • Choose a chart, table or direct value according to the question; permit accessible interpretation without relying only on color or hover.
  • Connect summaries to the records or task that explains them where useful.

For operational tables, define search/filter/sort/pagination behavior and scope.

  • Make selection across pages and bulk-action impact explicit.
  • Support detail/recovery without losing useful list state.
  • Availability and entitlements should produce understandable routes, while enforcement remains on the server.
  • Avoid exposing restricted records in aggregates, counts, exports or hidden UI payloads.

Cover the actual journey

Design first-use, loading, useful empty, filtered-empty, partial/stale, denied, failed, pending and completed states where the journey encounters them.

  • Provide appropriate recovery and distinguish accepted work from completed effects.
  • Destructive or privileged actions need understandable scope and consequences, not a confirmation dialog on every click.
  • Customer billing/identity/support actions should use clear domain language and preserve tenant context.

Verify the design at the requested boundary

Verify realistic content, keyboard/focus, accessible names, zoom, responsive layouts and the primary task under relevant success/failure states.

This domain method remains independently usable and can provide the design result directly; a separate generic interface skill is not an obligatory dependency or a competing design approval step. When implementing, inspect the rendered target; a component story or screenshot does not establish full functional behavior. Check server isolation and persisted outcomes separately.

Return the design rationale, affected states and actual evidence at the requested stopping point.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
2
Repository forks
1
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/joao-aires/agent-skills-public/saas-dashboard-design/badge)](https://verified-skill.com/skills/joao-aires/agent-skills-public/saas-dashboard-design)

Something wrong with this skill or its page? Tell us.