Cognitive ux dashboard

Skill kfeng209-oss/cognitive-ux/skills/cognitive-ux-dashboard

Research-traceable UI/UX skills for AI coding agents.

Install

npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and audit analytics dashboards, monitoring surfaces, and decision-support websites using evidence-informed UX. Use when people must monitor a situation, interpret data, investigate exceptions, and act; return a decision inventory, KPI/provenance model, progressive drill-down, accessible data alternatives, alert rules, and accuracy-based validation.

SKILL.md

2.5 KB, as published. Nobody here has run it

Cognitive UX: Analytics & Dashboard

Scope

Use for analytical decision support. Use cognitive-ux-workflow when the main job is completing a multi-step task rather than interpreting data.

Intake

Identify the decisions users must make, their frequency, urgency, and consequence.
Identify metrics, units, timeframes, freshness, uncertainty, thresholds, and data permissions.
Identify role-specific actions, operational context, empty/error/stale states, and accessible alternatives.

State assumptions that could change the design. Define the primary task, its consequence of failure, and a measurable user outcome before proposing a layout.

Design procedure

Begin with the decision, change, exception, and next action—not an inventory of charts.
Show definition, timeframe, unit, freshness, uncertainty, and source/provenance for every decision-relevant metric.
Use summary → comparison → detail drill-down while preserving filters, focus, and the question being investigated.
Design alerts with a clear condition, severity, owner, action, acknowledgment, and recovery; avoid continuous alarm styling.
Provide a usable data-table or text alternative for charts, and do not encode meaning with color alone.

Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.

Required outputs

decision and KPI inventory
dashboard hierarchy and drill-down map
alert/action and data-state specification
visualization plus accessible data-alternative checklist
decision accuracy/time test plan
Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not use decorative charts, false precision, unlabeled timeframes, color-only severity, or a metric that lacks a defined decision purpose.

Related skills

Use cognitive-ux-workflow, cognitive-ux-admin, and cognitive-ux-finance. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.