Cognitive Ux Product Marketing
Design and audit product-marketing websites for complex software, services, and subscriptions using evidence-informed UX. Use when a visitor must evaluate capabilities, fit, plans, proof, and a demo or trial; return audience paths, capability-to-outcome mapping, transparent comparison, accessibility requirements, and validation metrics.
Install
$ agentstack add skill-kfeng209-oss-cognitive-ux-cognitive-ux-product-marketing ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Cognitive UX: Product Marketing
Scope
Use for multi-page product marketing and plan evaluation. Use cognitive-ux-sales for one focused campaign; use cognitive-ux-commerce when the visitor purchases inventory.
Intake
- Identify distinct audiences and their decision criteria.
- Identify capabilities, differentiators, limits, pricing, and eligibility.
- Identify trial/demo path, commitment details, and existing proof.
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
- Define audience paths from their job-to-be-done rather than an internal feature taxonomy.
- Translate capabilities into observable outcomes, then link each claim to evidence or a clear limitation.
- Make plan comparison criteria, usage limits, price basis, renewal, and qualification discoverable before the CTA.
- Keep navigation predictable across features, use cases, pricing, security, and support; preserve orientation when visitors compare paths.
- Design the demo/trial handoff to explain what data is requested, what happens next, and how to exit.
Label each non-obvious recommendation as Standard / requirement, Evidence-informed default, or Hypothesis to test. Read [archetype evidence](references/archetype-evidence.md) before making research claims.
Required outputs
- audience-path map
- capability-to-outcome and proof ledger
- plan comparison model
- demo/trial handoff specification
- task-based evaluation plan
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not bury pricing or material limits, present marketing claims as research, or use pressure to substitute for decision support.
Related skills
Use cognitive-ux-sales, cognitive-ux-docs, and cognitive-ux-onboarding. Do not combine multiple archetypes by default; select the primary user task and add another skill only when a secondary task is independently important.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kfeng209-oss
- Source: kfeng209-oss/cognitive-ux
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.