agentsclimarketplace
Sign in

Cognitive ux portal

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

Design and audit member, customer, student, and account portals using evidence-informed UX. Use when authenticated people must access personal information and repeat tasks; return a task-oriented account architecture, secure yet accessible authentication/recovery, record/receipt patterns, help paths, privacy safeguards, and task-success validation.From its SKILL.md

Install
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-portal

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

One thing to look at

  • 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.

SKILL.md

2.6 KB, 444 tokens by cl100k_base, as published. Nobody here has run it

Cognitive UX: Member & Account Portal

Scope

Use for end-user authenticated self-service. Use cognitive-ux-admin for privileged staff operations and cognitive-ux-health or cognitive-ux-finance for high-stakes domain overlays.

Intake

  • Identify account holder goals, repeated tasks, data sensitivity, and identity risk.
  • Identify authentication, recovery, device/session, delegated access, notices, and audit needs.
  • Identify personal data types, current status, documents/receipts, support, and accessibility constraints.

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

  1. Organize navigation around account-holder tasks and current state rather than internal departments.
  2. Make authentication and recovery accessible, understandable, and appropriately risk-based; preserve a path when credentials fail.
  3. Show status, completed actions, documents, receipts, notices, and next steps in a stable, findable record.
  4. Explain why data is shown or requested, distinguish secure messaging from emergencies, and preserve privacy across shared devices.
  5. Give contextual help and support without forcing people to re-explain their account context.

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

Required outputs

  • account task and navigation model
  • authentication/recovery and session-state flow
  • status/document/receipt information design
  • privacy and delegated-access checklist
  • repeat-task and recovery usability study
  • Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
  • Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not simplify away required verification, expose sensitive data by default, make recovery inaccessible, or confuse a notice with a completed action.

Related skills

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

What ships with it: 2 files

1.5 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,569. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.