Menu

Individual skill

control-power-vs-simplicity

Apply layered control — designing interfaces that serve novice and expert users in the same product without forcing one audience into the other's interface. Use when building products that span experience levels (most consumer software, most professional tools used occasionally), choosing between "simple by default" and "powerful by default," or deciding what to expose vs. hide behind progressive disclosure. The skill is creating a default surface that suffices for novices and a depth surface that doesn't intimidate them but is fully present for experts.

plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/control-power-vs-simplicity/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,533
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

# Control — power vs. simplicity

The most-cited tension in control design: power users want depth, novices want simplicity, and most products have both kinds of users. The naive answers ("just make it simple," "just make it powerful") both fail. Simple products lose their experts to deeper alternatives; powerful products lose their novices before they ever discover the depth.

The successful pattern across decades of product design is *layering*: a simple default surface that handles the common cases, with depth available but not promoted. A novice can use the product productively without ever encountering the advanced controls. An expert can configure, customize, and extend without leaving the application.

## The core architecture

Layered control rests on a few moves applied consistently.

**Identify the 80/20.** What can a novice do that handles 80% of their use? That's the default surface. What does an expert need that handles the remaining 20% and the long-tail edge cases? That's the depth surface.

**Make the default surface complete for the novice case.** The novice should not feel that they're missing anything important. The default surface should be a complete tool for the use case it serves, not a stripped-down preview of the "real" tool.