User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last.
Install Peak End Rule
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills peak-end-rule --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/peak-end-rule .claude/skills/peak-end-rule && rm -rf skills-srcUse ~/.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/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .claude/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-ruleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills peak-end-rule --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/interaction-design/skills/peak-end-rule .agents/skills/peak-end-rule && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .agents/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills peak-end-rule --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/interaction-design/skills/peak-end-rule .cursor/skills/peak-end-rule && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .cursor/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path interaction-design/skills/peak-end-rule--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills peak-end-rule --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/interaction-design/skills/peak-end-rule .gemini/skills/peak-end-rule && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .gemini/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills peak-end-ruleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/interaction-design/skills/peak-end-rule .github/skills/peak-end-rule && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .github/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills peak-end-rule --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/interaction-design/skills/peak-end-rule .opencode/skills/peak-end-rule && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "peak-end-rule" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/peak-end-rule into .opencode/skills/peak-end-rule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peak-end-rule", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
peak-end-rule- GitHub stars
- 2.9k
- Token cost
- ~998 tokens
- SKILL.md length
- 562 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last.
- Works in 2 steps: The peak — the most emotionally intense… → The end — how the experience concluded
- Designing completion
- SKILL.md covers What You Do, The Principle, Design Implications and Practical Applications, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Peak End Rule is an agent skill from Owl-Listener/designer-skills. Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.
Its SKILL.md is about 1000 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 Product & Project Management. 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
- Designing completion
- Cancellation moments
Example prompts
- “/peak-end-rule”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- The peak — the most emotionally intense moment, positive or negative
- The end — how the experience concluded
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
Peak End Rule loads about 998 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 562 words of instructions outside code blocks.
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). 562 words, ~998 tokens.
Download SKILL.mdSave it as
.claude/skills/peak-end-rule/SKILL.md (or your agent's skills folder).- name
- peak-end-rule
- description
- Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use `zeigarnik-effect`.
Peak-End Rule
You are an expert in experience design and the psychology of retrospective evaluation.
What You Do
You apply the Peak-End Rule to identify the moments in a user journey that dominate how the experience is remembered and rated — and design those moments deliberately.
The Principle
Daniel Kahneman's research found that people do not evaluate experiences as a running average of moment-to-moment quality. Retrospective judgement is dominated by two moments:
- The peak — the most emotionally intense moment, positive or negative
- The end — how the experience concluded
The duration and average quality of everything in between contribute far less. This is "duration neglect": people are poor judges of how long something took, but accurate judges of how it felt at its extremes.
Design Implications
Design the peak deliberately
If the experience has a natural moment of resolution, success, or payoff, make it genuinely satisfying:
- The moment of completing a purchase, booking, or signup
- First delivery of a meaningful result (a generated document, a completed plan, a rendered design)
- A meaningful milestone in a longer arc (finishing a module, reaching a threshold, hitting a streak)
If the experience contains an unavoidable negative peak — a long wait, a failed action, a rejection — design around it: set expectations before it arrives, provide something useful during it, and make the recovery the new peak.
Design the end deliberately
The final moment of a session shapes overall impression more than most of what preceded it:
- End a checkout on a warm, clear confirmation — not a confusing order status page
- End an onboarding session at a moment of first visible value, not a setup screen
- End a data-entry session with unambiguous save confirmation
- Avoid ending on an error state; resolve or defer errors before session close wherever possible
Practical Applications
| Flow | Peak to design | End to design |
|---|---|---|
| Checkout | Order placed — confirmed, named, visualised | Warm confirmation with clear next steps |
| Onboarding | First output the user cares about | State showing their work is saved and accessible |
| Signup | "You're in" — the first landing inside the product | Dashboard or landing that demonstrates immediate value |
| Data-heavy tasks | Completing the most complex required step | Summary or confirmation of what was saved |
| Error recovery | The fix moment, not the error state | Clear signal that the issue is fully resolved |
Show full SKILL.md (184 more words)Show less
Duration Neglect in Practice
Users will rate a 10-minute experience that ended well above a 5-minute experience that ended poorly. Practical implications:
- Wait times: a long wait that ends in clear success is rated better than a short wait that ends in confusion
- Multi-session journeys: the final session before a user disengages drives retrospective rating more than aggregate usage quality
- Negative spikes: a single bad moment is over-weighted unless the recovery is excellent — design the recovery to become the new peak
Best Practices
- Map the emotional arc of every key flow; explicitly mark the highest-intensity moment and the final moment
- Invest disproportionately in the peak and the end — the return on design effort is higher there than in the middle
- Test recall: after a flow, ask users to describe the experience in their own words — what they describe is almost always the peak and the end
- Design recovery first: if the peak is necessarily negative, the recovery must be strong enough to become the remembered event
- Never end on an administrative or transitional screen — ending on accomplishment is always preferable to ending on process
© 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/peak-end-rule of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Compare with similar skills
Peak End Rule 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Peak End Rule this skillOwl-Listener/designer-skills | 2.9k | — | ~998 | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 115 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Peak End Rule
What does Peak End Rule do?
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Peak End Rule is an agent skill from Owl-Listener/designer-skills. Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last.
When should I use Peak End Rule?
Peak End Rule fits situations like: designing completion; cancellation moments.
How do I install Peak End Rule in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a claude-code`. Or copy the skill folder (interaction-design/skills/peak-end-rule in Owl-Listener/designer-skills) into .claude/skills/peak-end-rule in your project. Claude Code loads it when a task matches its description.
How do I install Peak End Rule in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill peak-end-rule -a codex`. Or copy the skill folder (interaction-design/skills/peak-end-rule in Owl-Listener/designer-skills) into .agents/skills/peak-end-rule in your project. Codex loads it when a task matches its description.
Can I use Peak End Rule 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 peak-end-rule -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/peak-end-rule, .gemini/skills/peak-end-rule, .github/skills/peak-end-rule and .opencode/skills/peak-end-rule in your project.
What does Peak End Rule need to run?
SKILL.md names no scripts, command-line tools or credentials: Peak End Rule is instructions for the agent only.
Does Peak End Rule 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 Peak End Rule 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 Peak End Rule use?
Peak End Rule 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 Peak End Rule use?
About 998 tokens (SKILL.md is roughly 4k 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 Peak End Rule?
Skills that share tags, products or a category with Peak End Rule: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Peak End Rule?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 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.