Cognitive ux onboarding
Skill kfeng209-oss/cognitive-ux/skills/cognitive-ux-onboarding
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-onboardingAssembled 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 first-run, activation, setup, and guided onboarding experiences using evidence-informed UX. Use when a new user must reach initial value in a product; return a time-to-value map, progressive setup, permission and data-request disclosure, empty-state design, recovery paths, accessibility checks, and activation-quality metrics.
SKILL.md
2.6 KB, as published. Nobody here has run it
Cognitive UX: Product Onboarding
Scope
Use for first-use product activation. Use cognitive-ux-forms for a complex application/form and cognitive-ux-learning when the purpose is long-term instruction and practice.
Intake
- Identify new user goal, prior knowledge, first valuable outcome, and context.
- Identify required versus optional setup, data/permission requests, imports, integrations, and time constraints.
- Identify empty states, support channels, success measure, and reasons a user may pause or return later.
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
- Define the smallest meaningful first outcome; sequence only setup required to reach it.
- Progressively disclose advanced configuration and explain why each data, permission, or integration request is needed at the moment of request.
- Use examples, starter data, and empty-state actions to support recognition without fabricating user content or outcomes.
- Let people skip, return, edit, and recover; never create a false sense that an optional step is mandatory.
- Measure the quality of activation through successful first outcomes and understanding, not a checklist completion rate alone.
Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.
Required outputs
- time-to-value and setup map
- permission/data-request disclosure plan
- empty-state and first-success specification
- skip/return/error recovery flow
- activation comprehension and follow-up study
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not gate core value behind unnecessary profiling, hide optionality, force imports, or define activation only as completion of onboarding screens.
Related skills
Use cognitive-ux-workflow, cognitive-ux-learning, and cognitive-ux-forms. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.