Evaluate APIs, CLIs, and UIs for mismatches between perceived and actual actions.
npx skills add https://github.com/NlightNFotis/skills --skill affordance-review
Please help me install this Agent Skill. Skill: affordance-review Source: https://github.com/NlightNFotis/skills/tree/main/affordance-review Command: npx skills add https://github.com/NlightNFotis/skills --skill affordance-review
This Skill helps you find where an API, CLI, or UI makes the wrong action too easy, the right action too hard, or the outcome too unclear. It is built for situations where users keep making avoidable mistakes because the design relies on memory, documentation, or guesswork instead of clear affordances.
Use the affordance-review skill to evaluate a command, API, or interface and identify where its design makes unsafe or confusing actions too easy.
High-intent search queries and answers about installing and using this skill.
To audit API and CLI design for unsafe actions, evaluate mismatches between perceived affordances and actual behavior by inventorying available actions, classifying risk levels, and checking reversibility. This process identifies where designs rely on guesswork instead of clear signifiers.
An affordance inventory maps what actions a surface truly allows versus what its labels, flags, and controls suggest to users. It improves usability by exposing mismatches between perceived actions and actual behavior, reducing reliance on documentation for safe operation.
Diagnose repeated user errors in operational tools by applying Norman's interaction model to identify gulfs of execution and evaluation. This reveals whether users fail to initiate correct actions or fail to understand system feedback.
Review destructive CLI commands for safety by classifying actions as dangerous or irreversible, then verifying defaults, confirmations, and undo paths. This ensures destructive operations require explicit typed confirmations or offer dry-run modes.
Yes, you can audit SDK method names and default choices by analyzing whether entry point naming and default configurations encourage safe actions or inadvertently make dangerous outcomes too easy to trigger without explicit intent.
Redesign risky confirmation flows by proposing stronger constraints such as safer defaults, clearer naming, typed confirmations, split commands, and dry-run modes. These concrete recommendations ground interaction design in explicit, safe affordances.
HDeiblerAudits UI elements that visually misrepresent interactivity and rewrites disabled/read-only treatments with accessibility semantics.
intellectronicaManage Todoist tasks, projects, sections, labels, and comments via the td CLI.
mngarciaAnalyzes interfaces using affordances, signifiers, constraints, feedback and conceptual models to identify usability flaws.
yfyang86Generate decision analysis insights using Herbert Simon's bounded rationality framework.
