Cognitive ux sales
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-salesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 25 days oldThe repository was created 25 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 focused sales, campaign, portfolio, launch, and lead-generation landing pages using evidence-informed UX. Use for a visitor who must understand one offer and take one clear next step; return message hierarchy, proof and objection map, honest CTA design, accessibility checks, and a comprehension test rather than generic visual polish.
SKILL.md
2.6 KB, 453 tokens by cl100k_base, as published. Nobody here has run it
Cognitive UX: Campaign & Sales Landing Pages
Scope
Use for a focused offer, lead-generation page, portfolio, launch, or campaign. Use cognitive-ux-product-marketing when the visitor must compare a complex product or plan.
Intake
- Identify audience, job, and context of first visit.
- Identify offer, proof available, price or commitment, and objections.
- Identify one primary next step and a qualified—not vanity—outcome.
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
- Write the value proposition as audience + problem/outcome + what happens next; test whether first-time visitors can restate it.
- Create one primary action and keep secondary actions present but quieter; do not conceal conditions or alternatives.
- Place credible proof close to the decision it supports; distinguish testimonial, claim, case study, and independently verifiable evidence.
- Make price, qualification, privacy, trial renewal, and cancellation terms clear before commitment.
- Use attention hierarchy to reduce visual-search cost, not to manufacture urgency or distraction.
Label each non-obvious recommendation as Standard / requirement, Evidence-informed default, or Hypothesis to test. Read archetype evidence before making research claims.
Required outputs
- message and evidence hierarchy by section
- CTA decision map with commitment disclosure
- objection/proof matrix
- accessible page and responsive interaction checklist
- comprehension task, success criterion, and follow-up metric
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not invent an attention-span statistic, promise conversion, use false scarcity, hide material terms, or use a preselected consent/recurring choice.
Related skills
Use cognitive-ux-product-marketing, cognitive-ux-commerce, and cognitive-ux-nonprofit. Do not combine multiple archetypes by default; select the primary user task and add another skill only when a secondary task is independently important.