backnotprop/pstack

principle-experience-first

Apply when product, UX, or feature-scope tradeoffs come up.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/backnotprop/pstack --skill principle-experience-first

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

Related by task

from this repository

More skills

All skills