Menu

Individual skill

closure-completion-cost

Recognize when closure is the wrong choice — when the perceptual completion work it asks of the user is too costly, ambiguous, or risky. Use when designing for accessibility audiences, novice users, high-stakes interfaces (medical, financial, safety), small rendering sizes that strain perception, or any context where the user shouldn't have to do completion work to understand the form. The skill is judging when explicit forms serve the user better than suggested ones, even at the cost of visual elegance.

plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/closure-completion-cost/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Closure — completion cost

Closure is a powerful tool for visual economy and elegance, but it asks the user to do perceptual work — to complete the form. In some contexts, that work is too costly, too risky, or simply not available to the user. The skill is recognizing those contexts and committing to explicit forms instead.

The decision is rarely "closure or not"; it's "how much closure is appropriate for this audience and this stakes." The same designer who reduces a logo to elegant minimalism may reasonably choose explicit, fully-drawn shapes for a critical-action button.

## When closure costs too much

**Accessibility audiences.** Users with vision differences may have less ability to perceive subtle visual cues. A form suggested through partial outlines or negative space may not be perceivable at all. Provide explicit forms or text alternatives.

**Novice users.** First-time users haven't built up the visual vocabulary that closure depends on. A minimal icon that an expert recognizes instantly may be opaque to a novice. Pair minimal icons with labels until familiarity builds.

**Small rendering sizes.** Below ~24px, many forms lose enough visual information that closure stops working. The brain can't recover what isn't there. Either make the form larger or commit to explicit visual structure.