Design interface behaviour with AI
Decide what an action changes, who is affected and how someone recovers from a mistake. Record reachable states before turning a design into code.
Design interface behaviour with AI before deciding where to put a confirmation dialog. Removing a shared file from one person's recent list is quite different from deleting it for the entire team. A button labelled “Remove” could plausibly mean either.
The product-design skill brings the object, scope and consequence of an action into the same discussion. It can review an existing interface or specify a proposed one. When there is no evidence for a product decision, the resulting notes can mark it as unresolved instead of presenting a preference as a requirement.
What it does
- Choose a control that fits the intended action
- Specify whether a change affects one item or several people
- Compare confirmation with undo for a reversible operation
- Describe empty, partial, failed and completed states
- Name the product decisions a developer still needs answered
Install and use
- Install the skill in a compatible agent and share a brief, mock-up or description you have permission to use. No external account is needed to reason about the design.
- Ask, “Review removing a file from a team folder. Distinguish hiding it for myself from deleting it for everyone. Include a recovery path where one exists.”
- Walk through the result with each affected role. Check the proposed behaviour against what the product can actually restore.
FAQ
Source
Made by Matthew Blode. Original skill: product-design, published on GitHub under the MIT licence.
View on GitHub