AGENT SKILL

principle-experience-first

Experience first. Apply when a product, UX or scope trade-off comes up.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 2
Forks
0

01 前言 Front Matter

name
principle-experience-first
license
MIT
metadata
{ "source": "pstack principle-experience-first, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37" }
description
Experience first. Apply when a product, UX or scope trade-off comes up.

03 SKILL.md 正文

<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->

Experience first

When implementation convenience conflicts with the user's delight, choose delight.

  • Every feature, control and option has to justify itself.
  • Ship less, ship better: a polished experience with three features beats a rough one with ten.
  • Prototype before committing; a design decision is cheaper in a throwaway sketch than in production code.
  • Get the details right: transitions, alignment, spacing, feedback, error states.
  • Tighten the core loop: every feature serves the central workflow or gets 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 order of the work, this principle governs the target.

Stop when a feature cannot be justified from the user's side. Cut it rather than polish it.

04 同仓库更多 Skills

erickb336
erickb336/sage-stack

writing-standard

Write at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.

★ 2
erickb336
erickb336/sage-stack

sage

The state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~/.claude/sage/<project>/. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

sage-help

Help with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types /sage:sage-help (or /sage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

report

The report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

remote-control

Set up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~/workspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

readme-guide

Write a project README. Apply when you write, change or review a README of any project, in any language.

★ 2