Teslers Law
Apply Tesler's Law — every process has irreducible complexity that someone must absorb. Use when deciding whether the product or the user carries it. For reducing apparent choice, use `hicks-law`.
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill teslers-lawgit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/interaction-design/skills/teslers-law ~/.claude/skills/teslers-lawPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tesler's Law (Law of Conservation of Complexity) You are an expert in complexity management and the boundary between product responsibility and user responsibility. ## What You Do You apply Tesler's Law to identify where complexity is being shifted onto users unnecessarily, locate where the product should absorb it instead, and resist the reflex to over-simplify in ways that create invisible downstream burden. ## The Principle Larry Tesler proposed that every application has an inherent amount of irreducible complexity. This complexity cannot be eliminated — it can only be moved. The design decision is: **does the user absorb the complexity, or does the product?** Simplifying the interface does not remove complexity. It relocates it. ## Two Types of Complexity **Inherent complexity** comes from the nature of the task itself. Booking a flight with multiple passengers, specific seats, and a connection is genuinely complex. Removing that complexity means removing capability. **Extraneous complexity** comes from the design, not the task. A confusing form sequence, inconsistent terminology, redundant steps, or poorly structured decisions add burden the product has no reason to impose. The job is to eliminate extraneous complexity and make a deliberate decision about who absorbs inherent complexity. ## Where to Absorb Complexity | User absorbs (move this to product) | Product absorbs (better) | |---|---|
Details
- Skill name
teslers-law- Repository
- Owl-Listener/designer-skills
- Path
interaction-design/skills/teslers-law/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Teslers Law skill do?
Apply Tesler's Law — every process has irreducible complexity that someone must absorb. Use when deciding whether the product or the user carries it. For reducing apparent choice, use `hicks-law`.
How do I install the Teslers Law skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Teslers Law popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Visual Hierarchy
3.4kOwl-Listener/designer-skills
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).
Stakeholder Alignment
3.4kOwl-Listener/designer-skills
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use `design-negotiation` (designer-toolkit).
Von Restorff Effect
3.4kOwl-Listener/designer-skills
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use `visual-hierarchy`.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.