Cognitive ux booking
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-bookingAssembled 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 appointment, event, accommodation, and resource booking flows using evidence-informed UX. Use when people must choose a service or time, reserve it, change it, or cancel it; return an availability model, constraints, price breakdown, calendar accessibility, recovery paths, and test plan.
SKILL.md
2.5 KB, as published. Nobody here has run it
Cognitive UX: Reservation & Booking
Scope
Use for appointments and reservable resources. Use cognitive-ux-travel for end-to-end itinerary search and travel-specific terms.
Intake
- Identify service/resource, duration, location/time-zone, capacity, and constraints.
- Identify price components, hold expiry, payment, cancellation, and amendment policy.
- Identify whether the user is booking for self, another person, or a group.
State assumptions that could change the design. Define the primary user task, its consequence of failure, and a measurable success outcome before proposing a layout.
Design procedure
- Let people state critical constraints—location, date, time zone, party, access needs, price—before presenting availability.
- Show duration, availability status, hold expiry, full price, and cancellation/change consequences before payment.
- Make date selection keyboard-operable and intelligible without color or hover; prevent ambiguous date/time-zone interpretation.
- Preserve selected context and entered information through unavailable slots, payment failures, and session interruption.
- Provide a confirmation with a durable record plus amend, cancel, support, and reminder paths.
Label each non-obvious recommendation as Standard / requirement, Evidence-informed default, or Hypothesis to test. Read archetype evidence before making research claims.
Required outputs
- availability and constraint model
- reservation state and expiry rules
- price/cancellation disclosure
- calendar and keyboard interaction spec
- book/change/cancel task test
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not imply availability that is not real, hide a hold timer, introduce fees late, or make cancellation harder than booking.
Related skills
Use cognitive-ux-travel, cognitive-ux-forms, and cognitive-ux-commerce. Do not combine multiple archetypes by default; select the primary user task and add another skill only when a secondary task is independently important.