affordance-false-and-anti

What problem does it solve?

This Skill helps you fix UI problems where elements mislead users about whether they can interact, reducing “I tapped and nothing happened” confusion.

Core Features & Use Cases

• Identifies false affordance patterns such as button-like cards, inert hover states, hyperlink styling that isn’t actually a link, and decorative elements that users interpret as controls.
• Designs anti-affordance for unavailable actions using properly differentiated disabled and read-only treatments, with clear “you can’t” signaling (visual difference plus optional explanation).
• Applies practical audit heuristics including hover-style audits, disabled-with-context checks, and accessibility-oriented state requirements.

Quick Start

Use this skill to audit a screen for elements that look clickable but don’t respond, then rewrite the treatments for disabled, read-only, or inert components so users understand what is and isn’t interactive.