Cognitive ux civic
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-civicAssembled 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 government and public-service websites using evidence-informed UX. Use when people must check eligibility, apply, renew, submit evidence, receive a decision, appeal, or get human help; return service-start guidance, conditional journey, save/resume/review, clear decision and appeal paths, accessibility checks, and equity-focused validation.
SKILL.md
2.7 KB, as published. Nobody here has run it
Cognitive UX: Civic & Public Service
Scope
Use for public-service and civic tasks. It does not determine legal eligibility or replace the responsible program’s policy and accessibility review.
Intake
- Identify service purpose, eligibility rules, documents, deadlines, privacy, jurisdiction, and consequence of exclusion.
- Identify user needs, language, access constraints, assisted-digital support, save/resume, and human escalation.
- Identify conditional steps, evidence verification, decision/appeal rules, and responsible policy owner.
State assumptions that could change the design. Define the primary task, consequence of failure, and measurable user outcome before proposing a layout.
Design procedure
- Start with plain-language service purpose, eligibility, required evidence, time/effort, privacy, deadlines, and a route to human help.
- Structure the journey around user decisions; ask only needed information and reveal conditional questions at the relevant point.
- Support save/resume, document handling, review/edit, confirmation, status, and clear next steps after every decision.
- Design ineligibility, partial completion, missing evidence, no-access, and appeal/reconsideration paths without dead ends.
- Test with people who face access, language, digital-literacy, disability, or time constraints—not only expert staff.
Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.
Required outputs
- service-start and eligibility information design
- conditional journey and evidence checklist
- save/resume/review/decision/appeal flow
- assisted-digital and accessibility support plan
- equity, completion, and comprehension study
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not infer eligibility, obscure a deadline or required document, use an inaccessible upload/control, create a no-help dead end, or present policy as UX advice.
Related skills
Use cognitive-ux-forms, cognitive-ux-portal, and cognitive-ux-jobs. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.