mcpbeat Sign in

Principle Experience First Skill for Claude

by michael-denyer

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

293 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
255
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/michael-denyer/pstack-claude --skill principle-experience-first

The instruction itself

1 sections, as written by the author

Experience First

When implementation convenience conflicts with user delight, choose delight.

  • Every feature, control, and option must be justified
  • Ship less, ship better (polished experience with three features beats rough one with ten)
  • Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
  • Get the details right (transitions, alignment, spacing, feedback, error states)
  • Tighten the core loop (every feature should serve the central workflow or get out of the way)

The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their perspective.

Foundations should serve the experience. Foundational thinking governs the *sequence* of work; this principle governs the *target*.

How to use it

Copy the folder

Take michael-denyer/principle-experience-first from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.