Cognitive ux admin
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-adminAssembled 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 administration, back-office, moderation, and operations websites using evidence-informed UX. Use when authorized staff must manage users, content, configuration, permissions, queues, or bulk actions; return role/permission maps, safe action design, auditability, accessible dense controls, recovery flows, and operational-error validation.
SKILL.md
2.6 KB, as published. Nobody here has run it
Cognitive UX: Admin Operations
Scope
Use for privileged administration. Use cognitive-ux-workflow for ordinary knowledge-work flows and cognitive-ux-dashboard for monitoring/decision support.
Intake
- Identify roles, authority boundaries, objects, queues, and primary decisions.
- Identify bulk actions, irreversible outcomes, audit/log requirements, automation, and escalation.
- Identify density, keyboard use, assistive technology, support, and error consequences.
State assumptions that could change the design. Define the primary task, consequence of failure, and measurable user outcome before proposing a layout.
Design procedure
- Create a role/permission map before exposing actions; show who can do what and why an action is unavailable.
- Design bulk changes with scope preview, exclusions, confirmation, progress, result records, and undo/rollback where possible.
- Make destructive and privilege-changing actions explicit, reviewable, and auditable; preserve a safe recovery route.
- Use dense tables, filters, shortcuts, and status controls only with clear labels, keyboard support, focus management, and responsive alternatives.
- Treat queue exceptions, empty states, no-permission, partial failure, and stale data as first-class operational states.
Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.
Required outputs
- role/permission/action map
- bulk-action, audit-log, and rollback specification
- queue/exception/error recovery flow
- dense-control accessibility checklist
- critical-error and operator-efficiency study
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not use defaults that silently grant authority, conceal partial failure, allow unreviewed destructive bulk changes, or make audit history inaccessible.
Related skills
Use cognitive-ux-workflow, cognitive-ux-dashboard, and cognitive-ux-portal. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.