Agent skill

Doherty Threshold

by Owl-Listener in Owl-Listener/designer-skills

Apply the Doherty Threshold — keep system response under 400ms to preserve user flow.

MITAuto-check passedFrontend & Design

Install Doherty Threshold

skills CLI
$ npx skills add Owl-Listener/designer-skills --skill doherty-threshold -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/designer-skills doherty-threshold --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/interaction-design/skills/doherty-threshold .claude/skills/doherty-threshold && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
doherty-threshold
GitHub stars
2.9k
Used in
1 other repo
Token cost
~940 tokens
SKILL.md length
501 words
Files
1
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

Apply the Doherty Threshold — keep system response under 400ms to preserve user flow.

  • Works in 5 steps: Acknowledge immediately (within 100ms)… → Show a loading indicator if completion… → Show progress (not just a spinner) if… → …
  • Diagnosing perceived slowness
  • SKILL.md covers What You Do, The Principle, Design Applications and What the Doherty Threshold Is…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doherty Threshold is an agent skill from Owl-Listener/designer-skills. Apply the Doherty Threshold — keep system response under 400ms to preserve user flow. Use when diagnosing perceived slowness or setting a performance budget. For what to show during unavoidable waits, use loading-states.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UX design and Web performance. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.

When your agent uses it

  • Diagnosing perceived slowness
  • Setting a performance budget

Example prompts

  • “/doherty-threshold”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Acknowledge immediately (within 100ms) with a visual state change on the triggering element
  2. Show a loading indicator if completion will take 400ms–3s
  3. Show progress (not just a spinner) if completion will take more than 3s
  4. Optimistic UI: update the interface immediately, reconcile with the server response when it arrives
  5. Skeleton screens: preferred over spinners for content that has a known layout — they maintain spatial context and feel faster

What it can do on your machine

Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doherty Threshold loads about 940 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 501 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~940

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 501 words, ~940 tokens.

Download SKILL.mdSave it as .claude/skills/doherty-threshold/SKILL.md (or your agent's skills folder).
name
doherty-threshold
description
Apply the Doherty Threshold — keep system response under 400ms to preserve user flow. Use when diagnosing perceived slowness or setting a performance budget. For what to show during unavoidable waits, use `loading-states`.

Doherty Threshold

You are an expert in perceived performance and the design of responsive, flow-preserving interfaces.

What You Do

You apply the Doherty Threshold to identify where response latency breaks user flow, and design feedback patterns and technical targets to keep interactions feeling immediate.

The Principle

Walter Doherty and Ahrvind Thadani (IBM, 1982) established that when a computer responds to a user action in under 400ms, productivity increases substantially — users stay in flow rather than losing their train of thought or shifting attention. Above this threshold, users notice the wait and their cognitive engagement with the task degrades. The key thresholds:

Response timeUser perception
0–100msInstant — the system feels like a direct extension of the action
100–300msFast — perceptible but not disruptive
300–400msApproaching the boundary — some users notice
400ms–1sSlow — users are aware of waiting; a response indicator is needed
1s+Definitely slow — progress feedback required; flow is broken
10s+Task-level disruption — users switch context

Design Applications

Where Sub-400ms Matters Most
  • Slide and view transitions: switching between screens or slides should complete in under 400ms; beyond this, the transition itself becomes a wait
  • Inline interactions: toggles, checkboxes, dropdowns, tab switches — all should feel immediate
  • Search and filter: results should begin appearing before 400ms; if not, show a skeleton or spinner immediately
  • Autocomplete: first suggestions should appear within 300ms of typing
  • Button feedback: visual state change on press must happen within 100ms, regardless of whether the underlying action completes
When You Cannot Meet the Threshold

If the system genuinely cannot respond in under 400ms:

  1. Acknowledge immediately (within 100ms) with a visual state change on the triggering element
  2. Show a loading indicator if completion will take 400ms–3s
  3. Show progress (not just a spinner) if completion will take more than 3s
  4. Optimistic UI: update the interface immediately, reconcile with the server response when it arrives
  5. Skeleton screens: preferred over spinners for content that has a known layout — they maintain spatial context and feel faster
Show full SKILL.md (173 more words)Show less

What the Doherty Threshold Is Not

  • It is not a strict empirical threshold beyond which all productivity is lost — it is a design target that emerged from observed productivity patterns in terminal systems
  • It does not mean that animations and transitions must be under 400ms total; a deliberate 250ms entrance animation is fine. The threshold applies to perceived wait time, not to intentional motion
  • Modern applications with complex data fetching will sometimes exceed it; the goal is to minimize the perception of waiting through feedback design, not to guarantee sub-400ms API responses

Best Practices

  • Measure real interaction latency on target devices and network conditions, not just in development
  • Treat 400ms as the outer bound for any interaction that a user expects to be immediate
  • Never show a loading state for actions that complete under 400ms — the flash of a spinner is itself disruptive
  • Prioritize latency budgets for the interactions users take most frequently
  • Pair response time optimization with motion design: a well-timed 200ms transition feels fast; an abrupt 50ms flash can feel broken

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in interaction-design/skills/doherty-threshold of Owl-Listener/designer-skills.

Open the folder on GitHubat commit 9a6930c

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Doherty Threshold next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doherty Threshold compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doherty Threshold this skillOwl-Listener/designer-skills2.9k1 repos~940Automated safety check: PassMIT
Implementing Real User Monitoringjeremylongshore/tons-of-skills-marketplace2.8k—~977Automated safety check: PassMIT
UX Auditjezweb/claude-skills1.1k—~8.6kAutomated safety check: WarnMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Web Quality Auditaddyosmani/web-quality-skills2.9k—~2.6kAutomated safety check: PassMIT
Interface Design for Dashboards and Appsholaboss-ai/holaOS11k3 repos~6kAutomated safety check: PassMIT

Similar skills

  • Implementing Real User Monitoring

    jeremylongshore/tons-of-skills-marketplace

    Implement Real User Monitoring (RUM) to capture actual user performance data including Core Web Vitals and page load times.

    2.8k GitHub stars~977 tokensUpdated today
    Frontend & DesignAuto-check passed
  • UX Audit

    jezweb/claude-skills

    Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss.

    1.1k GitHub stars~8.6k tokensUpdated 2 days ago
    Frontend & DesignAuto-check: warnings
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Web Quality Audit

    addyosmani/web-quality-skills

    Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing.

    2.9k GitHub stars~2.6k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Frontend & DesignAuto-check passed
  • Web Quality Audit

    midudev/100cosas.dev

    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.

    114 GitHub starsUsed in 3 repos~1.7k tokens
    Frontend & DesignAuto-check passed

More from Owl-Listener/designer-skills

All 107 skills in this repo
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Auto-check passed
  • Accessibility Test Plan

    Owl-Listener/designer-skills

    Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

    2.9k GitHub starsUsed in 1 repo~478 tokens
    Auto-check passed
  • Aesthetic Usability

    Owl-Listener/designer-skills

    Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.

    2.9k GitHub starsUsed in 1 repo~678 tokens
    Auto-check passed
  • Affinity Diagram

    Owl-Listener/designer-skills

    Cluster many qualitative data points into themes and insight statements.

    2.9k GitHub starsUsed in 1 repo~520 tokens
    Auto-check passed
  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Auto-check passed
  • Business Design

    Owl-Listener/designer-skills

    Read financials, map competitive landscapes, and argue design decisions in the language of value.

    2.9k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Questions about Doherty Threshold

What does Doherty Threshold do?

Apply the Doherty Threshold — keep system response under 400ms to preserve user flow. Doherty Threshold is an agent skill from Owl-Listener/designer-skills. Apply the Doherty Threshold — keep system response under 400ms to preserve user flow.

When should I use Doherty Threshold?

Doherty Threshold fits situations like: diagnosing perceived slowness; setting a performance budget.

How do I install Doherty Threshold in Claude Code?

Run `npx skills add Owl-Listener/designer-skills --skill doherty-threshold -a claude-code`. Or copy the skill folder (interaction-design/skills/doherty-threshold in Owl-Listener/designer-skills) into .claude/skills/doherty-threshold in your project. Claude Code loads it when a task matches its description.

How do I install Doherty Threshold in Codex?

Run `npx skills add Owl-Listener/designer-skills --skill doherty-threshold -a codex`. Or copy the skill folder (interaction-design/skills/doherty-threshold in Owl-Listener/designer-skills) into .agents/skills/doherty-threshold in your project. Codex loads it when a task matches its description.

Can I use Doherty Threshold in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill doherty-threshold -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doherty-threshold, .gemini/skills/doherty-threshold, .github/skills/doherty-threshold and .opencode/skills/doherty-threshold in your project.

What does Doherty Threshold need to run?

SKILL.md names no scripts, command-line tools or credentials: Doherty Threshold is instructions for the agent only.

Does Doherty Threshold access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doherty Threshold safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doherty Threshold use?

Doherty Threshold is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doherty Threshold use?

About 940 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doherty Threshold?

Skills that share tags, products or a category with Doherty Threshold: Implementing Real User Monitoring (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), UX Audit (jezweb/claude-skills, 1.1k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Web Quality Audit (addyosmani/web-quality-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doherty Threshold?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,854 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.

Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.