@erclx/canon 5.41.0 → 5.43.0

package/claude/skills/deploy-app/references/vercel.md

@@ -10,7 +10,8 @@ Run these steps once the body's Pick step resolves to Vercel. Read `vercel <comm
 ## Guard
 
 - If `vercel whoami` fails, stop: `❌ vercel is not authenticated. Run vercel login, then re-invoke.`
-- If `command -v jq` fails, stop: `❌ jq is not installed. Install it, then re-invoke.` Step 3 pipes its output into a secret, and a missing reader would set that secret empty while `gh secret list` still lists its name.
+- If `command -v jq` fails, stop: `❌ jq is not installed. Install it, then re-invoke.`
+- Step 3 pipes jq's output into a secret, and without jq the secret is set empty while `gh secret list` still lists its name
 
 ## Step 1: create and link the project
 

package/claude/skills/deprecation-migration/references/adopted.md

@@ -5,49 +5,68 @@ description: Which external sources on deprecation and migration this skill adop
 
 # Adopted and declined
 
-External sources were read and filtered rather than imported. This file is the record. A later session extending the skill adds to it rather than re-arguing an item already settled here.
+External sources were read and filtered rather than imported. This file is the record, and a later session extending the skill adds to it rather than re-arguing an item settled here.
 
-## Adopted
+## Adopted from the default shelf
 
-### From the default shelf
+### Deprecation
 
-**Deprecation.** [Software Engineering at Google, chapter 15](https://abseil.io/resources/swe-book/html/ch15.html). Adopted from it:
+[Software Engineering at Google, chapter 15](https://abseil.io/resources/swe-book/html/ch15.html) supplies four positions the body states.
 
-- Advisory and compulsory deprecation as the two types, with compulsory carrying a removal date. The body allows compulsory only once a replacement has shipped, which the chapter implies and the four questions make explicit.
-- Warnings that are actionable and relevant: a warning names what the caller does, and surfaces where the caller uses the old surface.
-- Deprecation as a process with an owner, since the chapter observes that unowned deprecation work makes no progress. Adopted as the fourth decision question and the rule against an advisory deprecation left open with no owner.
-- Finding consumers before removal, which the chapter does with static analysis across one repository. Generalized into the zero-consumers check across caller kinds, since a target project rarely has a whole-company code index and its callers often live outside the repository.
+- **Two types.** Advisory and compulsory, the second carrying a removal date. The body allows compulsory only once a replacement ships, which the chapter implies and the four questions make explicit.
+- **Actionable, relevant warnings.** A warning names what the caller does, and surfaces where the caller uses the old surface.
+- **An owner.** The chapter observes that unowned deprecation work makes no progress. Adopted as the fourth decision question and the rule against an ownerless advisory deprecation left open.
+- **Finding consumers before removal.** The chapter's static analysis over one repository becomes the zero-consumers check across caller kinds, since a target's callers often live outside it.
 
-**The Churn Rule.** [Software Engineering at Google, chapter 1](https://abseil.io/resources/swe-book/html/ch01.html), under "Policies That Don't Scale": infrastructure teams move their internal users to new versions themselves, or update in place in a backward-compatible way. Adopted as the group on migrating callers yourself, with the backward-compatible path kept for callers the owner cannot edit.
+### Migrating callers yourself
 
-### The decision and the bridges
+[Software Engineering at Google, chapter 1](https://abseil.io/resources/swe-book/html/ch01.html), under "Policies That Don't Scale", has infrastructure teams move their internal users to new versions themselves, or update in place in a backward-compatible way.
 
-**Deprecation and migration.** Addy Osmani's `agent-skills`, pinned at addyosmani/agent-skills@2686b620, [`skills/deprecation-and-migration/SKILL.md`](https://github.com/addyosmani/agent-skills/blob/2686b620/skills/deprecation-and-migration/SKILL.md). Adopted from it:
+Adopted as the group on migrating callers yourself, with the backward-compatible path kept for callers the owner cannot edit.
 
-- The five-question deprecation decision, cut to four. Its unique-value and maintenance-cost questions merge into one question about what keeping the surface costs. Its per-consumer migration-cost question drops, since the Churn Rule puts that cost on the owner rather than weighing it per caller. The owner question from the book takes the freed place.
-- The rule never to deprecate without a replacement, as the third decision question.
-- The strangler and adapter patterns, stated as when each fits rather than as worked code tied to one stack.
+## Adopted for the decision and the bridges
 
-#### Migration, zombie code, and red flags
+Addy Osmani's `agent-skills`, pinned at addyosmani/agent-skills@2686b620, [`skills/deprecation-and-migration/SKILL.md`](https://github.com/addyosmani/agent-skills/blob/2686b620/skills/deprecation-and-migration/SKILL.md), supplies the decision and the bridge patterns.
 
-- Expand, migrate, contract, lifted out of its schema section and stated for any surface as three separate changes.
-- Zombie code, narrowed to code that is unowned, uncalled, and still built, and settled by the same zero-consumers check rather than a list of staleness signals.
-- The rationalizations and red flags that carry across stacks, reworded for any surface rather than a service or a column. Two excuse rows come from here:
-  - The row on a search that found nothing, from its red flag against removing code without verifying zero active consumers.
-  - The row on adding the new one and dropping the old one now, generalized from its rationalization about adding a column and dropping the old one in the same migration.
+### The decision
+
+Its five-question deprecation decision is cut to four. The unique-value and maintenance-cost questions merge into one about what keeping the surface costs, and the per-consumer migration-cost question drops, since the Churn Rule puts that cost on the owner.
+
+- The owner question from the book takes the freed place
+- The rule never to deprecate without a replacement is the third decision question
+- The strangler and adapter patterns are stated as when each fits rather than as worked code tied to one stack
+
+### Migration, zombie code, and red flags
+
+The migration shape and the excuse rows carry across stacks once reworded for any surface rather than a service or a column.
+
+- Expand, migrate, contract, lifted out of its schema section and stated for any surface as three separate changes
+- Zombie code, narrowed to code that is unowned, uncalled, and still built, and settled by the zero-consumers check rather than a list of staleness signals
+- The excuse row on a search that found nothing, from its red flag against removing code without verifying zero active consumers
+- The excuse row on adding the new one and dropping the old one now, generalized from its rationalization about a column added and dropped in one migration
 
 ## Declined
 
-**Its database schema section.** The column rename worked example, the tested down path, batched backfills, and concurrent index builds. Declined because a project's persistence rule owns schema changes, and restating them here puts two owners on one rule. Only the expand, migrate, contract shape was lifted, generalized beyond schemas.
+Each item below was read and left out, with the reason it changes nothing a session does here.
+
+### The schema section and its mechanisms
+
+**Its database schema section.** The column rename worked example, the tested down path, batched backfills, and concurrent index builds. A project's persistence rule owns schema changes, so only the expand, migrate, contract shape was lifted, generalized beyond schemas.
 
 **Feature flag migration.** Declined because it is one way to run a strangler, and naming a flag mechanism ties the body to a runtime a target may not have.
 
-**The traffic percentages in its strangler phases.** Declined because they describe a service behind a router, and most surfaces a session retires, such as a function, a flag, or a file, have callers rather than traffic.
+### Numbers that fit one project
+
+**The traffic percentages in its strangler phases.** They describe a service behind a router, and most surfaces a session retires, such as a function, a flag, or a file, have callers rather than traffic.
+
+**The thresholds in its zombie signs and rebuttals.** No commits in six months, and comparing costs over two or three years. Declined for the reason the body states no deprecation window, since a number fits one project's cadence and not another's.
+
+### Defaults and framing
 
-**"Default to advisory" as a standing default with no exit.** Kept advisory as the starting state, and declined leaving it open, since an advisory deprecation with no date and no owner is the stalled case the body exists to prevent.
+**"Default to advisory" as a standing default with no exit.** Advisory is kept as the starting state and leaving it open is declined, since an advisory deprecation with no date and no owner is the stalled case the body exists to prevent.
 
-**The thresholds in its zombie signs and rebuttals.** No commits in six months, and comparing costs over two or three years. Declined for the same reason the body states no deprecation window: a number fits one project's cadence and not another's.
+**"Code is a liability" and design-time deprecation planning as sections.** Framing a session already accepts by loading the skill. The cost question carries the first, and designing a new surface for removal belongs to the skill shaping that surface.
 
-**"Code is a liability" and design-time deprecation planning as sections.** Declined as framing a session already accepts by loading the skill. The cost question carries the first, and designing a new surface for removal belongs to the skill shaping that surface.
+### Ceremony
 
 **The celebration step and the deprecation notice template.** Declined because neither changes what a session does, and the template's example names a package runner and a migration script tied to one stack.

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

@@ -15,14 +15,22 @@ External catalogs were read and filtered rather than imported. This file is the
 
 ## Declined from the catalogs
 
+Each item below is real advice placed in the wrong surface, or a rule that decides nothing.
+
+### Values and dials
+
 **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.
 
+### Rules owned elsewhere
+
 **The em dash ban as a design rule.** One source bans the character on a page as a visual tell. The markdown standard already bans it for prose reasons and `canon markdown audit` gates that from package data, so restating it here would put a second copy of an enforced rule behind an unenforced pointer.
 
 **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
+
 **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.
 
 ## Declined from the systems reference
@@ -33,7 +41,7 @@ Each failed the test in `REQUIREMENT.md`. Recorded so they are not argued again.
 - **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.
 - **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` already covers, so the layer stays thin on purpose rather than by oversight.
+- **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.
 
 ## Carried as a caution
 

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

@@ -11,7 +11,7 @@ Read this when a layout satisfies the ordering, the locks and the tells, and sti
 
 The eye and the arithmetic disagree, and the eye is the one being served.
 
-- **Centering by the numbers is not centering.** A triangle inside a circle, an icon beside a label, a glyph inside a round button all sit visually left or low when centered by their bounding box. Nudge until it looks right, usually a pixel or two.
+- **Centering by the numbers is not centering.** A triangle in a circle, an icon beside a label, or a glyph in a round button sits left or low when centered by its box. Nudge it, usually a pixel or two.
 - **Equal vertical padding reads bottom-heavy.** A block with matching top and bottom padding looks like it is sinking. Give the bottom slightly more.
 - **Optical size beats declared size.** A circle and a square at the same declared size do not read as the same size. The circle needs to be larger.
 - **Type alignment follows the letterform, not the box.** A quotation mark, a bullet or an opening parenthesis at the start of a line should hang outside the text edge so the text itself lines up.
@@ -56,6 +56,8 @@ Reaching for size is the first instinct and the weakest tool.
 
 ### Content and copy
 
+Copy reads unfinished in the same way.
+
 - Every item dated identically, which no real collection ever is.
 - An exclamation mark in a success message. Confidence is quieter than that.
 - An error opening on an apology rather than on what to do next.

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

@@ -12,8 +12,8 @@ Read this once the declared read names a kind. The body's rules hold on every ki
 Landing pages, campaign pages, portfolios. The reader has never used the thing and owes it no attention.
 
 - **Optimizes for** comprehension in the first screen, then one clear next action.
-- **Composition carries the weight.** A marketing page is judged on section order and variation before anything else, which is why a palette round against a flat composition changes nothing a reader notices.
-- **Vary the section shape.** Alternate alignment, container width and the ratio between sections. A page where every section is a centered heading over centered body reads as a template regardless of its values.
+- **Composition carries the weight.** A marketing page is judged on section order and variation first, so a palette round against a flat composition changes nothing a reader notices.
+- **Vary the section shape.** Alternate alignment, container width and the ratio between sections. Every section a centered heading over centered body reads as a template whatever its values.
 - **Low density.** Whitespace is the argument that the thing is considered. This is the one kind where less information on screen is usually better.
 - **Every claim names a real thing.** A page asserting what a tool does, illustrated by something the tool did not produce, breaks its own thesis in the place it is making it.
 - **Motion is permitted and rationed.** Entrance motion for what genuinely leads the eye, nothing looping forever.
@@ -25,8 +25,9 @@ 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 not edge cases on this kind, they are most of what the reader sees, so they are composed rather than handled. Whether each exists at all is the `ui` rules' question and not this one.
-- **An agentic surface adds three states of its own:** work in progress with something to read while it runs, work that needs the person before it continues, and work that finished with a result to inspect. Each needs a visible resting place and none should be a spinner.
+- **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.
+- **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.
 - **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.
@@ -41,12 +42,12 @@ Documentation, articles, reference pages, learning material. The reader arrived
 - **Navigation is a map.** A reader who cannot see where they are in the whole cannot judge whether to keep going, which is what a scrollspy or a persistent outline buys.
 - **Code, tables and figures are first-class.** They are what the reader scans for, so they are styled as content rather than as interruptions.
 - **Motion is almost always wrong.** Movement during reading competes with reading.
-- **Where a rule from another kind is wrong here:** density tuned for an application surface makes long prose unreadable, and marketing whitespace between every paragraph breaks a section into unrelated fragments.
+- **Where a rule from another kind is wrong here:** application density makes long prose unreadable, and marketing whitespace between every paragraph breaks a section into unrelated fragments.
 
 ## Kinds this file does not cover
 
-- **Transactional flows** such as checkout, sign-up and settings are read as application UI. Their distinctive rules are state coverage and error recovery, which the `ui` governance rules already carry.
-- **Presentation surfaces** such as slide decks are drafted by `draft-slides`, which carries the deck's own design rules. Take the layer ordering and the floor from the body and the rest from that skill.
+- **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.
+- **Presentation surfaces** such as slide decks are drafted by `draft-slides`, which carries the deck's design rules. Take the layer ordering and the floor from the body and the rest from it.
 - **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

@@ -28,6 +28,8 @@ Skip nothing on the ground that it is obviously fine. A rule is on this list bec
 
 ### Section rhythm
 
+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`
@@ -35,6 +37,8 @@ Skip nothing on the ground that it is obviously fine. A rule is on this list bec
 
 ### Content and first screen
 
+The grid and the first screen are shaped to the content counted.
+
 - [ ] Grid cells equal content items, with no blank tile filling a gap
 - [ ] Lists over five items use something other than a longer list
 - [ ] The first screen carries the point and the primary action without scrolling
@@ -46,12 +50,16 @@ Skip this group where the surface draws on a system already settled.
 
 ### Space and type
 
+The scales come from `systems.md`.
+
 - [ ] Every gap comes from one scale, and the distinct spacing values number under about eight
 - [ ] Space between groups exceeds space within them
 - [ ] The type scale carries five to seven steps, each visibly different from its neighbors
 
 ### Color
 
+Each box is a relationship, never a value.
+
 - [ ] The accent is rare enough to read as an accent
 - [ ] Neutrals sit in one family at one temperature
 - [ ] Adjacent surfaces separate by a little and content separates from ground by a lot
@@ -64,6 +72,8 @@ Skip this group where the surface draws on a system already settled.
 
 ### Type detail
 
+The detail boxes come from `craft.md`.
+
 - [ ] No orphaned word closing a heading
 - [ ] Body text measure is capped
 - [ ] Changing numbers set in tabular figures
@@ -77,6 +87,8 @@ Skip this group where the surface draws on a system already settled.
 
 ### Wording
 
+Every word on the surface states what is true of it.
+
 - [ ] No filler verbs
 - [ ] Sentence case throughout, with exceptions per `interface-casing`
 - [ ] Every claim about what the product does is a thing it does

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

@@ -14,8 +14,9 @@ Nothing below states a value. A value belongs to the project's own design docume
 An unguided model reaches for whatever number looks right at each point, which produces a surface with thirty spacing values and no rhythm.
 
 - **Every gap comes from one scale.** Count the distinct spacing values on a finished surface. More than about eight means there is no scale, only arithmetic.
-- **The steps grow, they do not add.** A scale stepping 4, 8, 12, 16, 24, 32, 48, 64 gives usable distinctions at both ends. One stepping 10, 20, 30, 40 gives four values that all read the same at large sizes and none that work at small.
-- **Space between groups exceeds space within them.** This is the one spacing rule carrying real meaning, since proximity is what tells a reader which things belong together. A surface with one gap everywhere has told the reader nothing, and it is the most common spacing failure in generated output.
+- **The steps grow, they do not add.** A scale stepping 4, 8, 12, 16, 24, 32, 48, 64 gives usable distinctions at both ends. One stepping 10, 20, 30, 40 reads alike at large sizes and fails at small.
+- **Space between groups exceeds space within them.** The one spacing rule carrying meaning, since proximity tells a reader which things belong together.
+- **One gap everywhere** tells the reader nothing, and it is the most common spacing failure in generated output.
 - **Section rhythm is two or three tiers, not a value per section.** Pick the tiers, then assign each section to one.
 - **Space responds to viewport, type mostly does not.** A layout that scales every value together arrives at a phone reading like a shrunken desktop.
 
@@ -31,12 +32,12 @@ An unguided model reaches for whatever number looks right at each point, which p
 
 The layer a model is worst at, and the layer where rules are hardest to make falsifiable. Everything below is a relationship, since a rule naming a value is a value ban and values belong to the project.
 
-- **An accent is defined by rarity, not by hue.** A color used on a third of the surface is a ground, whatever it was chosen as. If the accent appears more than a handful of times per screen, there is no accent.
+- **An accent is defined by rarity, not by hue.** A color on a third of the surface is a ground, whatever it was chosen as. An accent seen more than a handful of times per screen is none.
 - **Neutrals are one family at one temperature.** Warm grays beside cool grays read as a mistake rather than as a decision, and it is a mistake a model makes by pulling neutrals from different sources.
 - **Adjacent surfaces separate by a little, content separates from ground by a lot.** Generated output routinely inverts this: cards that shout against the page, and text that does not.
-- **A semantic color is not the accent.** Error, success and warning carry meaning. Borrowing the accent for one of them makes the accent mean something, and it stops being available for anything else.
-- **Dark mode is re-derived, not inverted.** The relationships above are what carry across, and the values are settled again. A palette flipped by algorithm gets the relationships wrong in both directions.
-- **Saturation has a budget across the surface, not per color.** Several colors each individually reasonable produce a surface that reads loud, which is why the rule is about the total rather than about any one value.
+- **A semantic color is not the accent.** Error, success and warning carry meaning. Borrowing the accent for one makes the accent mean something, and it stops being available for anything else.
+- **Dark mode is re-derived, not inverted.** The relationships above carry across and the values are settled again. A palette flipped by algorithm gets the relationships wrong in both directions.
+- **Saturation has a budget across the surface, not per color.** Several colors each reasonable alone produce a surface that reads loud, so the rule is about the total rather than any one value.
 
 ## Considered and declined
 

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

@@ -5,39 +5,38 @@ description: The visual defaults a model reaches for when nothing states a direc
 
 # Machine tells in design
 
-Each item below is a shape rather than a value, which is why no ban list of colors or fonts reaches any of them. Read this before handing over anything a model drafted. Skip it on a small change to a surface that already has a settled direction.
+Each item below is a shape rather than a value, which is why no ban list of colors or fonts reaches any of them. Read this before handing over anything a model drafted, and skip it on a small change to a surface that already has a settled direction.
 
-The skill body carries the ten most common of these. This is the same catalog at full length, so an item appearing in both is one list rather than two.
-
-An item is a default to reach past, not a prohibition. A brief that explicitly asks for one gets it, and the point is that it was chosen rather than defaulted into.
+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.
 
 ## Composition
 
-- **The three equal cards.** Three identical boxes in a row under a heading is the most-reached-for feature section in existence. Reach for a two-column alternation, an asymmetric grid, a list with one item given weight, or a single worked example.
-- **One section shape repeated down the page.** A page where every section is a centered heading over a centered body reads flat whatever its palette. Vary alignment, container width and the ratio between sections.
+- **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.
+- **One section shape repeated down the page.** Every section a centered heading over a centered body reads flat whatever its palette. Vary alignment, container width and the ratio between sections.
 - **The centered hero over a dark wash.** Centered headline, centered subhead, two buttons, gradient behind. Reach for an asymmetric split, a full-bleed artifact, or content that starts immediately.
-- **Decoration standing in for structure.** Hairline grids, crosshairs, floating rules and corner marks added so a page feels designed. Use them where they organize real content and remove them where they do not.
-- **The corner floater.** A large left-aligned section heading with a small explanatory paragraph floating in the top right, aligned to nothing. Put the sub-text under the heading or build a real two-column header.
+- **Decoration standing in for structure.** Hairline grids, crosshairs, floating rules and corner marks added so a page feels designed. Keep them only where they organize real content.
+- **The corner floater.** A large left-aligned heading with a small paragraph floating top right, aligned to nothing. Put the sub-text under the heading or build a real two-column header.
 
 ## Content and labels
 
 - **Enumerated eyebrows.** `001 / Capabilities`, `Phase 02`, `Step 1`, `Stage One`. The content is the label. Where progression genuinely matters, use the verb.
 - **Poetic section labels.** "From the field", "On our desks", "Currently on the bench". Use the plain functional label or drop the label.
-- **Atmospheric strips.** City, time zone, temperature, coordinates, build version, last-sync time, placed for texture rather than information. Keep one only where it carries real state a reader acts on.
+- **Atmospheric strips.** City, time zone, temperature, coordinates, build version, last-sync time, placed for texture. Keep one only where it carries real state a reader acts on.
 - **Scroll cues.** "Scroll", an animated wheel, a downward arrow with a label. A reader looking at the top of a page knows what scrolling is.
-- **Decorative status dots.** A coloured dot before every nav item, list row or badge. Keep it only where it reports genuine state, and then sparingly.
-- **Filler verbs.** A verb chosen for its warmth rather than for what it reports, such as `elevate`, `unleash`, `empower` or `next-generation`. Name the thing the surface does.
-- **Placeholder that reads as placeholder.** Generic person names, egg avatars, invented company names of the `Acme` family, one portrait reused for several people, every item dated identically. Real collections are uneven and specific.
-- **Invented precision.** A figure like 4.1x or 48k either came from real data, is marked as sample, or does not appear. There is no fourth case. Inventing a number to look engineered is the version of this that gets shipped, because it reads as confidence.
+- **Decorative status dots.** A colored dot before every nav item, list row or badge. Keep it only where it reports genuine state, and then sparingly.
+- **Filler verbs.** A verb chosen for warmth rather than for what it reports, such as `elevate`, `unleash`, `empower` or `next-generation`. Name the thing the surface does.
+- **Placeholder that reads as placeholder.** Generic names, egg avatars, `Acme`-family companies, one portrait for several people, every item dated alike. Real collections are uneven and specific.
+- **Invented precision.** A figure like 4.1x or 48k came from real data, is marked as sample, or does not appear. An invented number gets shipped, because it reads as confidence.
 - **The fake screenshot built from boxes.** A product UI simulated out of styled rectangles inside a hero. Show the real thing, a real capture, or nothing.
-- **Copy nobody re-read.** Read every visible string once as a reader rather than as its author, before handing anything over. Rewrite what is grammatically broken, what carries a pronoun with no antecedent on the page, and what reaches for charm it has not earned. Plain beats clever and wrong, which is what a model drafting copy produces by default.
+- **Copy nobody re-read.** Read every visible string once as a reader rather than its author before handing over. Plain beats clever and wrong, which is what a model drafting copy produces by default.
+- **What the re-read rewrites.** A string that is grammatically broken, carries a pronoun with no antecedent on the page, or reaches for charm it has not earned.
 
 ## Surface and palette
 
 - **Glow as depth.** Outer glows and neon rims standing in for elevation. Use a border, a tint, or a real shadow with direction.
 - **Pure black and pure white as grounds.** Both are harsher than nearly any surface wants. Move off the extreme.
-- **Saturation everywhere.** An accent at full saturation next to neutrals that are also tinted leaves nothing to anchor on. Desaturate the neutrals and let one accent carry.
-- **The gradient as a substitute for a decision.** A gradient covering a section, a heading, or a button set, applied because the flat version looked plain. Flat is usually the fix for flat composition, not gradient.
+- **Saturation everywhere.** A full-saturation accent beside tinted neutrals leaves nothing to anchor on. Desaturate the neutrals and let one accent carry.
+- **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.
 
 ## Typography
@@ -49,28 +48,28 @@ An item is a default to reach past, not a prohibition. A brief that explicitly a
 
 ## Motion
 
-- **Motion nobody can justify.** Before adding any animation, say in one sentence what it communicates: hierarchy, sequence, feedback, or a state that changed. "It looked good" is not one of those. A sentence that will not come is the answer, and the animation goes.
+- **Motion nobody can justify.** Before adding any animation, name the hierarchy, sequence, feedback, or changed state it communicates. A sentence that will not come means it goes.
 - **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 not present, or present but not claimed.** A surface described as restrained that animates on every scroll, or one described as fluid that sits still, has decided nothing. Ship the motion or drop the claim.
-- **Motion that ignores a reduced-motion preference.** Not a taste failure at all. It is a correctness failure the `ui` governance rules own, listed here only so a motion pass does not read this catalog as the whole of what motion owes.
+- **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.
 
 ## The countable limits
 
-These are the rules with 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. Every one came out of production testing by people shipping model-drafted pages.
 
 - **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-left and image-right reads as considered twice and as filler by the third. Break it with a full-width section, a vertical stack, a grid, or anything else.
-- **One small uppercase label per three sections.** The tiny wide-tracked line above a heading is the single most over-reached default in model output. `interface-casing` carries the count. The fix is usually to delete it, since a section's position already says what it is.
+- **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 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.** A longer list is the lazy answer. Group into clusters, split into columns, give each item a card, make them scrollable, or collapse the tail behind a disclosure.
+- **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.
 
 ## The first screen
 
-- **It fits.** The point and the primary action are both visible without scrolling. If the copy will not fit, the copy is too long or the type is too large, and the second is the more common cause.
+- **It fits.** The point and the primary action are both visible without scrolling. Copy that will not fit is too long or set too large, and the second is the more common cause.
 - **At most four text elements.** A label or a brand strip, a headline, a short supporting line, and the actions. That is the whole budget.
-- **Everything else moves down.** A small tagline under the actions, a trust strip, a pricing hint, a feature list, a row of faces. Each of those is a section of its own below, not a fifth element above.
+- **Everything else moves down.** A tagline under the actions, a trust strip, a pricing hint, a feature list, a row of faces. Each is a section of its own below, not a fifth element.
 - **Plan the type scale against the asset.** A headline wrapping to four lines is a size error rather than a length error.
 - **Logos go under it, never inside it.** A credibility row shares no space with the point.
 

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

@@ -7,9 +7,11 @@ description: The layer, property, pattern and process terms this skill uses, so
 
 Terms used by `design-taste` and by the skills it is loaded alongside. It changes when a design round needs a name it cannot look up here.
 
-This glossary departs from one rule in `glossary.md`: an entry does not name where the term first appears. The material is five short files a reader can scan, so a location per entry costs more than it returns.
+This glossary departs from one rule in `glossary.md`, since an entry does not name where the term first appears. The material is five short files a reader can scan, so a location per entry costs more than it returns.
 
-Every other rule there holds, and the one deciding membership holds strictly. A term appears here once this skill's own material uses it, never ahead of that, and the section below records what was considered and left out.
+- Every other rule there holds, and the one deciding membership holds strictly
+- A term appears here once this skill's own material uses it, never ahead of that
+- The last section records what was considered and left out
 
 ## Layers
 
@@ -28,7 +30,7 @@ Ordered by when each settles, not alphabetically, since the order is the content
 ## Properties
 
 - **Casing**: whether text is set upper, lower, title or sentence case, treated as a hierarchy decision rather than a typing one.
-- **Density**: how much information a given area carries. High density is correct in an application surface and reads as clutter on a marketing one, which is why it belongs to the kind rather than to taste.
+- **Density**: how much information a given area carries. Correct in an application surface and clutter on a marketing one, so it belongs to the kind rather than to taste.
 - **Hierarchy**: the order a reader takes things in, produced by weight, color, space and position together rather than by size alone.
 - **Ground**: the surface a thing sits on, whether the page behind everything or the fill behind one element. Named apart from "background" because the relationship that matters is what sits against it.
 - **Line height**: the vertical distance from one baseline to the next, set against size rather than fixed across a scale. Avoid "leading", which names the same thing.
@@ -52,9 +54,9 @@ Named compositions, carried so an operator can ask for one by name instead of de
 
 How a draft is staged while unfinished.
 
-- **FPO**: a placeholder held at the true final size and marked as a placeholder, from print production where it abbreviates "for position only". Marking it is the point, since an unmarked stand-in gets read as a decision.
+- **FPO**: a placeholder held at the true final size and marked as one, from the print term "for position only". Marking it is the point, since an unmarked stand-in gets read as a decision.
 - **Greeking**: standing text in for copy that does not exist yet, of which lorem ipsum is the common form. Correct while judging space and wrong once an arm is judged on content.
-- **Grey-box**: drawing every element as a flat neutral block so the layers above the one under judgment are removed from view. Avoid "wireframe", which reads as a deliverable rather than a drafting stage.
+- **Grey-box**: drawing every element as a flat neutral block, removing the layers above the one under judgment from view. Avoid "wireframe", which reads as a deliverable rather than a stage.
 
 ## Terms this vocabulary deliberately does not carry
 

package/claude/skills/document-health/references/axes.md

@@ -11,78 +11,103 @@ The skill body holds the order, the guards, and the report shape. This holds the
 
 ## Length
 
-**Measures:** whether a document, or a passage inside it, has grown past what a reader takes in one pass.
+| Field          | Value                                                                                      |
+| -------------- | ------------------------------------------------------------------------------------------ |
+| Measures       | Whether a document, or a passage inside it, has grown past what a reader takes in one pass |
+| Verbs          | `canon markdown audit --json`, and `canon gov audit --json` for a rule                     |
+| Evidence class | `measured`                                                                                 |
 
-**Verb:** `canon markdown audit --json`.
-
-**Evidence class:** `measured`.
-
-The record carries the checkpoints it read against under `checkpoints` and the per-file weights under `entries`. Read both from the record rather than from a number stated here, since the CLI moves a checkpoint on its own cadence and a copy of one goes stale in place.
-
-Four weights answer this axis, each naming a different shape of overgrowth:
+The record carries the checkpoints it read against under `checkpoints` and the per-file weights under `entries`. Read both from the record rather than from a number stated here, since the CLI moves a checkpoint on its own cadence and a copy goes stale in place.
 
 - `heavyBullets`: a top-level bullet past the character checkpoint, which is a paragraph wearing a dash
 - `heavyParagraphs`: a paragraph past the sentence or character checkpoint
 - `longestRun`, against `longestRunLine`: unbroken rendered lines between headings, which is the depth checkpoint
 - `cadence`, carrying `measured`, `flat`, and `repeating`: sentence-length spread and repeated openers
+- `rules[].findings`: a rule past one of its own six shape limits or carrying an emphasis word, since the density weights above never read a rule file
 
-Weight is a judgment a reader settles rather than a defect, which the verb states for itself and which this axis carries forward. A finding here is an argument for a split or a trim rather than a rule broken.
+### Reading a length finding
 
-**Routes to:** a split of the document, or a move of the overgrown passage to the surface that owns it. Where the project states what a given document may hold, that statement decides whether the passage belongs in it at all, and the finding routes there rather than to a trim.
+Weight is a judgment a reader settles rather than a defect, as the verb states for itself. A finding here argues for a split or a trim rather than naming a broken rule.
 
-**Caveat:** the cadence numbers are drawn from prose a person reads straight through. Terse reference prose sits below that range correctly, so a flat paragraph in a table-heavy or bullet-heavy file is not a finding.
+- **Routes to:** a split of the document, or a move of the overgrown passage to the surface that owns it
+- **A project statement of what a document may hold** decides whether the passage belongs, and the finding routes there rather than to a trim
+- **Caveat:** the cadence numbers are drawn from prose read straight through. Terse reference prose sits below that range correctly, so a flat paragraph in a table or bullet-heavy file is no finding.
 
 ## Placement
 
-**Measures:** whether a document's content sits in the file that owns it, and whether the catalogs pointing at it still resolve.
+| Field          | Value                                                                                                                    |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| Measures       | Whether a document's content sits in the file that owns it, and whether the catalogs pointing at it resolve              |
+| Verbs          | `canon context audit --json` for the structural half, `canon context classify sweep --json` for the per-section verdicts |
+| Evidence class | `measured` for the audit's findings, `classified` for the sweep's verdicts                                               |
 
-**Verbs:** `canon context audit --json` for the structural half, `canon context classify sweep --json` for the per-section verdicts.
+The audit answers required sections, entry length, citation resolution, reference form, catalog tables, provenance, and index drift. Required sections reach context entries.
 
-**Evidence class:** `measured` for the audit's findings, `classified` for the sweep's verdicts.
+- A citation resolving to nothing is a fact and gates
+- Entry length, reference form, table shape, and provenance are judgments under every flag
 
-The audit answers required sections, entry length, citation resolution, reference form, catalog tables, provenance, and index drift. Required sections reach context entries. A citation resolving to nothing is a fact and gates. Entry length, reference form, table shape, and provenance are judgments under every flag.
+### The sweep's verdicts
 
-The sweep classifies each section as keep, replace or rewrite, history, or move. A `move` verdict is the placement finding proper, naming content sitting in the wrong document. Each verdict carries its own confidence, which is why the class is `classified` rather than `measured`, and a low-confidence `move` is a prompt to look rather than an instruction to cut.
+The sweep classifies each section as keep, replace or rewrite, history, or move. A `move` verdict is the placement finding proper, naming content sitting in the wrong document.
 
-**Routes to:** the document the verdict names as the owner. Where the move crosses a tier rather than a file, the project's own content-ownership rules decide the destination.
+- Each verdict carries its own confidence, which is why the class is `classified` rather than `measured`
+- A low-confidence `move` is a prompt to look rather than an instruction to cut
+- **Routes to:** the document the verdict names as the owner. Where the move crosses a tier rather than a file, the project's own content-ownership rules decide the destination.
 
-**Caveat:** both verbs resolve their folders by surface root rather than by a path written into them, so a project whose layout differs from the one they look for resolves nothing. The audit says so, refusing with `reason: "no-folders"` and naming the folders it looked for. Report that refusal as an unread axis. The sweep degrades differently: with the model layer off it answers from its regex layer alone, which is a narrower read rather than a refusal, so say which layer answered.
+### When a verb resolves nothing
 
-## Staleness
+Both verbs resolve their folders by surface root rather than by a path written into them, so a project laid out differently resolves nothing. The two degrade differently.
 
-**Measures:** whether a document still describes the tree it was written about.
+- The audit refuses with `reason: "no-folders"`, naming the folders it looked for. Report that refusal as an unread axis.
+- The sweep with the model layer off answers from its regex layer alone, a narrower read rather than a refusal, so say which layer answered
 
-**Verb:** none.
+## Staleness
 
-**Evidence class:** `read`.
+| Field          | Value                                                            |
+| -------------- | ---------------------------------------------------------------- |
+| Measures       | Whether a document still describes the tree it was written about |
+| Verb           | None                                                             |
+| Evidence class | `read`                                                           |
 
-This is the axis the operator names first and the one nothing measures. A document goes stale by the tree moving under it rather than by anything changing in the document, so no property of the file answers it and a timestamp answers a different question. A file untouched for a year beside code untouched for a year is current, and one edited yesterday against a refactor from this morning is stale.
+This is the axis the operator names first and the one nothing measures. A document goes stale by the tree moving under it, so no property of the file answers it and a timestamp answers a different question.
 
-Read each document against the surfaces it names. Four claim shapes are testable without leaving the project:
+A file untouched for a year beside code untouched for a year is current, and one edited yesterday against a refactor from this morning is stale. Read each document against the surfaces it names, testing four claim shapes without leaving the project.
 
 - A file or folder path the document states, against whether it resolves
 - A command or verb the document names, against whether it exists and carries the flags shown
 - A count the document states over a tree, against the tree
 - A cross-reference to another document, against what that document now says
 
-A claim resting on none of the four is unverifiable from here. Report it as unread rather than as passing, which is the same rule the measured axes take when a verb refuses.
+A claim resting on none of the four is unverifiable from here. Report it as unread rather than as passing, the same rule the measured axes take when a verb refuses.
 
 ### Identity drift in the requirements record
 
-This record states what the project is and why it is built, so it goes stale by the project changing direction as well as by the tree moving. Test these claim shapes beside the four above:
+This record states what the project is and why, so it goes stale by the project changing direction as well as by the tree moving. Test these claim shapes beside the four above, each a `read`.
 
 - A goal nobody pursues, read against the task board and the recent history
 - A non-goal the project has since shipped
 - A constraint the tree contradicts
 
-Each is a `read`. The review point beside them is `measured`: `canon records stale canonical --json` returns the `reviewed` date from its frontmatter and `releasesSince`, the release tags merged into HEAD after that day. A null `releasesSince` means the doc was never reviewed, and `tagged: false` means no release tag exists to count, so a zero there measured nothing. The count is a reminder of how far the project has moved since someone last read the record whole, never a threshold.
+### The review point
 
-**Routes to:** the skill that rewrites a stale claim against an answer, rather than a direct edit from here. A document health run reports and never repairs.
+The review point beside them is `measured`. `canon records stale canonical --json` returns the `reviewed` date from the record's frontmatter and `releasesSince`, the release tags merged into HEAD after that day.
 
-**Caveat:** a reading is the weakest evidence in the report and the most consequential finding in it, which is the tension this axis ships with. Marking the class is what keeps the two facts together in the reader's hands.
+- A null `releasesSince` means the doc was never reviewed
+- `tagged: false` means no release tag exists to count, so a zero there measured nothing
+- The count is a reminder of how far the project has moved since someone last read the record whole, never a threshold
+
+### Routing a staleness finding
+
+A document health run reports and never repairs, so a stale claim routes to the skill that rewrites it against an answer rather than to a direct edit from here.
+
+A reading is the weakest evidence in the report and the most consequential finding in it, which is the tension this axis ships with. Marking the class keeps the two facts together in the reader's hands.
 
 ## Why the three stay apart
 
-The axes are not equally actionable and a report flattening them implies they are. A length finding is a number against a checkpoint, a placement finding is a verdict carrying a confidence, and a staleness finding is a judgment with nothing behind it. Each is worth reporting and each is worth a different response, so the class travels beside the state on every row rather than being stated once in a preamble a reader skims.
+The axes are not equally actionable, and a report flattening them implies they are. Each is worth reporting and each is worth a different response, so the class travels beside the state on every row rather than once in a preamble a reader skims.
+
+- A length finding is a number against a checkpoint
+- A placement finding is a verdict carrying a confidence
+- A staleness finding is a judgment with nothing behind it
 
 Shipping staleness on weaker evidence than the other two is the trade taken deliberately. Cutting it would leave the report answering the two questions that were never the operator's complaint.