ux-intent-mapping

Map panel and modal surfaces to user-intent Purpose statements and CTA inventories.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonaseck2/slaktforskning --skill ux-intent-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-intent-mapping
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/ux-intent-mapping
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill ux-intent-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents UX inconsistencies by ensuring every bounded panel or modal surface has a clear, user-intent-aligned Purpose statement and a CTA inventory that matches the actual verbs users experience.

Core Features & Use Cases

  • Purpose-by-user-language enforcement: Requires a one-sentence Purpose statement written in the user's words before any change to a panel section or modal.
  • CTA inventory with full verb coverage: Produces a per-surface inventory across View/Add/Edit/Delete/Open so actions are discoverable and semantically correct.
  • Consistency and anti-pattern detection: Flags known mismatches like label-hides-primitive, cross-surface unlink/delete ambiguities, and derived-view add flows that don’t map cleanly to primitives.
  • Project-specific UI contract checks: Guides auditing of host-entity flow, primitive delivery, section and host lifecycle (edit/remove), and state transitions to avoid silent degradation.

Quick Start

Use this skill when a developer or designer is about to change a specific Släktforskning panel section or modal and ask for a one-sentence Purpose in the user’s words before planning or implementing the UI changes.

Frequently Asked Questions about ux-intent-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a CTA inventory to audit UX consistency across panel and modal surfaces?

A CTA inventory audits UX consistency by mapping bounded panel and modal surfaces to user-intent Purpose statements, cataloging verbs across View, Add, Edit, Delete, and Open to ensure semantic correctness and discoverability.

What is intent mapping in product design and when do I need it for UI auditing?

Intent mapping in product design aligns UI actions with user goals by requiring a one-sentence Purpose statement in the user's words before changing any panel section or modal, preventing mismatches like label-hides-primitive ambiguities.

How do I detect UX anti-patterns like unlink and delete ambiguities across modal surfaces?

Detect UX anti-patterns by auditing cross-CTA inventories across View, Add, Edit, Delete, and Open, flagging known mismatches like cross-surface unlink/delete ambiguities and derived-view add flows that do not map cleanly to primitives.

Can I map user intent for one surface at a time when redesigning UI components?

Yes, intent mapping requires one-surface-at-a-time capture, ensuring each bounded panel or modal receives a dedicated Purpose statement and CTA inventory before any UI changes are planned or implemented.

What's the best way to maintain a UI contract check for host-entity flow and lifecycle symmetry?

Maintain UI contract checks by auditing host-entity flow, primitive delivery, section and host lifecycle for edit and remove, and state transitions, persisting the complete output inventory in a dedicated UX documentation file.