Use this skill when the design has interactive capability but users aren''t *seeing* it — when the affordance is technically present but the signifier (the visible cue that tells users "you can do this") is missing or weak. Trigger when reviewing flat-design UIs where everything looks the same, when designing custom controls, when stakeholders ask "should this be more obvious?", or when picking signifier strength for primary vs. secondary actions. Sub-aspect of affordance; read that first.
$npx -y skills add hdeibler/universal-design-principles --skill affordance-signifiersInstalls into the current project.
Run `npx skills use "https://github.com/hdeibler/universal-design-principles" --skill "hdeibler/universal-design-principles/affordance-signifiers"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/hdeibler/universal-design-principles" that are relevant to the current task. Run `npx skills add "https://github.com/hdeibler/universal-design-principles"` and select the relevant skills, then follow their instructions.