closure-completion-cost
CommunityUse explicit forms when closure is costly
Design & Creative#accessibility#usability testing#error prevention#ux#visual hierarchy#icon design#form clarity
AuthorHDeibler
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Closure-based designs can force users to visually complete ambiguous shapes, which breaks down for people with limited perceptual access, unfamiliar symbols, or high-stakes contexts.
Core Features & Use Cases
- Calibrate implicit form vs explicit form based on audience familiarity, risk, and visual conditions.
- Identify failure symptoms like misclicks, “what does this do?” confusion, and missing visual structure during audits.
- Choose safer alternatives such as explicit outlines, added labels, stronger containment cues, or small-size variants for critical UI elements.
Quick Start
Use the skill to evaluate whether a particular icon, control, or layout should switch from closure-based minimalism to explicit form for your target audience and rendering conditions.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: closure-completion-cost Download link: https://github.com/HDeibler/universal-design-principles/archive/main.zip#closure-completion-cost Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.