Individual skill

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`.

interaction-design/skills/teslers-law/SKILL.md

Read pinned source

Source commit 9a6930cf84a822eb458624bd11c61aac5bbdf224

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 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): 3,320
Repository last updated: Sep 5, 2026
License: MIT

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

agentic Repository topic
agentic-ai Repository topic
ai Repository topic
ai-tools Repository topic
claude-code Repository topic
design-system Repository topic
design-systems Repository topic
prompt-engineering Repository topic
skills Repository topic
ux-design Repository topic
legal Derived category
operations Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 3,965 bytes

Read excerpt

# 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