mirror of https://github.com/cursor/plugins.git synced 2026-09-14 20:00:00 +08:00

Files

T

lauren d7cde2b84e pstack: replace semicolons, em dashes, and connector colons in skill prose with periods or commas (#331 )

Punctuation and single-word swaps only. No sentence added or deleted, no
restructuring, no new text.

- 65 markdown files under pstack/skills. 220 changed lines, every changed
  line pairs with one base line.
- 272 rewrites. 239 semicolons (224 became a period plus a capital, 15 became
  a comma). 29 connector colons (28 became a period, 1 became a comma).
  1 em dash before a list became a colon. 3 word swaps (`public surface` and
  `smaller surface area` to `API`, `echo the scaffolding` to `echo the
  structure`).
- Label colons, colons before a list or an example, template strings such as
  `file:line`, and the literal `TL;DR` stay.
- Heading, numbered-step, fenced-block, and line counts are unchanged in
  every file. No frontmatter, code span, or fenced block changes.
- o200k tokens of the pstack/skills markdown tree 87,747 before, 87,766
  after (+19), because a period plus a capital tokenizes one token longer
  than a semicolon in a few places.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>

2026-09-07 17:00:12 -07:00

1.2 KiB

Raw Permalink Blame History

name, description, disable-model-invocation

name	description	disable-model-invocation
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.	true

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.

1.2 KiB Raw Permalink Blame History

Experience First

1.2 KiB

Raw Permalink Blame History