AGENT SKILL

principle-experience-first

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

License 许可
MIT
最近更新
2026-11-14
Stars
★ 109
Forks
19

01 前言 Front Matter

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

02 资源文件 1

03 SKILL.md 正文

Experience First

The product is the experience. Every technical decision either helps or hurts it. When implementation convenience conflicts with user delight, choose delight.

  • Say no to 1,000 things (every feature, control, and option must earn its place)
  • 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)
  • Sweat the details (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 seat.

Foundations should serve the experience, not the other way around. Foundational thinking governs the sequence of work; this principle governs the target.

04 同仓库更多 Skills

Aqua-123
Aqua-123/pstack-for-codex

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 109
Aqua-123
Aqua-123/pstack-for-codex

unslop

Cut AI tells from any writing. Must always apply.

★ 109
Aqua-123
Aqua-123/pstack-for-codex

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 109
Aqua-123
Aqua-123/pstack-for-codex

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 109
Aqua-123
Aqua-123/pstack-for-codex

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 109
Aqua-123
Aqua-123/pstack-for-codex

tdd

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

★ 109