ux-law-hicks-tesler-occam

Simplifies screens, menus, and forms using Hick's, Tesler's, and Occam's design laws.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill ux-law-hicks-tesler-occam-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-law-hicks-tesler-occam
Source: https://github.com/arayaroma/ether/tree/main/skills/ux-law-hicks-tesler-occam
Command: npx skills add https://github.com/arayaroma/ether --skill ux-law-hicks-tesler-occam-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces with too many visible choices slow users down and increase decision fatigue. This Skill provides a structured method for reducing visible options, deciding whether the user or the system should absorb complexity, and choosing the simplest viable design. ## Core Features & Use Cases - Hick's Law application: Cut visible options to what the current task needs, group related choices into categories, and progressively disclose advanced settings. - Tesler's Law reasoning: Decide who absorbs irreducible complexity, defaulting to smart defaults, auto-detection, and inferred values in code rather than pushing configuration onto users. - Occam's Razor tiebreaker: Between equally valid designs, pick the one with fewer screens, states, and moving parts without stripping controls users actually need. - Use Case: When redesigning an onboarding flow with eight upfront questions, apply the four-step checklist to auto-detect what the system already knows, group the rest, and ship the simplest remaining flow. ## Quick Start Ask the assistant to review this settings screen and simplify it using Hick's Law, Tesler's Law, and Occam's Razor.

Frequently Asked Questions about ux-law-hicks-tesler-occam

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce too many options in a UI menu?▼

Apply Hick's Law by cutting visible options to what the current task needs and grouping related choices into categories. Categorized choices are processed faster than an equal-size flat list, and remaining items can be progressively disclosed behind advanced settings or show-more controls.

What is Tesler's Law in UX design?▼

Tesler's Law states every system has irreducible complexity that someone must absorb. The practical guidance is to ask who absorbs it, the user or the system, and default to absorbing it in code through smart defaults, auto-detection, and inferred values.

How do Hick's Law and Occam's Razor work together?▼

First use Tesler's Law to remove choices the system can answer itself, then use Hick's Law to group and progressively disclose what remains. Finally apply Occam's Razor as a tiebreaker, picking the design with fewer screens, states, and moving parts.

When should simplicity not be the priority in design?▼

Occam's Razor is a tiebreaker between designs that solve the task equally well, not an excuse to under-solve it. Do not strip a control the user actually needs just to reduce the visible element count.

Can this approach simplify onboarding flows?▼

Yes, onboarding steps are an explicit trigger scenario. List every step shown to the user, auto-detect values the system already knows, group the remaining steps, and ship the simplest flow that still completes the task.