agentsclimarketplace
Sign in

Cognitive ux travel

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

Design and audit travel search, comparison, booking, and itinerary-management websites using evidence-informed UX. Use when people must plan a trip, compare routes or stays, book, and manage changes; return constraint-first search, itinerary structure, full-price disclosure, recovery paths, and task validation.From its SKILL.md

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

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, 445 tokens by cl100k_base, as published. Nobody here has run it

Cognitive UX: Travel

Scope

Use for itinerary-oriented travel sites. Use cognitive-ux-booking for a generic appointment or reservable resource.

Intake

  • Identify trip purpose, travelers, origin/destination, dates, flexibility, accessibility, and budget.
  • Identify fare/rate components, baggage or inclusions, transfers, change/cancel rules, and jurisdiction.
  • Identify post-booking needs: itinerary, document, alert, support, or disruption handling.

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

  1. Start with trip constraints and show flexible alternatives without silently changing a critical constraint.
  2. Make comparison preserve route/time, transfers, inclusions, total price, refund/change conditions, and provider identity.
  3. Disclose full price and material conditions before commitment; distinguish optional extras from required charges.
  4. Maintain one clear itinerary with time zone, local date/time, confirmation, document, and support context.
  5. Design disruption, cancellation, rebooking, and refund paths as first-class flows, not support dead ends.

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

Required outputs

  • trip-search and comparison model
  • fare/rate and condition disclosure
  • booking and itinerary information architecture
  • disruption/rebooking support flow
  • find/compare/book/manage usability study
  • Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
  • Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not conceal fees or baggage/transfer constraints, change dates or airports without clear notice, or make the cheapest option appear comparable when conditions differ.

Related skills

Use cognitive-ux-booking, cognitive-ux-marketplace, and cognitive-ux-finance. Do not combine multiple archetypes by default; select the primary user task and add another skill only when a secondary task is independently important.

What ships with it: 2 files

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