devrites 3.0.5 → 3.0.7

package/pack/generated/claude/skills/rite-polish/SKILL.md

@@ -5,12 +5,12 @@ argument-hint: "[target | bolder | quieter | distill | harden | normalize-only]"
 user-invocable: true
 ---
 
-# /rite-polish — finish before review
+# /rite-polish: finish before review
 
 The "finish" phase. **Always** code-polishes; **and** runs UI normalize +
 design polish when the feature touches UI. Self-review the work to ship
 quality *before* handing it to `/rite-review`. The two-phase split (code,
-UI) lives in `reference/code.md` and `reference/ui.md` — read each on demand,
+UI) lives in `reference/code.md` and `reference/ui.md`: read each on demand,
 don't load both up front.
 
 ## Operating rules
@@ -18,7 +18,7 @@ don't load both up front.
 - **Functionality complete first.** Polish runs after `/rite-prove` (full
   feature proven).
 - Feature scope only.
-- For UI: **NEVER polish without normalizing first** — decoration on drift is
+- For UI: **NEVER polish without normalizing first**: decoration on drift is
   banned.
 
 ## Orchestration
@@ -30,7 +30,7 @@ don't load both up front.
    Then run `devrites-engine preamble` for deterministic workspace orientation.
 1. **Read** `state.md`, `touched-files.md`, and the `git diff` for the active
    workspace (or `$ARGUMENTS` if a target was given).
-2. **Detect UI scope** — UI is touched if the diff or `touched-files.md`
+2. **Detect UI scope:** UI is touched if the diff or `touched-files.md`
    contains any of: `.tsx`, `.jsx`, `.vue`, `.svelte`, `.html`, `.css`,
    `.scss`, `.sass`, `.less`, `.styl`, component dirs (`components/`,
    `pages/`, `routes/`, `app/`, `views/`, `screens/`), Storybook stories,
@@ -43,29 +43,29 @@ don't load both up front.
    `design-brief.md` if present (the UX/UI contract `devrites-ux-shape` shaped at spec and
    `devrites-frontend-craft` refined while building) so the polish honors the agreed
    direction + states. **Read the `## Visual Verdict` table in `browser-evidence.md` if present:
-   its `FAIL` and `PARTIAL` rows are the normalize/quality-bar worklist** — fix the root cause of
+   its `FAIL` and `PARTIAL` rows are the normalize/quality-bar worklist**: fix the root cause of
    each (a missing state, an off-token CTA, an anti-slop hit), don't decorate around it. Then run
    **Phase 3 (normalize)** → **Phase 4 (UI polish)**. Honor argument modes:
-   - `bolder | quieter | distill | harden` — passed to Phase 4 as the
+   - `bolder | quieter | distill | harden`: passed to Phase 4 as the
      emphasis dial.
-   - `normalize-only` — run Phase 3 and stop (no Phase 4).
-5. **Re-verify after any code edit** — polish edits code, so the proof from
+   - `normalize-only`: run Phase 3 and stop (no Phase 4).
+5. **Re-verify after any code edit:** polish edits code, so the proof from
    `/rite-prove` no longer post-dates it. Run the relevant fast checks (the
    targeted tests for the touched files + typecheck/lint; browser re-check if UI
    changed) and record a **`Re-verification:`** line in `polish-report.md`. A
    polish that changed code without a green re-verification isn't finished.
-6. **Aggregate output** — both phases append to the single `polish-report.md`.
+6. **Aggregate output:** both phases append to the single `polish-report.md`.
 
 ## Refinement modes
 
 When the user (or your own assessment) names a direction the UI should move,
-pass it through to Phase 4. Modes don't bypass normalize + quality-bar work —
+pass it through to Phase 4. Modes don't bypass normalize + quality-bar work:
 they shape the polish *after* the system is aligned. See `reference/ui.md` for
 the mode table.
 
 > **Mid-flight discipline.** When tempted to polish UI without normalize, cite
 > clean lint as proof of quality, skip Phase 2 on a backend diff, or delete a
-> Chesterton's Fence — see [anti-patterns](reference/anti-patterns.md).
+> Chesterton's Fence: see [anti-patterns](reference/anti-patterns.md).
 
 ## Output → `polish-report.md`
 

package/pack/generated/claude/skills/rite-polish/reference/anti-patterns.md

@@ -1,4 +1,4 @@
-# rite-polish — anti-patterns
+# rite-polish: anti-patterns
 
 Load this when standing a non-trivial polish decision, or when tempted to
 skip normalize, polish without Chesterton's Fence, or cite clean lint/build
@@ -12,11 +12,11 @@ Pack-wide rationalizations + red flags (incl. lint-pass-as-quality): see
 | Excuse | Rebuttal |
 |---|---|
 | "Tests pass; the feature is done." | Tests don't measure ship-quality, design drift, anti-slop, or backend polish. |
-| "UI looks fine to me." | Must align to the design system + meet CWV/WCAG 2.2 — not match a personal taste. |
-| "Code is simple enough; no need to audit." | Measure first. If there's no hotspot, that's fine — but record "no hotspots found", don't skip silently. |
-| "It's a small UI change; polish without normalize is fine." | **NO** — decoration on drift is banned. Phase 3 runs before Phase 4, always. |
-| "Backend looks OK; skip Phase 2." | If the diff touched BE, Phase 2 runs — error responses, logging hygiene, queries, anti-slop. |
-| "Fewer lines is simpler, so this is done." | The bar is the comprehension test, not line count: would a new reader understand it *faster* than the original? A cryptic one-liner fails it. Fewer-but-slower is churn — revert it. |
+| "UI looks fine to me." | Must align to the design system + meet CWV/WCAG 2.2, not match a personal taste. |
+| "Code is simple enough; no need to audit." | Measure first. If there's no hotspot, that's fine, but record "no hotspots found", don't skip silently. |
+| "It's a small UI change; polish without normalize is fine." | **NO**: decoration on drift is banned. Phase 3 runs before Phase 4, always. |
+| "Backend looks OK; skip Phase 2." | If the diff touched BE, Phase 2 runs: error responses, logging hygiene, queries, anti-slop. |
+| "Fewer lines is simpler, so this is done." | The bar is the comprehension test, not line count: would a new reader understand it *faster* than the original? A cryptic one-liner fails it. Fewer-but-slower is churn: revert it. |
 
 ## Red Flags
 
@@ -24,7 +24,7 @@ Pack-wide rationalizations + red flags (incl. lint-pass-as-quality): see
 - No browser evidence saved for a UI polish.
 - Code polish ran without naming a single technique (guard clauses, Extract Method, ...).
 - Backend was touched but `polish-report.md` shows no Phase 2 section.
-- A "simplification" that changes observable behavior — that's not behavior-preserving.
+- A "simplification" that changes observable behavior. That's not behavior-preserving.
 - Reading a Chesterton's Fence as "looks dead" and deleting without explaining what it guards.
-- Simplifying, reflowing, or "tidying" a block marked `devrites:keep` / `simplify-ignore` — the marker is an explicit fence; leave it in place.
+- Simplifying, reflowing, or "tidying" a block marked `devrites:keep` / `simplify-ignore`: the marker is an explicit fence; leave it in place.
 - Hand-editing a >500-line simplification that a codemod / AST transform should have applied uniformly.

package/pack/generated/claude/skills/rite-polish/reference/backend-polish.md

@@ -1,6 +1,6 @@
 # Backend polish (when backend touched)
 
-Runs as Phase 2 of `/rite-polish` when the feature touches server-side code — handlers /
+Runs as Phase 2 of `/rite-polish` when the feature touches server-side code: handlers /
 controllers / services / routes / models / migrations / queries / jobs / workers / auth /
 schemas. Polishes the **server side** to ship-quality before review, the way UI normalize
 + polish does for the client side.
@@ -17,17 +17,17 @@ schemas. Polishes the **server side** to ship-quality before review, the way UI
 
 ### Error handling (consistent + meaningful)
 - [ ] **Consistent error response shape** across endpoints (e.g. an RFC 7807 problem
-      document or the project's existing convention). One shape — not three.
+      document or the project's existing convention). One shape, not three.
 - [ ] **Correct HTTP / protocol status codes** (4xx for client errors, 5xx for server
       errors; not 200 with `{ error: ... }`).
 - [ ] **Custom error classes** (or equivalent) so callers can distinguish error kinds.
-- [ ] **Fail closed** on auth/permission/transaction errors — deny + roll back; never
+- [ ] **Fail closed** on auth/permission/transaction errors: deny + roll back; never
       default to allow or partial commit (`error-handling.md`, `security.md`).
-- [ ] **Narrow `catch`** — no blanket `catch (e) {}` swallows. If you catch, recover or
+- [ ] **Narrow `catch`**: no blanket `catch (e) {}` swallows. If you catch, recover or
       rethrow with context.
 
 ### Logging hygiene
-- [ ] **Structured logs** (key/value or JSON) with **context** — request id, user/actor
+- [ ] **Structured logs** (key/value or JSON) with **context**: request id, user/actor
       id, operation, duration.
 - [ ] Log the **events that matter**: failures, access violations, validation rejections,
       retries, auth events.
@@ -36,22 +36,22 @@ schemas. Polishes the **server side** to ship-quality before review, the way UI
 - [ ] No `console.log` / debug prints left in. No noisy "got here" lines.
 
 ### Data & queries
-- [ ] **No N+1** — fetch in batches / use joins or includes.
-- [ ] **No unbounded result sets** — pagination/limits where data can grow.
+- [ ] **No N+1**: fetch in batches / use joins or includes.
+- [ ] **No unbounded result sets**: pagination/limits where data can grow.
 - [ ] **Parameterized queries** only; never string-built SQL/shell/HTML.
 - [ ] **Indexes** exist for new query patterns (or recorded as a follow-up if the project
       adds them by migration).
-- [ ] **Transaction boundaries** are right — one logical write = one transaction; rollback
+- [ ] **Transaction boundaries** are right: one logical write = one transaction; rollback
       on error; no partial commits.
 - [ ] Don't return more fields than the caller needs.
 
 ### API contract
 - [ ] Response shape matches the contract the spec set (and what the UI / consumers
-      expect — match against `references/` if any).
+      expect: match against `references/` if any).
 - [ ] **Idempotency** where applicable (PUT/DELETE; retry-safe POSTs with idempotency
       keys).
 - [ ] **Pagination, sorting, filtering** consistent with neighboring endpoints.
-- [ ] **Validation at the boundary** — type/length/format/range on untrusted input;
+- [ ] **Validation at the boundary**: type/length/format/range on untrusted input;
       reject what doesn't match (see `security.md` three-tier).
 
 ### Performance (measure first)
@@ -67,14 +67,14 @@ schemas. Polishes the **server side** to ship-quality before review, the way UI
 - [ ] No leftover `TODO`s without an owner/issue.
 - [ ] **Migrations** are reversible where reasonable; destructive ones have rollback notes.
 
-### Anti-slop (code patterns — see `anti-ai-slop.md`)
+### Anti-slop (code patterns: see `anti-ai-slop.md`)
 - [ ] No over-defensive null/length checks layered redundantly.
 - [ ] No useless wrapper functions ("`function getUser(id) { return User.find(id); }`").
 - [ ] No generic AI naming (`process_data`, `handle_thing`, `do_it`).
 - [ ] No "robust" code that catches everything and hides bugs.
-- [ ] Didn't go **beyond the spec** — implemented what the spec asked, no extras.
+- [ ] Didn't go **beyond the spec**: implemented what the spec asked, no extras.
 
 ## Rules
 - Feature scope only. Don't refactor unrelated server code.
 - Re-prove after changes: targeted tests + a real request/response observation.
-- A polish change that breaks a test isn't behavior-preserving — revert and reconsider.
+- A polish change that breaks a test isn't behavior-preserving: revert and reconsider.

package/pack/generated/claude/skills/rite-polish/reference/browser-polish-evidence.md

@@ -6,14 +6,14 @@ in `polish-report.md`).
 
 ## Required when a browser can run
 - Screenshots of the polished UI at the target viewports (375 / 768 / 1280 as relevant).
-  **Open each screenshot and describe what's actually visible** — a path is not proof.
+  **Open each screenshot and describe what's visible**: a path is not proof.
 - All key interaction states captured or exercised: hover, focus, active, disabled,
   loading, empty, error, success.
-- Console clean (no errors/warnings) — captured.
-- No layout shift on load — observed.
+- Console clean (no errors/warnings): captured.
+- No layout shift on load: observed.
 - Reduced-motion behavior checked if motion was added.
 - **Design references**: if the spec saved references in `.devrites/work/<slug>/references/`,
-  compare the polished UI against them — does it match the agreed target? Note any diffs.
+  compare the polished UI against them: does it match the agreed target? Note any diffs.
 
 ## Before/after
 Where polish changed something visible, capture a **before/after** pair. The pair is the

package/pack/generated/claude/skills/rite-polish/reference/code.md

@@ -5,27 +5,27 @@ code polish (Phase 1) and, when backend is touched, backend polish (Phase 2).
 
 ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`)
 
-- `coding-style.md` — Phase 1 (simplify, dead code, naming, comments).
-- `patterns.md` — Phase 1 simplification — avoid over-engineering.
-- `error-handling.md` — Phase 2 backend (no silent catches, consistent errors).
-- `performance.md` — Phase 2 backend (N+1s, query bounds).
-- `documentation.md` — keep touched docs current; record polish-time decisions.
+- `coding-style.md`: Phase 1 (simplify, dead code, naming, comments).
+- `patterns.md`: Phase 1 simplification: avoid over-engineering.
+- `error-handling.md`: Phase 2 backend (no silent catches, consistent errors).
+- `performance.md`: Phase 2 backend (N+1s, query bounds).
+- `documentation.md`: keep touched docs current; record polish-time decisions.
 
 ## Operating rules
 
 - **Never cite clean automation** (lint/build pass) as proof of good design or
   simplicity.
 - Feature scope only. Spec Drift Guard applies.
-- Re-run targeted tests after each change — a simplification that breaks a
+- Re-run targeted tests after each change: a simplification that breaks a
   test wasn't behavior-preserving.
 
-## Phase 1 — Code polish *(always)*
+## Phase 1: Code polish *(always)*
 
 Delegates the audit to `devrites-audit simplify`. Reduce complexity in the
 feature's touched code while **preserving exact behavior**. Scope = active
 feature only.
 
-- **Measure first, target hotspots** — deep nesting, long branchy functions,
+- **Measure first, target hotspots:** deep nesting, long branchy functions,
   high cyclomatic complexity, sprawling conditionals. Don't redistribute
   complexity, reduce it. Untargeted cleanup just moves decision points around.
 - **Behavior-preserving techniques** (name the one used per change): guard
@@ -35,25 +35,25 @@ feature only.
   into well-named parts), dedupe, inline single-use indirection, replace
   hand-rolled utils with the stdlib/existing helper, delete dead code this
   feature added.
-- **Chesterton's Fence** — understand *why* something exists before removing it.
-  If you can't explain a check, branch, or wrapper, you may not remove it —
+- **Chesterton's Fence:** understand *why* something exists before removing it.
+  If you can't explain a check, branch, or wrapper, you may not remove it:
   many "useless" lines guard a real edge case. A `devrites:keep` / `simplify-ignore`
   marker comment **is** an author's fence, made explicit: read it and leave the marked
-  block exactly as-is — never simplify, reflow, or "tidy" it. Honor the marker in place;
+  block exactly as-is: never simplify, reflow, or "tidy" it. Honor the marker in place;
   don't rewrite the file around it.
-- **Behavior preservation** — observable behavior stays identical; tests stay
-  green. If behavior would change, it's not simplification — it needs its own
+- **Behavior preservation:** observable behavior stays identical; tests stay
+  green. If behavior would change, it's not simplification. It needs its own
   acceptance + proof (and maybe drift handling). Prefer transformations with
   obvious equivalence.
-- **Don't over-reduce / proportionality** — inherent complexity is fine;
+- **Don't over-reduce / proportionality:** inherent complexity is fine;
   readability is the goal, not a metric. Forcing the complexity number down by
   *hiding* branches elsewhere is worse. Don't spend disproportionate effort on
   small, stable, rarely-touched code; target central/often-read code.
-- **Guardrails** — feature scope only, no project-wide refactor; don't delete
+- **Guardrails:** feature scope only, no project-wide refactor; don't delete
   suspected dead code **outside** this feature without asking; re-prove after
   simplifying (a simplification that breaks a test wasn't behavior-preserving);
   cleverness that's shorter but harder to read is not simpler.
-- **Rule of 500 — mechanize the big ones.** A simplification touching more than ~500 lines
+- **Rule of 500: mechanize the big ones.** A simplification touching more than ~500 lines
   (a rename, an API-shape change, a repeated idiom swap) is a job for a codemod / AST transform /
   `sed`, not hand-edits. Hand-editing at that scale is where transcription bugs and inconsistent
   application creep in; a scripted transform applies once, uniformly, and is reviewable as one diff.
@@ -61,14 +61,14 @@ feature only.
   imports/vars; tighten naming and comments in code this feature touched.
 - **The comprehension test (the completion criterion).** Every change must pass one question:
   *would a new team member understand this faster than the original?* If not, it's churn, not
-  simplification — revert it. Fewer lines that read slower fail this test; a clearer five lines
+  simplification: revert it. Fewer lines that read slower fail this test; a clearer five lines
   beat a cryptic one.
-- **Done when** — every touched change passes the comprehension test, every anti-slop charter
-  item in the touched code is cleared (the AI-tells do-not list — [anti-ai-slop.md](anti-ai-slop.md)
+- **Done when:** every touched change passes the comprehension test, every anti-slop charter
+  item in the touched code is cleared (the AI-tells do-not list: [anti-ai-slop.md](anti-ai-slop.md)
   Code section, `coding-style.md`) **and** the feature's targeted tests + build re-run green.
   An open charter item or a red check means Phase 1 isn't done.
 
-## Phase 2 — Backend polish *(if BE touched)*
+## Phase 2: Backend polish *(if BE touched)*
 
 See [backend-polish.md](backend-polish.md). For server-side scope (handlers,
 services, routes, models, migrations, queries, jobs, auth). Polish the server
@@ -76,21 +76,21 @@ side to ship-quality:
 
 - **Error responses consistent** + correct status codes + custom error classes
   + fail closed on auth/permission/transaction errors. No blanket `catch`es.
-- **Logging hygiene** — structured logs with context (request id, user, op);
+- **Logging hygiene:** structured logs with context (request id, user, op);
   log key events; **never** log secrets / tokens / PII. No leftover
   `console.log` / debug prints.
-- **Data & queries** — no N+1, no unbounded result sets, parameterized
+- **Data & queries:** no N+1, no unbounded result sets, parameterized
   queries, right transaction boundaries, return only what the caller needs.
 - **API contract** matches the spec (and any saved `references/`); idempotency
   where applicable; consistent pagination/sorting/filtering; validation at the
   boundary.
-- **Performance** — measure-first; obvious wins applied; no quadratic loops on
+- **Performance:** measure-first; obvious wins applied; no quadratic loops on
   growing collections (`devrites-audit perf`).
-- **Cleanup** — remove dead routes, unused endpoints + bad naming this feature
+- **Cleanup:** remove dead routes, unused endpoints + bad naming this feature
   added.
-- **Code anti-slop** — kill over-defensive layered null/length checks, useless
+- **Code anti-slop:** kill over-defensive layered null/length checks, useless
   wrappers, generic AI naming, "robust" catches that hide bugs, anything
-  outside the spec ([anti-ai-slop.md](anti-ai-slop.md) — Code section).
+  outside the spec ([anti-ai-slop.md](anti-ai-slop.md). Code section).
 
 ## Output → appends to `polish-report.md`
 

package/pack/generated/claude/skills/rite-polish/reference/harden-checklist.md

@@ -1,26 +1,26 @@
-# Harden checklist — UI against real-world inputs
+# Harden checklist: UI against real-world inputs
 
 Designs that only work on the happy path are not production-ready. `/rite-polish`
 Phase 2 (UI polish) uses this list to harden the feature against the inputs, errors,
 languages, and network conditions real users will throw at it.
 
-Feature scope only — don't harden screens this feature doesn't touch.
+Feature scope only: don't harden screens this feature doesn't touch.
 
 ## 1. Extreme content (the input axis)
 
 Walk every text-bearing surface in the feature with deliberately hostile data:
 
-- **Very long text** — names of 200+ chars, descriptions of 5000+ chars, titles
+- **Very long text:** names of 200+ chars, descriptions of 5000+ chars, titles
   longer than the viewport. Check truncation, wrapping, ellipsis, overflow.
-- **Very short / empty text** — single-char names, empty strings, names that are
+- **Very short / empty text:** single-char names, empty strings, names that are
   whitespace only. Check whether layout collapses or filters fail.
-- **Unicode** — emoji (`👨‍👩‍👧‍👦` — note grapheme clusters in count limits),<!-- pack-scan-ignore: intentional ZWJ in emoji edge-case example -->
+- **Unicode:** emoji (`👨‍👩‍👧‍👦`: note grapheme clusters in count limits),<!-- pack-scan-ignore: intentional ZWJ in emoji edge-case example -->
   zero-width joiners, RTL text (`مرحبا`), combining accents (`café` vs `café`).
-- **Numerics at scale** — `0`, negative numbers, `1.000.000`, `1234567890`, very
+- **Numerics at scale:** `0`, negative numbers, `1.000.000`, `1234567890`, very
   large currency. Check column width, formatter behaviour, locale separators.
-- **List sizes** — empty list, 1 item, 50 items, 1000+ items. Check pagination,
+- **List sizes:** empty list, 1 item, 50 items, 1000+ items. Check pagination,
   virtualisation, empty state, loading-state-then-empty.
-- **Adversarial input** — strings with `<script>`, `‮` (RTL override),<!-- pack-scan-ignore: intentional RTL-override example in adversarial-input checklist -->
+- **Adversarial input:** strings with `<script>`, `‮` (RTL override),<!-- pack-scan-ignore: intentional RTL-override example in adversarial-input checklist -->
   trailing whitespace, leading zeros. Confirm escaping at render time (not just
   on submit).
 
@@ -28,14 +28,14 @@ Walk every text-bearing surface in the feature with deliberately hostile data:
 
 Every async path needs designed behaviour for at least these states:
 
-- **Network failure** — offline, slow (throttled to 3G), timeout, intermittent.
-- **HTTP** — `400` (validation), `401` (signed-out), `403` (permission),
+- **Network failure:** offline, slow (throttled to 3G), timeout, intermittent.
+- **HTTP:** `400` (validation), `401` (signed-out), `403` (permission),
   `404` (gone), `409` (conflict), `429` (rate-limited), `500` / `502` /
   `503` (server).
-- **Partial success** — a bulk action where some items succeed and others fail.
-- **Stale data** — user reads, leaves the tab open for an hour, then acts on
+- **Partial success:** a bulk action where some items succeed and others fail.
+- **Stale data:** user reads, leaves the tab open for an hour, then acts on
   data that's since changed.
-- **Concurrent edit** — two windows of the same user, or two users on the same
+- **Concurrent edit:** two windows of the same user, or two users on the same
   record.
 
 For each: what does the UI show? Can the user recover, or are they stranded?
@@ -44,44 +44,44 @@ might miss.
 
 ## 3. Network / device conditions
 
-- **Slow connection** — does the surface show progress, or feel frozen?
-- **Offline** — does anything that *could* work offline still work (drafts,
+- **Slow connection:** does the surface show progress, or feel frozen?
+- **Offline:** does anything that *could* work offline still work (drafts,
   cached views), and is everything that can't gracefully blocked with a clear
   message?
-- **Touch + small screen** — every interactive element ≥ 24×24 CSS px (44×44
+- **Touch + small screen:** every interactive element ≥ 24×24 CSS px (44×44
   for primary touch targets). No drag-only flows.
-- **Keyboard-only** — full feature reachable without a mouse; visible focus;
+- **Keyboard-only:** full feature reachable without a mouse; visible focus;
   Esc closes overlays; Enter submits primary forms.
-- **Screen reader** — every control has a name; live regions for async
+- **Screen reader:** every control has a name; live regions for async
   feedback; reading order matches visual order.
-- **Reduced motion** — `prefers-reduced-motion` removes non-essential motion
+- **Reduced motion:** `prefers-reduced-motion` removes non-essential motion
   (no auto-carousel, no spring entrances).
-- **High zoom** — 200% text zoom; layout doesn't break, nothing overflows.
+- **High zoom:** 200% text zoom; layout doesn't break, nothing overflows.
 
 ## 4. Localisation / i18n
 
 Even single-locale features get hardened against the dimensions i18n exposes,
 because real text behaves the same way:
 
-- **String length variance** — German + Finnish + Japanese typically run +30–60%
+- **String length variance:** German + Finnish + Japanese typically run +30-60%
   longer than English; check buttons, table headers, badges.
-- **RTL** — Hebrew / Arabic mirror the layout. Even if the project is LTR-only,
+- **RTL:** Hebrew / Arabic mirror the layout. Even if the project is LTR-only,
   no RTL content should *break* anything.
-- **Date / number formats** — `1,234.56` vs `1.234,56` vs `1 234.56`. Currency
+- **Date / number formats:** `1,234.56` vs `1.234,56` vs `1 234.56`. Currency
   symbol placement.
-- **Pluralisation** — "1 item" vs "2 items" vs "0 items" — and locales with
+- **Pluralisation:** "1 item" vs "2 items" vs "0 items", and locales with
   more than two plural forms.
 
 ## 5. Permission / authorisation states
 
 Designed states for what the **current user** can / cannot do:
 
-- **Not signed in** — does the surface degrade, redirect, or 404 cleanly?
-- **Signed in, no permission** — message states what's missing and how to get
+- **Not signed in:** does the surface degrade, redirect, or 404 cleanly?
+- **Signed in, no permission:** message states what's missing and how to get
   it; doesn't show empty data as if it were a real empty state.
-- **Signed in, partial permission** — read-only mode designed (controls
+- **Signed in, partial permission:** read-only mode designed (controls
   disabled with reason; never silently no-oped).
-- **Signed in, owner / admin** — surfaces destructive actions appropriately and
+- **Signed in, owner / admin:** surfaces destructive actions appropriately and
   guards them.
 
 ## 6. Tooling-assisted checks (when available)
@@ -98,11 +98,11 @@ If the project has the tools, run them; capture evidence in `evidence.md`.
 
 For each finding raised by this checklist, classify by Phase-3 normalize bucket
 per [ui.md](ui.md):
-- **Token gap** — the design system already has the answer (`text-truncate`
+- **Token gap:** the design system already has the answer (`text-truncate`
   token, `state-empty` component) and it isn't being used.
-- **Component miss** — the project already has an `EmptyState`, `ErrorBanner`,
+- **Component miss:** the project already has an `EmptyState`, `ErrorBanner`,
   `OfflineNotice`, and a one-off was built instead.
-- **Flow / IA misalignment** — the error / empty / offline state doesn't follow
+- **Flow / IA misalignment:** the error / empty / offline state doesn't follow
   the project's pattern (e.g. inline where the project shows a banner; toast
   where the project uses inline).
 

package/pack/generated/claude/skills/rite-polish/reference/ui.md

@@ -7,7 +7,7 @@ the details. Skipping normalize means polishing drift.
 
 ## Operating rules
 
-- **NEVER polish without normalizing first** — decoration on drift is banned.
+- **NEVER polish without normalizing first:** decoration on drift is banned.
   Phase 3 runs before Phase 4, always.
 - Browser evidence required for UI polish when a browser can run
   ([browser-polish-evidence.md](browser-polish-evidence.md)).
@@ -17,14 +17,14 @@ the details. Skipping normalize means polishing drift.
 ## Why this order
 
 A beautiful component that ignores the project's tokens, components, and flow
-shape is *worse* than a plain one that fits — it adds a second system the team
+shape is *worse* than a plain one that fits. It adds a second system the team
 must maintain. Alignment is the precondition for polish, not an optional first
 step. **Fixing the symptom without naming the cause is how drift compounds:**
 patching a colour without adding the token bakes the next drift in; swapping a
 class without moving to the shared component leaves the next caller to redo the
 work.
 
-## Phase 3 — Normalize
+## Phase 3: Normalize
 
 Goal: this feature looks and behaves like it belongs in *this* product.
 
@@ -33,49 +33,49 @@ Goal: this feature looks and behaves like it belongs in *this* product.
    shared components, spacing/type scales, color roles, icon set, interaction
    & form patterns, neighboring screens.
 2. **Identify drift by root cause**, classifying each into one of **three
-   buckets** — the bucket dictates the fix:
+   buckets**: the bucket dictates the fix:
 
    | Bucket | What it is | Fix |
    |---|---|---|
-   | **Token gap** | A value is hard-coded where a token should carry it (colour, spacing, type size, radius, shadow). | Use the existing token; if a needed slot doesn't exist, propose adding it to the system — don't invent one inline. |
+   | **Token gap** | A value is hard-coded where a token should carry it (colour, spacing, type size, radius, shadow). | Use the existing token; if a needed slot doesn't exist, propose adding it to the system: don't invent one inline. |
    | **Component miss** | A one-off implementation exists where a shared component already covers the case (button, input, dialog, menu, table row). | Swap to the shared component. Don't fork it into the feature folder. |
-   | **Flow / IA misalignment** | The feature's flow shape, naming, or mental model doesn't match neighbouring features (modal where the project goes inline; save-on-blur where the project uses explicit submit; new vocabulary for an existing concept). | Reshape the flow / rename to the project's vocabulary. The most expensive bucket — and the most damaging if skipped. |
+   | **Flow / IA misalignment** | The feature's flow shape, naming, or mental model doesn't match neighbouring features (modal where the project goes inline; save-on-blur where the project uses explicit submit; new vocabulary for an existing concept). | Reshape the flow / rename to the project's vocabulary. The most expensive bucket, and the most damaging if skipped. |
 
    Sub-cases that map back to the buckets above: generic-AI-template styling →
    **Token gap** (hard-coded styling that should ride a token) or **Component
    miss** (rebuilt instead of reused); orphaned styles or components this
    feature created → **Component miss** (consolidate or remove); inconsistent
    IA / naming → **Flow / IA misalignment**.
-3. **Fix root causes, not symptoms** — use existing tokens, swap to shared
+3. **Fix root causes, not symptoms:** use existing tokens, swap to shared
    components, align flow shape with neighbors, consolidate duplication, remove
    obsolete styles created by this feature. Ask the user when a design-system
-   principle is genuinely ambiguous — don't guess the system's intent.
+   principle is genuinely ambiguous: don't guess the system's intent.
 
-## Phase 4 — UI polish
+## Phase 4: UI polish
 
 Only after functionality is complete **and** Phase 3 is done. Systematic detail
-pass against the UI quality bar below — zoom in, squint, use the thing. Little
+pass against the UI quality bar below: zoom in, squint, use the thing. Little
 things add up.
 
-Meet the **2026 quality bar** — CWV (LCP ≤ 2.5s / INP ≤ 200ms / CLS ≤ 0.1) and
+Meet the **2026 quality bar**. CWV (LCP ≤ 2.5s / INP ≤ 200ms / CLS ≤ 0.1) and
 WCAG 2.2 AA. Avoid [anti-ai-slop.md](anti-ai-slop.md). If the spec saved design
 references in `references/`, **match them**.
 
-Run the production-hardening sweep before declaring polish done — extreme
-inputs, errors, network, i18n, permission states — per
+Run the production-hardening sweep before declaring polish done (extreme
+inputs, errors, network, i18n, permission states) per
 [harden-checklist.md](harden-checklist.md). Polish that only works on the happy
 path isn't polish.
 
 ### UI quality bar (checklist)
 
-- [ ] **Aligned to the design system** — drift named and resolved by root cause (Phase 3)
+- [ ] **Aligned to the design system:** drift named and resolved by root cause (Phase 3)
 - [ ] **IA & flow** match neighboring features
-- [ ] **Visual hierarchy** — the primary action is obviously primary
+- [ ] **Visual hierarchy:** the primary action is obviously primary
 - [ ] **Spacing** uses design tokens consistently; rhythm reads as deliberate
 - [ ] **Alignment** perfect at every breakpoint
-- [ ] **Typography** hierarchy consistent; line length sane (65–75ch prose)
-- [ ] **Color & contrast** — semantic roles; text ≥ 4.5:1 (≥ 3:1 large/UI), WCAG 2.2 AA
-- [ ] **All interaction states** — hover, active, focus, disabled, selected
+- [ ] **Typography** hierarchy consistent; line length sane (65-75ch prose)
+- [ ] **Color & contrast**: semantic roles; text ≥ 4.5:1 (≥ 3:1 large/UI), WCAG 2.2 AA
+- [ ] **All interaction states**: hover, active, focus, disabled, selected
 - [ ] **Focus states visible** and **keyboard navigation** works
 - [ ] **Loading** states clear; **empty** states welcoming with a next action
 - [ ] **Error** states helpful (what happened + how to recover); **success** states clear
@@ -85,11 +85,11 @@ path isn't polish.
 - [ ] **Responsive** behavior correct across target viewports
 - [ ] **Target size** ≥ 24×24px (WCAG 2.2 AA); ≥ 44×44px for primary touch; **no drag-only** actions
 - [ ] **Motion** smooth (~60fps), purposeful; **reduced-motion** respected
-- [ ] **Performance basics** — no obvious jank, oversized images, or blocking work
+- [ ] **Performance basics:** no obvious jank, oversized images, or blocking work
 - [ ] **No console errors or warnings**
 - [ ] **No layout shift** on load
 - [ ] Works in the project's **supported browsers**
-- [ ] **Code quality** in touched UI files — no TODOs, console.logs, commented-out code
+- [ ] **Code quality** in touched UI files: no TODOs, console.logs, commented-out code
 
 ### Measurable bar (2026)
 
@@ -103,15 +103,15 @@ Cite the evidence in `browser-evidence.md`.
 
 ### Triage
 
-If it ships in 30 minutes, fix what users will actually notice (hierarchy,
+If it ships in 30 minutes, fix what users will notice (hierarchy,
 states, broken layout, bad copy) before micro-spacing. Don't introduce bugs
-while polishing — re-prove after changes.
+while polishing: re-prove after changes.
 
 ### Refinement modes (optional dials within Phase 4)
 
 | Mode | When | What it means |
 |---|---|---|
-| **bolder** | Surface reads safe / generic / forgettable. | Stronger hierarchy + weight contrast, one decisive accent, more committed scale. Reject generic-bold reflexes — gradients, glassmorphism, neon. |
+| **bolder** | Surface reads safe / generic / forgettable. | Stronger hierarchy + weight contrast, one decisive accent, more committed scale. Reject generic-bold reflexes: gradients, glassmorphism, neon. |
 | **quieter** | Surface reads loud / overstimulating. | Reduce chroma, increase whitespace, flatten elevation, soften motion. Personality stays; intensity drops. |
 | **distill** | Too many elements / colours / sizes competing. | Remove anything that doesn't earn its place: redundant copy, decorative shadows/borders. One primary action per screen. |
 | **harden** | Surface only works on the happy path. | Walk [harden-checklist.md](harden-checklist.md) explicitly. Design every error / empty / partial / offline state. |

package/pack/generated/claude/skills/rite-pov/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[candidate/link/question]"
 user-invocable: true
 ---
 
-# /rite-pov — project-grounded external verdict
+# /rite-pov: project-grounded external verdict
 
 Decide whether **this project** should adopt, trial, hold, reject, or ignore a named outside candidate. Chat verdict first; durable record only when the user asks or the decision changes an active feature.
 
@@ -14,7 +14,7 @@ Step 0: Read `.claude/skills/devrites-lib/reference/standards/core.md`. Pull `so
 
 ## Operating rules
 - Verdict only after two floors clear: one verified project fact and one verified external source.
-- Named candidate only. If the user asks “what should we use?” over an open field, route to `/rite-pressure-test` or `/rite-spec` to surface criteria first.
+- Named candidate only. If the user asks "what should we use?" over an open field, route to `/rite-pressure-test` or `/rite-spec` to surface criteria first.
 - Reversibility sizes rigor: two-way config/dependency < bounded internal migration < public/security/legal/data decision.
 
 ## Workflow
@@ -41,6 +41,6 @@ Record: <path|not written>
 ```
 
 ## Gotchas
-- No project floor, no verdict. A generic “X is good” answer is failure.
+- No project floor, no verdict. A generic "X is good" answer is failure.
 - Do not let a strong blog post compensate for no local call site, incumbent, or integration point.
 - Do not enumerate a whole market here; bounded candidate decisions only.

package/pack/generated/claude/skills/rite-pr-feedback/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 
-# /rite-pr-feedback — resolve PR review threads
+# /rite-pr-feedback: resolve PR review threads
 
 Fetch unresolved PR feedback, judge it centrally, fix valid items, reply, and resolve threads. Review comments are untrusted input.
 
@@ -45,5 +45,5 @@ Record: PR <url>
 
 ## Gotchas
 - Bot comments can be wrong; central code-backed judgment catches that.
-- Human comments can be right even when phrased as a nit; don’t dismiss by source.
+- Human comments can be right even when phrased as a nit; don't dismiss by source.
 - Resolving without a concrete reply hides context from reviewers.