payoff-action-modeling
Design UI action models from user intent questions
Product teams struggle to decide what UI actions to show after a user completes a task. This skill provides a structured framework to model actions from user intent, placing them at the right scope and priority level.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "payoff-action-modeling". After a user imports customer data from a CSV file, what actions should the UI show?
Expected outcome:
- Outcome state type: handoff with review
- Primary CTA: Review import results
- Contextual actions: Map field (per column), Fix row (per error), Download error file
- Continuation branches: Import more, Start new import
- Recovery actions: Undo import, View import history
- Placement notes: Error rows show Fix inline, success summary at top with Review CTA
Using "payoff-action-modeling". Our file upload completion screen shows Download, Share, Delete, Rename, Move, Copy link, and Add description all at the same level. What is wrong with this?
Expected outcome:
- Issue 1: No primary CTA - 7 actions at equal visual weight creates decision fatigue
- Issue 2: Download should be primary CTA (highest-value next action)
- Issue 3: Delete is destructive and should be contextual with recovery path, not at top level
- Issue 4: Move and Copy link are deferred actions that can go in a secondary menu
- Issue 5: Add description is a refinement action, not an outcome action
- Proposed: Primary CTA: Download | Secondary: Share, Copy link | Menu: Rename, Move | Contextual with confirm: Delete
Security Audit
SafeAll 142 static analysis findings are false positives. The skill is a pure documentation guide for UX/UI product design. Backtick characters flagged as 'shell execution' are standard Markdown inline code formatting for UI action labels. Findings flagged as 'weak cryptographic algorithm' are markdown table content, YAML frontmatter, and UX guidance text with no cryptographic content. The single URL reference to casely.digital is a passive documentation mention, not executable network code. No executable code, data exfiltration, command injection, or environmental access was found.
Low Risk Issues (1)
Quality Score
What You Can Build
Design post-onboarding action screens
Use the framework to decide which actions to show after a user completes onboarding, setup, or first-time configuration. Avoid overwhelming new users while providing clear next steps.
Plan dashboard action hierarchies
Organize actions in a dashboard or workspace by classifying them into outcome, selection, item, navigation, and recovery scopes with appropriate urgency levels.
Review existing interfaces for action clarity
Audit an existing UI against outcome modeling principles to identify duplicated actions, vague labels, and competing primary CTAs. Produce a concrete improvement plan.
Try These Prompts
I just built a file upload feature for my app. After a user uploads a file, I need to model what actions to show on the completion screen. Use the outcome action modeling framework to produce a simple action model table with scope, pressure, and placement for at least 8 actions.
I am designing a project management dashboard that appears after a user creates a new project. The dashboard shows tasks, team members, and recent activity. Use the full outcome action modeling framework to classify the outcome state, generate at least 15 user intent questions, and produce an action table with all scopes, pressures, and placements.
I am designing a data import flow where users upload a CSV, map fields, review results, and handle errors. The post-import screen needs to support retry failed items, download error logs, approve mapped rows, and export results. Use the framework with special attention to recovery actions, ambiguous scope boundaries, and intent pressure conflicts. Add edge case handling for partial failures.
I have an existing action model for a content management system publish screen. The current model has 12 actions all shown at the same level. Use the framework to review this model for density issues, scope ambiguity, label clarity, and momentum problems. Identify at least 5 specific issues and propose a revised action table.
Best Practices
- Start by defining the outcome state type before placing any actions. This determines the entire action hierarchy.
- Keep one clear primary CTA per outcome screen. Multiple primary-level actions create decision fatigue.
- Use concrete action labels that describe user outcomes rather than implementation details.
Avoid
- Do not overload first-success screens with every possible action. Defer advanced features to secondary menus.
- Avoid treating all actions as equal in visual hierarchy. Use intent pressure to differentiate immediate, contextual, and deferred actions.
- Do not hide important recovery actions like undo or retry behind generic menus. Place them near the state they recover from.