Agent skill · design visual · aiskillstore
payoff-action-modeling
Model product UI actions from user intent questions after a meaningful outcome, completion, created resource, imported data, uploaded file, synced integration, report, deployment, automation, review state, handoff, or workflow milestone. Use when deciding which actions to show, hide, group, name, prioritize, defer, or place across outcome, item, selection, continuation, navigation, recovery, and assistance scopes.
Why this skill is useful
Provides a structured action model for UI design based on user intent and outcomes, which the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Outcome Action Modeling Use this skill before designing or polishing any UI state where the user has achieved a meaningful outcome and now needs to understand what happened, what exists, and what to do next. This applies to AI products, CRUD systems, dashboards, onboarding flows, imports, uploads, reporting tools, automation tools, admin panels, PM tools, CMS platforms, deployment or sync flows, collaborative review systems, and workflow products. The goal is to answer: "Now that the user has value or progress, what might they reasonably want to do next, and where should each action live?" Core Output Produce an action model with: Primary outcome: the result, resource, state, or completion the user should understand first. Outcome state type: completion, generation, workspace, review, handoff, recovery, or continuation. User questions: realistic "What if I want to..." questions from the user's point of view. Action scope: outcome, selection, item, continuation, navigation, recovery, or assistance. Intent pressure: immediate, contextual, or deferred. UI placement: primary CTA, secondary action, per-item action, row menu, accordion detail, bulk toolbar, empty/optional state, status area, shell navigation, or next screen. Required vs optional: whether the action must be visible now or can be deferred. Copy: short labels written as user-facing outcomes, not implementation details. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/payoff-action-modeling