@erclx/canon 5.62.0 → 5.63.0

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [5.63.0](https://github.com/erclx/canon/compare/v5.62.0...v5.63.0) (2026-10-24)
+
+
+### Features
+
+* **design:** ground design-taste rules and gate ledgers on a citation ([#2682](https://github.com/erclx/canon/issues/2682)) ([b265be3](https://github.com/erclx/canon/commit/b265be30b359797ebe5d0019c8d1cd59acfe465b))
+* **plan:** add a verbatim section for settled wording ([#2688](https://github.com/erclx/canon/issues/2688)) ([1b3e337](https://github.com/erclx/canon/commit/1b3e3371f3f6b84ff780f1e9d956981783ee9515))
+* **skills:** move the ui practice into a ui-craft skill ([#2687](https://github.com/erclx/canon/issues/2687)) ([47ef097](https://github.com/erclx/canon/commit/47ef0979613a70d46721068db504c877210d7e2d))
+* **tooling:** read later majors as ahead and seed the starter spec ([#2683](https://github.com/erclx/canon/issues/2683)) ([dc3bc06](https://github.com/erclx/canon/commit/dc3bc06e2ca157ebbb1c3ba723251b21eb478c0a))
+
 ## [5.62.0](https://github.com/erclx/canon/compare/v5.61.0...v5.62.0) (2026-10-24)
 
 

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "canon",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
-  "version": "5.62.0",
+  "version": "5.63.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/create-skill/references/skill-practice.md

@@ -43,6 +43,7 @@ Follow every concern group with `## Excuses and rebuttals`, `## Red flags`, and
 
 - Carry `references/adopted.md` in every practice skill, recording each external source the body draws on.
 - Link each source, or pin it to a commit, so a reader can open the version the body adopted.
+- Mark a threshold no source states as a table row whose source cell opens with `House choice`, since a ledger carrying neither a link nor one such row cites nothing and the audit fails it.
 - State what was adopted, what was declined, and why for each, so a later session extends the position rather than re-deriving it.
 - Draw first from the default shelf, [Software Engineering at Google](https://abseil.io/resources/swe-book/html/toc.html) and [Google's engineering practices](https://google.github.io/eng-practices/), and record a source from elsewhere the same way.
 

package/claude/skills/design-record/references/design.md

@@ -89,7 +89,7 @@ In an intent record, `## Colors` carries a `Role | Property | Intent` table and
 
 Add either optional section when the project has content for it:
 
-- `## Layout`: page width, breakpoints, and grid rules as current constraints. The surface-capture rule reads breakpoints here, so a project declaring none is captured at the 320 reflow floor alone.
+- `## Layout`: page width, breakpoints, and grid rules as current constraints. `ui-craft` captures at these breakpoints, so a project declaring none is captured at the 320 reflow floor alone.
 - `## Mark`: the logo's construction rules and the files that carry it
 
 ## The uncertainty tag

package/claude/skills/design-taste/REQUIREMENT.md

@@ -29,7 +29,8 @@ The output has no standard of quality either. A model with no stated direction d
 
 ## Out of scope
 
-- Accessibility, keyboard interaction, state coverage, forms, and rendered copy, which the `a11y`, `keyboard`, `ux-completeness`, `forms`, and `copy` rules own
+- Accessibility, keyboard interaction, state coverage, forms, and rendered copy, which `ui-craft` owns
+- The focus ring's floors, which `ui-craft` owns, though its weight is this skill's
 - The candidate loop and the pick, which `pick-by-eye` owns
 - The shape of the project's design document, which `design-record`'s design reference governs
 - Prose on the surface being designed, which `write-human` and `markdown-craft` own

package/claude/skills/design-taste/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design-taste
-description: Carries the layer model that decides which design decision settles first, the rules that keep a surface coherent across sections, and the catalog of defaults a model reaches for when nothing states a direction. Use when drafting or judging an interface, a page, or any rendered surface, when output reads generic or templated, when redesigning something that already exists, or when asked to "make this look designed", "why does this look like AI made it", "give it taste", "what layer is this decision at", or "grey-box this first". Do NOT use for accessibility, forms, or state coverage, which the `ui` governance rules carry, for the shape of the project's design document, which `design.md` governs, or to run the candidate loop, which is `pick-by-eye`.
+description: Carries the layer model that decides which design decision settles first, the rules that keep a surface coherent across sections, and the catalog of defaults a model reaches for when nothing states a direction. Use when drafting or judging an interface, a page, or any rendered surface, when output reads generic or templated, when redesigning something that already exists, or when asked to "make this look designed", "why does this look like AI made it", "give it taste", "what layer is this decision at", or "grey-box this first". Do NOT use for accessibility, forms, or state coverage, which `ui-craft` carries, for the shape of the project's design document, which `design.md` governs, or to run the candidate loop, which is `pick-by-eye`.
 metadata:
   family: build
 ---
@@ -58,7 +58,7 @@ A lower layer constrains every layer above it. Two consequences follow in opposi
 - Settling a higher layer over a broken lower one changes nothing, which is why a palette round against a broken composition is wasted
 - Judging a lower layer through a finished higher one is nearly impossible, which is why grey-boxing works
 
-The model is Jesse James Garrett's five planes from _The Elements of User Experience_ (2000), subdivided to the granularity a drafting round works at.
+The model is Jesse James Garrett's five planes from [The Elements of User Experience](http://www.jjg.net/elements/) (2000), subdivided to the granularity a drafting round works at.
 
 | Order | Layer       | The question it answers                                                    |
 | ----- | ----------- | -------------------------------------------------------------------------- |
@@ -101,6 +101,7 @@ Coherence is a property of the whole and every one of these is broken one sectio
 - **One theme.** No inverted section dropped between its neighbors. A reader must not feel they walked into a different product mid-scroll.
 - **One copy register.** Technical, editorial and promotional voices do not mix in one composition unless the brand states that they do.
 - **One light source.** Every shadow on the surface falls the same way, and a shadow is tinted toward the ground rather than pure black.
+- **One focus ring weight.** Chosen once and drawn the same on every control. The `ui-craft` skill owns its visibility, contrast, and floor, and this lock sets the weight above them.
 
 ## Working on something that already exists
 
@@ -148,9 +149,9 @@ Run `${CLAUDE_SKILL_DIR}/references/preflight.md` against the output. It is the
 
 ## What this delegates
 
-- Focus, keyboard, ARIA, alt text, and every accessibility floor: the `ui` governance rules, which fire on the same paths this skill does and are the single source
-- States, empty and loading coverage, destructive confirmation, truncation: the same rules
-- Rendered copy casing, button labels, error message shape: the same rules
+- Focus, keyboard, ARIA, alt text, and every accessibility floor: the `ui-craft` skill, which the same pointer rule loads beside this one and is the single source
+- States, empty and loading coverage, destructive confirmation, truncation: the same skill
+- Rendered copy casing, button labels, error message shape: the same skill
 
 ### Other skills
 

package/claude/skills/design-taste/references/adopted.md

@@ -1,17 +1,143 @@
 ---
 title: Adopted and declined
-description: Which external design catalogs this skill adopted from, which items it declined, and why, so a later session extends the position instead of re-deriving it
+description: Where each design-taste rule comes from, being a quoted authority, the community catalog of model-output tells, or a house threshold, plus what was declined and why
 ---
 
 # Adopted and declined
 
-External catalogs were read and filtered rather than imported. This file is the record, and a later session extends it rather than re-deriving it.
+Every rule in this skill traces to one of three origins. A reader arguing against a rule finds its origin here, and a session extending the skill adds a row rather than re-deriving one.
 
-## Adopted
+- **An authority.** A typographer, a usability lab, a platform guideline, or the CSS reference states the rule, and the row quotes the passage relied on.
+- **The catalog.** Community prompt skills recorded what models draw when nothing states a direction. A tell from them is an observation of model output, not established practice.
+- **A house choice.** The toolkit chose the threshold so a tell can be counted, and no source stands behind the number.
 
-**Adopted with no change.** The three equal cards, the centered hero over a wash, enumerated eyebrows, scroll cues, decorative status dots, atmospheric strips, the fake screenshot built from boxes, filler verbs, and placeholder that reads as placeholder. Each names a shape, each carries a replacement, and none depends on a stack.
+A rule a quoted passage only partly backs names the part it backs, and the rest sits in the catalog or the house class.
 
-**Adopted with the stack removed.** Source items naming an icon set, a component library, a font by name, or an animation package were rewritten to state what the rule is about. "Do not use Inter" became one family doing every job, since the defensible claim is about pairing and role separation rather than about one typeface.
+## Contents
+
+- [The layer model](#the-layer-model)
+- [Craft rules an authority states](#craft-rules-an-authority-states)
+- [Systems rules an authority states](#systems-rules-an-authority-states)
+- [Tells an authority states](#tells-an-authority-states)
+- [The catalog](#the-catalog)
+- [House choices](#house-choices)
+- [Declined from the catalogs](#declined-from-the-catalogs)
+- [Declined from the systems reference](#declined-from-the-systems-reference)
+- [Carried as a caution](#carried-as-a-caution)
+
+## The layer model
+
+The body's layer order subdivides the five planes of Jesse James Garrett's [The Elements of User Experience](http://www.jjg.net/elements/). Its second chapter states the dependency the order rests on, that "Each plane is dependent on the planes below it."
+
+The same passage gives the constraint running the other way, that "the choices available to us on each plane are constrained by the decisions we make about issues on the planes below it". The nine layers and the grey-box stage are the skill's own subdivision of those planes.
+
+## Craft rules an authority states
+
+Rows for `craft.md`, grouped by its sections.
+
+### Type detail
+
+Each rule below is stated by the type reference or the CSS property that implements it.
+
+| Rule                | Source                                                                                                                                                        |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Measure             | [Practical Typography](https://practicaltypography.com/line-length.html): "Aim for an average line length of 45–90 characters, including spaces."             |
+| Figures in columns  | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-numeric): `tabular-nums` sets figures "the same size, allowing them to be easily aligned" |
+| Small caps tracked  | [Practical Typography](https://practicaltypography.com/letterspacing.html): "always add 5–12% extra letterspacing to text in all caps or small caps"          |
+| Large type tighter  | The same page: typographers "will often remove letterspacing from lowercase text used at larger sizes"                                                        |
+| Orphans             | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/text-wrap): `balance` suits "a short number of lines, such as headings, captions, and blockquotes"     |
+| Hanging punctuation | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/hanging-punctuation): "An opening bracket or quote at the start of the first formatted line" hangs     |
+
+Casing is the `ui-craft` copy reference's, which `craft.md` points at rather than restating.
+
+### Optical size, hierarchy, and unfinished work
+
+The rows below back one bullet each. The error row backs the fix half of its bullet alone.
+
+| Rule                  | Source                                                                                                                                                          |
+| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Optical size          | [Wikipedia, Overshoot](https://en.wikipedia.org/wiki/Overshoot_%28typography%29): round letters overshoot "to achieve an optical effect of being the same size" |
+| Hierarchy from weight | [Practical Typography](https://practicaltypography.com/headings.html): with a bold heading, "you can also try reducing the point size"                          |
+| Where the reader is   | [NN/g](https://www.nngroup.com/articles/navigation-you-are-here/): "Navigation should not only show where you can go but also where you are now."               |
+| Error opens on a fix  | [NN/g](https://www.nngroup.com/articles/error-message-guidelines/): "offer some potential remedies"                                                             |
+
+That an apology should not lead the error is the catalog's observation, since the NN/g page allows one on a total failure.
+
+### Craft rules from the catalog
+
+The remaining `craft.md` rules are catalog observations of model output. They are optical centering, bottom-heavy padding, alignment across siblings, color and space carrying hierarchy, the shouting heading, every depth and texture rule, the dead link, the reused portrait, and the copy that reads unfinished.
+
+## Systems rules an authority states
+
+Rows for `systems.md`. The counts it states sit under house choices below.
+
+| Rule                         | Source                                                                                                                                                        |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Between groups beats within  | [NN/g](https://www.nngroup.com/articles/gestalt-proximity/): "Items close together are likely to be perceived as part of the same group"                      |
+| One gap everywhere fails     | The same page: a tight label reads as one group "compared to a larger margin before the next label-field pair"                                                |
+| Adjacent steps differ        | [Practical Typography](https://practicaltypography.com/headings.html): "Use the smallest increment necessary to make a visible difference."                   |
+| Fewer steps than feel enough | The same page: "Limit yourself to three levels of headings. Two is better."                                                                                   |
+| Weights beside sizes         | The bold heading passage under craft above                                                                                                                    |
+| Dark mode re-derived         | [Apple HIG](https://developer.apple.com/design/human-interface-guidelines/dark-mode): dark colors "aren't necessarily inversions of their light counterparts" |
+
+### Systems rules from the catalog
+
+Geometric spacing steps, space responding to the viewport, body size anchoring the scale, and line height moving opposite to size are catalog observations. Practical Typography gives a line spacing range for body text alone, so it does not back the last.
+
+Every palette rule but the dark mode row is catalog as well, being accent by rarity, one neutral temperature, the separation of surfaces from content, a semantic color kept off the accent, and the saturation budget.
+
+## Tells an authority states
+
+Two tells and one application UI rule rest on a source rather than on the catalog.
+
+| Rule                              | Source                                                                                                                                                  |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Unstyled platform control         | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/color-scheme): it adapts "The default colors of form controls"              |
+| Transparency with no checkerboard | [Wikipedia](https://en.wikipedia.org/wiki/Transparency_%28graphic%29): an editor "shows transparency by a special pattern, e.g. a checkerboard pattern" |
+| Shortcut beside its command       | [NN/g](https://www.nngroup.com/articles/ui-copy/): shortcuts sit "to the far right of the menu" and "alongside the command text in tool tips"           |
+
+## The catalog
+
+Every other tell in `tells.md`, and the ten defaults in the body, came from community prompt skills that recorded what models draw unguided. None of them is a design authority. Each tell is an observation of model output, falsifiable against a render, rather than established practice.
+
+- **[Taste-Skill](https://github.com/leonxlnx/taste-skill)** and its fork **[claude-taste-skill](https://github.com/nxpatterns/claude-taste-skill)** supplied the composition, content, surface, and motion tells
+- **[UI/UX Pro Max](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill)** was first read through a vendor listing and later from its repository. Its ranking puts accessibility first, and its lookup corpus was declined.
+- **[frontend-design](https://github.com/anthropics/skills/tree/main/skills/frontend-design)**, Anthropic's skill, supplied the five clusters current AI design falls into, restated in `tells.md`
+- **[Impeccable](https://github.com/pbakaus/impeccable)** supplied what a visual direction may lend an application screen and the category self-check, restated in `kinds.md`. Its themed browser surfaces lie behind the platform control tell.
+
+No sentence from any of them is copied. Each idea is restated and cited here.
+
+### Adopted with no change
+
+The three equal cards, the centered hero over a wash, enumerated eyebrows, scroll cues, decorative status dots, atmospheric strips, the fake screenshot built from boxes, filler verbs, and placeholder that reads as placeholder. Each names a shape, each carries a replacement, and none depends on a stack.
+
+### Adopted with the stack removed
+
+Source items naming an icon set, a component library, a font by name, or an animation package were rewritten to state what the rule is about. "Do not use Inter" became one family doing every job, since the defensible claim is about pairing and role separation rather than about one typeface.
+
+## House choices
+
+Each threshold below is the toolkit's, chosen so a tell can be counted rather than judged.
+
+| Threshold                     | Source                                                                                         |
+| ----------------------------- | ---------------------------------------------------------------------------------------------- |
+| About eight spacing values    | House choice: past it, a count tells a scale from arithmetic on a finished surface             |
+| Five to seven type steps      | House choice: fewer forces size to carry every level, and more holds steps nobody tells apart  |
+| Two or three section tiers    | House choice: enough tiers for rhythm, few enough that each section takes one                  |
+| One marquee                   | House choice: a second sliding strip is where the device reads as filler                       |
+| Two consecutive splits        | House choice: a third alternation is where the pattern reads as filler                         |
+| Four first-screen text items  | House choice: a label, a headline, a supporting line, and the actions, so a fifth is countable |
+| One layout family, five items | House choice: a repeated shape and a long run become counts a reviewer can check               |
+
+The uppercase label count belongs to the `ui-craft` copy reference, whose own ledger records it as a house choice.
+
+### The focus ring's weight
+
+One more lock is the toolkit's own choice.
+
+| Threshold       | Source                                                                                                   |
+| --------------- | -------------------------------------------------------------------------------------------------------- |
+| One ring weight | House choice: a ring varying by component reads as several products. The `ui-craft` skill owns the floor |
 
 ## Declined from the catalogs
 
@@ -21,7 +147,7 @@ Each item below is real advice placed in the wrong surface, or a rule that decid
 
 **Banned fonts by name.** A font ban is a value ban, and a value belongs to the project's own design document rather than to a skill that loads everywhere. A project that wants a typeface ruled out rules it out there.
 
-**Numeric intensity dials.** Every external source carries a 1-to-10 scale for variance, motion and density. A session picks a middle value and reports compliance. That satisfies the rule, decides nothing, and leaves no trace a later reader could check it by. The declared read carries the same information in a sentence somebody can argue with.
+**Numeric intensity dials.** Every external source carries a 1-to-10 scale for variance, motion and density. A session picks a middle value and reports compliance, which decides nothing and leaves no trace a later reader could check. The declared read carries the same information in a sentence somebody can argue with.
 
 ### Rules owned elsewhere
 
@@ -29,17 +155,19 @@ Each item below is real advice placed in the wrong surface, or a rule that decid
 
 **The official-package map.** A table routing a brief to Fluent, Material, Carbon, Polaris, Primer or a government design system. It is real advice and it is a stack decision a project takes once, so it belongs in that project's own records rather than in a skill that loads on every design round.
 
-### Scope
+### Scope and tooling
 
 **Scoping out application UI.** The largest source covers landing pages, portfolios and redesigns, and excludes dashboards, data tables and multi-step product UI. Those exclusions are most of what software projects actually build, so the kinds reference carries application UI as a first-class kind.
 
+**A design detector hook.** Impeccable runs one after UI edits. A detector belongs beside an automated review probe once the tells are grounded, not inside a skill that carries guidance.
+
 ## Declined from the systems reference
 
 Each failed the test in `REQUIREMENT.md`. Recorded so they are not argued again.
 
 - **Control sizing and proportion.** An unguided model produces reasonable controls without instruction, so it fails the first question.
 - **Specific ratios for a type scale**, such as a named musical interval. Falsifiable and arbitrary, and a project picking a different ratio is not wrong.
-- **Named palettes or banned hues.** A value ban, which belongs to the project's design document. This is where every external catalog of this kind ends up, and it is why theirs cannot be imported.
+- **Named palettes or banned hues.** A value ban, which belongs to the project's design document. Every external catalog of this kind ends up here, which is why theirs cannot be imported.
 - **A minimum contrast figure.** A threshold with a number, which the accessibility rules own.
 - **Imagery as a system.** There is no scale to establish. What a model gets wrong about images is using fake ones, which `tells.md` covers, so the layer stays thin on purpose.
 

package/claude/skills/design-taste/references/craft.md

@@ -39,7 +39,7 @@ Reaching for size is the first instinct and the weakest tool.
 - **Measure.** Body text running the full width of a wide container is unreadable however good the type is.
 - **Figures in columns.** Numbers that change, in a table, a price or a timer, need tabular figures or the column jitters.
 - **Tracking by size.** Large type wants tighter letter spacing, small uppercase labels want looser. Body text wants whatever the face was drawn with.
-- **Casing.** Sentence case for headings and labels. `interface-casing` states the rule and its exceptions.
+- **Casing.** Sentence case for headings and labels. The `ui-craft` copy reference states the rule and its exceptions.
 
 ## Depth and texture
 

package/claude/skills/design-taste/references/kinds.md

@@ -26,12 +26,18 @@ Dashboards, tools, admin surfaces, agentic and assistant interfaces. The reader
 - **Optimizes for** throughput and state legibility. How fast can the reader see what is happening and act on it.
 - **High density is correct.** Cramming is a failure and spaciousness is also a failure, since a surface that shows six rows where thirty fit costs the reader a scroll per glance.
 - **The states carry the design weight.** Loading, empty, error, partial and stale are most of what the reader sees on this kind, so they are composed rather than handled.
-- **Whether each state exists** is the `ui` rules' question, not this file's.
+- **Whether each state exists** is the `ui-craft` skill's question, not this file's.
 - **An agentic surface adds three states.** Work running with something to read, work that needs the person, and work finished with a result to inspect. Each rests visibly, never as a spinner.
 - **Chrome is persistent and quiet.** Navigation, status and context stay put and stay recessive, since they are read constantly and looked at rarely.
 - **Motion is feedback, not entrance.** A thing moving should be reporting that something changed.
+- **The visual direction lends four things.** Type, palette, density, and one signature move. Layout, the navigation model, and the controls stay the category's own.
+- **A borrowed interface lends the same four.** A direction taken from a terminal or an instrument panel gives only what transfers, and the working screen never dresses up as its source.
+- **Check each render against its category.** Cover the product name and ask whether the screen reads as a tool of its kind and whether the task can be done from it.
+- **A command shows its shortcut.** A menu row carries the keys at its right edge and a tooltip names them beside the command, in the platform's own spelling.
 - **Where a rule from another kind is wrong here:** generous whitespace, entrance animation on every panel, and hero-scale typography all read as a marketing page wearing a product's clothes.
 
+The direction limits and the category check restate [Impeccable](https://github.com/pbakaus/impeccable)'s guidance for app screens. The shortcut placement follows [NN/g](https://www.nngroup.com/articles/ui-copy/).
+
 ## Content and long-form
 
 Documentation, articles, reference pages, learning material. The reader arrived to read and will stay if reading is comfortable.
@@ -46,7 +52,7 @@ Documentation, articles, reference pages, learning material. The reader arrived
 
 ## Kinds this file does not cover
 
-- **Transactional flows** such as checkout, sign-up and settings are read as application UI. Their distinctive rules, state coverage and error recovery, sit in the `ui` governance rules.
+- **Transactional flows** such as checkout, sign-up and settings are read as application UI. Their distinctive rules, state coverage and error recovery, sit in the `ui-craft` skill.
 - **Terminal and text-mode surfaces** have no layout engine and their own color rules, stated where the writing surface is decided rather than here.
 
 A read naming any of the three above takes the body's rules and says it has no per-kind guidance, naming the surface that governs it. A read naming a kind this file does not list at all says so rather than borrowing the nearest section.

package/claude/skills/design-taste/references/preflight.md

@@ -32,7 +32,7 @@ Each box here is a count from `tells.md`.
 
 - [ ] No layout family used twice. Eight sections carry at least four families
 - [ ] No three consecutive sections sharing the image-and-text split
-- [ ] Small uppercase labels above headings number no more than one per three sections, per `interface-casing`
+- [ ] Small uppercase labels above headings number no more than one per three sections, per the `ui-craft` copy reference
 - [ ] At most one horizontal marquee
 
 ### Content and first screen
@@ -90,7 +90,7 @@ The detail boxes come from `craft.md`.
 Every word on the surface states what is true of it.
 
 - [ ] No filler verbs
-- [ ] Sentence case throughout, with exceptions per `interface-casing`
+- [ ] Sentence case throughout, with exceptions per the `ui-craft` copy reference
 - [ ] Every claim about what the product does is a thing it does
 
 ## Motion
@@ -102,4 +102,4 @@ Every word on the surface states what is true of it.
 ## Handover
 
 - [ ] The weakest thing on the surface is named out loud, per `pick-by-eye` Step 3, and fixed where naming it would embarrass the work
-- [ ] The floor the `ui` governance rules carry has been applied, not assumed
+- [ ] The floor the `ui-craft` skill carries has been applied, not assumed

package/claude/skills/design-taste/references/tells.md

@@ -1,6 +1,6 @@
 ---
 title: Machine tells in design
-description: The visual defaults a model reaches for when nothing states a direction, each with what to do instead, plus the countable composition limits and the first-screen budget
+description: The looks current AI design clusters in and the visual defaults a model reaches for when nothing states a direction, each with what to do instead, plus the countable composition limits and the first-screen budget
 ---
 
 # Machine tells in design
@@ -9,6 +9,20 @@ Each item below is a shape rather than a value, which is why no ban list of colo
 
 The skill body carries the ten most common of these, and this is the same catalog at full length. An item is a default to reach past, not a prohibition, so a brief that explicitly asks for one gets it, chosen rather than defaulted into.
 
+## Where current AI design clusters
+
+Unguided output does not spread evenly. It lands in a handful of looks, and following every other rule in this catalog does not keep a page out of them.
+
+- **The warm paper page.** A cream ground near `#F4F1EA` under a serif display set at strong contrast, accented in clay or terracotta.
+- **Black with one loud accent.** A near-black ground lit by a single acid green or vermilion.
+- **The newspaper imitation.** Hairline rules, square corners, and tight columns borrowed from print.
+- **The card kit.** Every block in a matching rounded box under the same faint grey shadow, with gradient washes for decoration.
+- **Template chrome.** A tracked uppercase label over each heading, meta joined by middle dots, monospace for small data, an arrow on link text, and off-black for black.
+
+A page drafted under this skill landed on the first look at exactly that cream, which is why the list sits apart from the shapes below. Each look suits a brief that names it. Where the brief leaves an axis open, choose something else on purpose.
+
+The five restate the calibration list in Anthropic's [frontend-design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) skill.
+
 ## Composition
 
 - **The three equal cards.** Three identical boxes in a row under a heading. Reach for a two-column alternation, an asymmetric grid, a list with one item given weight, or a single worked example.
@@ -39,6 +53,13 @@ The skill body carries the ten most common of these, and this is the same catalo
 - **The gradient as a substitute for a decision.** A gradient over a section, a heading, or a button set because flat looked plain. Flat composition is fixed by composition, not gradient.
 - **Uniform radius and uniform elevation.** Every card at the same radius with the same shadow flattens hierarchy. Let the thing that matters differ.
 
+## Platform surfaces
+
+The browser and the operating system draw some parts of every page, and a themed surface leaves them at their defaults unless someone decides otherwise.
+
+- **An unstyled platform control.** A dark surface whose scrollbars, selects, or checkboxes still wear the light defaults. Declare the page's color scheme and take the accent from the palette.
+- **A transparent color with no checkerboard.** An alpha swatch over a flat ground, where a faint red and a solid pink look alike. Draw it over a checkerboard, the way image editors do.
+
 ## Typography
 
 - **Scale as the only hierarchy.** An enormous heading over uniform body text. Weight, color, spacing and measure carry hierarchy at lower cost.
@@ -52,15 +73,15 @@ The skill body carries the ten most common of these, and this is the same catalo
 - **The permanent loop.** Anything animating forever with no input. It costs attention on every frame and earns none back.
 - **Motion on arrival for everything.** Every section fading up on scroll. Reserve entrance motion for what genuinely needs the eye.
 - **Motion claimed but absent, or present but unclaimed.** A "restrained" surface animating on every scroll, or a "fluid" one sitting still, has decided nothing. Ship the motion or drop the claim.
-- **Motion that ignores a reduced-motion preference.** A correctness failure the `ui` governance rules own, not a taste one. It sits here so a motion pass does not read this catalog as all motion owes.
+- **Motion that ignores a reduced-motion preference.** A correctness failure the `ui-craft` skill owns, not a taste one. It sits here so a motion pass does not read this catalog as all motion owes.
 
 ## The countable limits
 
-These rules carry numbers, so they are checked by counting rather than by judging. Every one came out of production testing by people shipping model-drafted pages.
+These rules carry numbers, so they are checked by counting rather than by judging. Each number is a house choice made so the tell can be counted, and `adopted.md` records it as one.
 
 - **A layout family appears once.** Once a section uses a shape, no other section on the surface uses it. Eight sections need at least four distinct families.
 - **Two consecutive splits, never three.** Alternating image sides reads as considered twice and as filler by the third. Break it with a full-width section, a vertical stack, or a grid.
-- **One small uppercase label per three sections.** The most over-reached default in model output, with the count in `interface-casing`. Usually delete it, since position already says what a section is.
+- **One small uppercase label per three sections.** The most over-reached default in model output, counted in `ui-craft`. Usually delete it, since position already says what a section is.
 - **One marquee.** Two sliding strips on one surface read as filler rather than as a device.
 - **Cells equal items.** A grid with a hole in it, or a blank tile at the end, means the grid was shaped before the content was counted. Reshape it.
 - **Over five items wants a different component.** Group into clusters, split into columns, give each item a card, make them scrollable, or collapse the tail behind a disclosure.
@@ -75,4 +96,4 @@ These rules carry numbers, so they are checked by counting rather than by judgin
 
 ## Adopted, declined, and why
 
-The record of which external catalog items were adopted, which declined, and why sits in `adopted.md` beside this file.
+Most items here are observations of what models draw unguided, gathered from community prompt skills rather than from a design authority. The record of which were adopted, which declined, and why sits in `adopted.md` beside this file, with the few an authority states and the links to the catalog behind the rest.

package/claude/skills/plan-feature/SKILL.md

@@ -38,7 +38,7 @@ Read these in parallel from the project root, skipping any that do not exist:
 
 Also read `canon/DESIGN.md` when the feature touches code or UI, for visual intent and component rules, with values read from the stylesheet its lead names. Skip it for prose, docs, catalog, or config-only changes. For a UI feature, read `canon/design/index.md` too, if it exists, for the surfaces with an accepted design.
 
-Coding standards live in `.claude/rules/`. Claude Code loads them automatically, and path-scoped rules apply to the files they match. For a UI feature, load `canon:design-taste` whether or not `canon/DESIGN.md` exists.
+Coding standards live in `.claude/rules/`. Claude Code loads them automatically, and path-scoped rules apply to the files they match. For a UI feature, load `canon:ui-craft` for how it behaves and `canon:design-taste` for how it looks, whether or not `canon/DESIGN.md` exists.
 
 ### Read the domain's context entry
 
@@ -86,7 +86,7 @@ Every `- Suggested:` line takes senior judgment, picking the best option in one
 - Suggest a real default when best practice, the codebase, or prior context points to one
 - Before `## Files to touch`, load `canon:codebase-layout` for a new path (its reason) and `canon:api-design` for a changed verb, flag, output, record shape, or endpoint. Report either if missing.
 - Fill `## Design references` with the `canon/design/<surface>/` folder for each surface a UI file in `## Files to touch` renders, and write `None identified.` in a project with no folder
-- Write `## Verification` as one bullet per outcome naming the test or command that proves it
+- Write `## Verification` as one bullet per outcome naming the test or command that proves it, with a grep bullet per `## Verbatim` block of settled wording
 - Write `## Review focus` as the inputs or states that would break the change, carrying the risk you understood to the executor and the reviewer
 
 ### Sources and size

package/claude/skills/plan-feature/references/plan.md

@@ -75,6 +75,7 @@ The document opens with `# Feature: <short title>` and one paragraph stating wha
 | `## Current behavior`  | each command run against the thing being changed and what it showed         | When the change touches something that runs       |
 | `## Constraints`       | durable rules the work must respect                                         | When supplied                                     |
 | `## Files to touch`    | each file with a one-line reason                                            | Always                                            |
+| `## Verbatim`          | settled wording that lands unchanged in an existing file, one H3 per block  | When wording is settled                           |
 | `## Design references` | the tracked design folders the change builds against, each with its surface | When Files to touch names a rendered-surface file |
 | `## Verification`      | the test or command that proves each outcome                                | Always                                            |
 | `## Risks`             | conflicts, coupling, and the tricky spots                                   | Always                                            |
@@ -171,6 +172,16 @@ A batch in a fan-in set declares its side in a constraint bullet, ``Fan-in membe
 
 A constraint naming a `.canon/ready/` folder is a third shape beside the hold and the shared path. It makes that folder's files the verbatim source for the paths this plan's `## Files to touch` lists, per `ready.md`, so the executing session copies those paths rather than authoring them.
 
+### Verbatim
+
+A `## Verbatim` section carries wording someone settled, landing in an existing file exactly as written. Wording the planner only proposes stays a `- Suggested:` question, and a whole new file goes in the ready folder per `ready.md`, so the two never describe the same file.
+
+- Give each block an H3 naming it, then a lead sentence with the action, the full path, and the anchor, then a fenced `text` block holding the wording
+- Name the action as Add, Insert, or Replace. A Replace quotes the old line in the lead's code span.
+- Write the block as the project's formatter leaves it, since a formatter that re-pads a table row or rewraps a line makes the grep fail on correct text
+- Name the outcome in a grep bullet and put a command past 200 characters in a fenced `bash` block under it, since `S4` reports a longer bullet
+- Give each block one `## Verification` bullet running `grep -cF -e` on its whole first line against its file, so a reworded line fails a check the reviewer already runs.
+
 ### Design references
 
 A plan whose `## Files to touch` names a rendered-surface file (`.tsx`, `.jsx`, `.astro`, `.vue`, `.svelte`, `.html`, or `.css`) carries this section. It tells the building session which accepted design to open before it writes a line.
@@ -258,9 +269,9 @@ This contract inverts the one an intake folder keeps, where an empty slot means
 
 ## Template
 
-Each H3 below shows where a section groups once it passes 5 bullets. A section of 5 or fewer drops its H3s and keeps its bullets flat, except `## Risks`, which takes an H3 per risk at any count.
+Each H3 below shows where a section groups once it passes 5 bullets. A section of 5 or fewer drops its H3s and keeps its bullets flat, except `## Risks` and `## Verbatim`, which take an H3 per risk or block at any count.
 
-```markdown
+````markdown
 # Feature: <short title>
 
 <One paragraph on what is being built and why now.>
@@ -300,6 +311,16 @@ The files below share <the reason>.
 
 - `<path/to/file>`: <reason>
 
+## Verbatim
+
+### <Block name>
+
+Add as <where> in `<path/to/file>`, after <anchor>.
+
+```text
+<the wording, as the formatter leaves it>
+```
+
 ## Design references
 
 - `canon/design/<surface>/`: <the surface it governs>
@@ -335,4 +356,4 @@ The questions below decide <what>, numbered across the whole section.
 ## Sources
 
 - [<title>](url), backing <decision>: "<passage relied on>"
-```
+````

package/claude/skills/review-craft/SKILL.md

@@ -49,7 +49,7 @@ An axis whose condition the diff meets is not optional. When the security or the
 Read each of these when the diff reaches what it names.
 
 7. **Security.** Read `${CLAUDE_SKILL_DIR}/references/security.md` when the diff runs a command, writes or deletes a file, takes outside input, touches a secret, adds a dependency, or changes a default.
-8. **Rendered output.** Read `${CLAUDE_SKILL_DIR}/references/ui.md` when the diff touches a file that paints, or when the pull request carries an evidence comment.
+8. **Rendered output.** Read `${CLAUDE_SKILL_DIR}/references/ui.md` when the diff paints or the pull request carries evidence. Judge behavior by `ui-craft` and the look by `design-taste`.
    - A file that paints is markup, a stylesheet, a component, a template, or a design token
    - A stylesheet diff says what the author changed and only the screenshot says what a user sees, so the reference opens the images and checks whether any exist
 9. **Developer experience and operations.** Ports, hooks, scripts, config, and scaffold defaults a consumer installs.

package/claude/skills/role-worker/SKILL.md

@@ -23,6 +23,7 @@ This body states the role, the boundaries, and the channel, and starts no step o
 - Resolve `.canon/plans/`, `.canon/tasks/`, `.canon/review/`, and `.canon/ready/` at the main worktree root, never the linked worktree. Being gitignored, they are absent there rather than empty.
 - Report a plan that fails to resolve as unreadable from here, naming the main-root path. Reporting the task as having no plan is wrong about the world, and a reader cannot tell the two apart.
 - Build the plan the launch named. Never write a second one when the path fails to resolve, since a row citing a plan already has one.
+- Load `ui-craft` before editing a rendered surface, pointer rule or not
 - Keep a task list from launch, one item per slice, and tick each as its slice lands. Skip it on a host that offers no list tool, since the list is for the operator watching and not a gate.
 
 ### Ready folders and the draft mark
@@ -60,7 +61,7 @@ A plan carrying a `**Design references:**` section names the accepted design for
 
 - Open each cited folder's light and dark images and its frame HTML before the first edit to that surface
 - Take sizes, spacing, and colors from the frame HTML rather than from the image
-- Report a reference that does not resolve in the working tree, naming the path, rather than building without it
+- Report a missing reference by its path rather than building without it
 - Leave `None identified.` as it stands and build without a reference
 
 ## Scope after dispatch

package/claude/skills/ui-checklist/SKILL.md

@@ -48,7 +48,7 @@ The checkbox stays `- [ ]` followed by the action and the result, since the evid
 
 ## Boxes no engine reads
 
-The UI review runs axe over every route it reaches, so a box restating what axe checks, such as contrast, a missing name, or a page title, adds a drive and catches nothing. Derive a box instead for each behavior below that the changed surface carries:
+The UI review runs axe over every route it reaches, so a box restating what axe checks, such as contrast, a missing name, or a page title, adds a drive and catches nothing. Derive a box instead from the `ui-craft` references the changed surface reads, for each behavior below that it carries:
 
 - **Hover content.** Content shown on hover or focus stays while the pointer moves onto it, and Escape dismisses it, per WCAG 1.4.13.
 - **Keyboard trap.** Tab and Shift+Tab leave every widget the change added, per WCAG 2.1.2.

package/claude/skills/ui-craft/REQUIREMENT.md

@@ -0,0 +1,29 @@
+---
+name: ui-craft
+description: Why the UI behavior practice lives in one skill every role reads by name, and where it stops beside design-taste and design-record
+---
+
+# UI craft requirement
+
+## Gap
+
+Without this skill, the UI behavior practice reaches a session only as path rules a target has to sync, so a project holding the plugin without governance builds a component with none of it. A role that plans, builds, or reviews a rendered change has no name to load the practice by, and each one restates the part it remembers.
+
+## Must
+
+- Every rule the retired ui practice rules carried sits in a reference, unchanged in wording, with its source row in a ledger beside the reference
+- A rendered change reaches accessibility, keyboard, and state coverage on every read, and the other references by the change that needs them
+- A rendered change that is about to be handed over reaches the capture reference
+- A planning, building, or reviewing role reaches the skill by name, with or without the governance pointer installed
+
+## Must not
+
+- Reword a moved rule in the move, since a wording change is a separate change with its own ledger row
+- Restate the look, being layout, type, color, or the layer order
+- Be reached only by an author typing its name, since the `craft` pointer rule and the planning, building, and reviewing skills are its callers
+
+## Out of scope
+
+- How a surface looks, which `design-taste` owns
+- The design folder, its references, and the comparison a pull request shows, which `design-record` and the `design-reference` rule own
+- The visual checklist a reviewer reads, which `ui-checklist` owns