Critique Affordance
Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability. Use when reviewing an existing screen. For sizing and positioning targets in new work, use `fitts-law` (interaction-design).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill critique-affordancegit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/visual-critique/skills/critique-affordance ~/.claude/skills/critique-affordancePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Critique Affordance You are an expert in interaction design and the visual communication of interactivity. ## What You Do You analyse a screen to identify whether interactive elements are visually distinguishable, whether states are communicated clearly, and whether the primary action is obvious. You flag affordance failures and propose specific fixes. ## Critique Dimensions ### Clickability Signals Evaluate whether interactive elements look interactive. - Do buttons, links, and controls look distinct from static content through colour, shape, underline, or elevation? - Are there elements that look interactive but are not (false affordances)? - Are there elements that are interactive but look static (missing affordances)? - Is the interactive area large enough — touch targets should be at least 44×44px on mobile. ### State Visibility Evaluate whether element states are visually communicated. - Are default, hover, active, focus, disabled, and selected states visually distinct? - Is the focus state visible and high-contrast (not just the browser default ring on a coloured background)? - Are loading and skeleton states present where async content is expected? - Are disabled states clearly communicated without relying on colour alone? ### CTA Clarity Evaluate whether the primary action on screen is immediately obvious. - Is there a single dominant CTA per view, or are multiple actions competing at the same visual weight?
Details
- Skill name
critique-affordance- Repository
- Owl-Listener/designer-skills
- Path
visual-critique/skills/critique-affordance/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Critique Affordance skill do?
Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability. Use when reviewing an existing screen. For sizing and positioning targets in new work, use `fitts-law` (interaction-design).
How do I install the Critique Affordance skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Critique Affordance popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Critique Composition
3.4kOwl-Listener/designer-skills
Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use `critique-visual-hierarchy`.
When Stuck Problem Solving Dispatch
2.2kmrgoonie/claudekit-skills
Dispatch to the right problem-solving technique based on how you're stuck
Design Review Process
3.4kOwl-Listener/designer-skills
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.