cursor__plugins/pstack/skills/poteto-mode/playbooks/visual-parity.md at main

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

Visual parity

You own pixel-exact equivalence. The baseline is the spec. You do not touch it. Equivalence is verified by image diff, not by eye.

Establish the baseline first, before any migration: a visual regression harness that screenshots the current component across its states, plus the target when matching two implementations. No baseline, no parity claim. A blocking prerequisite, not a follow-up.
Anti-shortcut clauses, stated and held: no harness modifications, no baseline tampering, no component restructuring to make a diff pass. If the baseline looks wrong, stop and ask, don't edit it.
Migrate one component at a time. Parallelize across worktrees, one owner per component (the separate-before-serializing-shared-state principle skill). Shared primitives migrate first as a blocking phase.
Verify each component against its baseline via image diff on the matching surface via the control skill. A nonzero diff is a fail. Investigate the pixel delta. /loop per component until the diff is zero.
Run Opening a PR per component or per safe batch.

Reply: components migrated, the diff result for each, the baseline harness location, what's left.

1.2 KiB Raw Permalink Blame History

Visual parity

1.2 KiB

Raw Permalink Blame History