Individual skill
principle-experience-first
Use on tradeoffs in product, UX, API ergonomics, or feature scope. When the convenient build and the better result for users point different ways, choose the better result. Ship fewer capabilities that are complete rather than many that are partial.
plugins/requie/endostack/skills/principle-experience-first/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 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)
- 1,533
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
- design-interface 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 · 2,132 bytes
Read excerpt
# Experience first
If what is convenient to build differs from what serves the person using it, build for that person. A small number of finished capabilities beats a long list of half-done ones.
## When it applies
Product, UX, API-ergonomics, and feature-scope tradeoffs. This principle sets the target. The order in which you build toward it belongs to [principle-foundational-thinking](../principle-foundational-thinking/SKILL.md).
## What to do
1. Require a justification for every feature, control, and option. Cut the ones without one.
2. Ship fewer things at higher polish.
3. Prototype design decisions in throwaway form, such as plain HTML, before writing production code. Changes there cost minutes.
4. Attend to the details users hit: transitions, alignment, spacing, feedback, and error states.