jakobs-law

Evaluates interface design decisions against established user conventions using Jakob's Law.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill jakobs-law
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jakobs-law
Source: https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/jakobs-law
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill jakobs-law

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers often depart from familiar interface conventions without weighing the learning cost imposed on users, leading to confusing products. This Skill helps you identify which conventions carry strong user expectations and decide deliberately when to follow or break them.

Core Features & Use Cases

  • Convention Auditing: Catalog dominant patterns across 3-5 comparable products before starting new design work.
  • Deviation Cost Analysis: Assess the discovery, learning, and memory costs users pay when a familiar pattern is replaced.
  • Justified Innovation Framework: Distinguish legitimate departures (domain-specific conventions, tested improvements) from unjustified ones (aesthetic preference, differentiation for its own sake).
  • Use Case: When redesigning a checkout flow, use this Skill to verify that cart icon placement, navigation patterns, and close-button behavior match user expectations before proposing novel interactions.

Quick Start

Ask the AI to review your proposed navigation pattern against Jakob's Law and flag any departures from established conventions.

Frequently Asked Questions about jakobs-law

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

FAQPage Schema
What is Jakob's Law in UX design?

Jakob's Law, articulated by Jakob Nielsen, states that users prefer your site to work the same way as other sites they already know. Users arrive with pre-built expectations about navigation placement, icon meanings, and interaction behaviors formed by time spent on other products.

When is it acceptable to break design conventions?

Departure is justified when the conventional approach fails your use case, your users hold a stronger domain-specific convention, testing shows measurably better performance, or no strong convention exists yet. It is not justified by aesthetic preference or wanting to feel differentiated.

Which UI conventions have the strongest user expectations?

The strongest conventions include logo top-left linking home, shopping cart icons for checkout, hamburger menus for hidden navigation, magnifying glass for search, X to close modals, and blue underlined text for links. Violating these forces users to relearn basic interactions.

How do I audit competitor conventions before designing?

Review how 3-5 comparable products handle the interaction you are designing, then catalog the dominant patterns. Weight your decisions by task frequency: high-frequency interactions should follow conventions, while low-frequency ones allow more latitude.

Can onboarding replace following established conventions?

No. Teaching users a custom pattern through onboarding is expensive and fragile compared to leveraging existing expectations. The learning cost of a novel pattern is paid on every visit until mastered, so convention should be the default and innovation the reasoned exception.