Extended colour palette, EE neutral scale, semantic layer#13
Merged
Conversation
…mantic layer Lands WS0-WS3 of the June 2026 colours lockdown: 10 extended-palette scales with corrected monotonic OKLCH ramps (anchored at measured lightness, not forced to 500), an EE neutral scale (Byte White -> Dark Data) with named aliases, a cross-cutting semantic/RAG layer (error/warning/success/info/link/ interaction-state), and the Tier 3 data-viz categorical order. destructive now resolves to Runtime Red. generate-tokens.mjs regenerates colours.md from the new tokens; reference docs (accessibility, web-product, web-marketing, charts-data, imagery, slides) updated to match, with diagrams/slides content marked provisional pending the Ben Wilks session. Both tokens:check and reference:check are green. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Updates create-web-app/review-web-app (accessible-blue links vs EE-Blue buttons, neutral scale for surfaces, status colours via semantic tokens), create-presentation/review-presentation (Dark Data deck model, single Lime/Orange pull-out, one-palette in-slide charts), and create-imagery (new diagram job, one-palette-at-a-time + CVD redundancy for infographics/ diagrams) to apply the tokens/reference added in the prior commit. kuat-review inherits these via its existing delegation to the activity skills, so it needed no direct edit. Rebuilt plugins/ and skills/dist/ from the updated sources; tokens:check, reference:check, and verify:plugins all green. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Records the June 2026 colours lockdown outcomes (extended palette + neutral scale + semantic layer, destructive -> Runtime Red, accessible-blue WIP status, Server Slate kept distinct from the neutral scale) so the rationale survives and isn't relitigated. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Fill in the web-product/emails.md and web-marketing/emails.md stubs with principles, design/content guidance, and common scenario patterns, synthesised from EE brand/content/accessibility foundations and external best-practice research (Postmark, Klaviyo, NN/g, Email on Acid). Kept technology-agnostic. Passes npm run reference:check (passive test, link integrity, structure, token drift).
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands WS0–WS4 of the June 2026 colours lockdown (from the "Nick Orme / Ed Ford" meeting — see
extended-palette-review.md) into the token source of truth and its consumers.colors.tokens.json) — 10 extended-palette scales (Index Indigo, Packet Plum, Runtime Red, Uptime Green, Server Slate, Logic Lime, Edge Blue, Signal Yellow, Cursor Coral, Patch Peach), each a corrected monotonic 50–950 ramp anchored at its measured lightness step (not forced to 500); an EE neutral scale (neutral-50…950, Byte White → Dark Data) with named aliases including the new Overcast (neutral-600); a cross-cutting semantic/RAG layer (error/warning/success/info/link/interaction-state+ on-dark variants); the Tier 3categorical-1…8data-viz sequence.destructivenow resolves to Runtime Red. Every new token carriesscopes/codeSyntax.generate-tokens.mjsextended to emit the new sections;colours.mdregenerated.colour-usage.md(tier model, adjacency rules, accessible-blue WIP flag) andcolour-modes.md(shadcn light/dark mapping); updates toaccessibility.md,charts-data/README.md,web-marketing/website.md, plus provisional additions for diagrams and slides.create-web-app/review-web-app,create-presentation/review-presentation,create-imageryupdated to apply the new rules (link-vs-button colour, status colours, one-palette charts, Dark Data deck model, CVD-safe diagrams).Accessible link blue (
#0080be) is intentionally WIP — flagged throughout, pending validation in real link contexts.Companion PR
Downstream half (kuat-core
variables.css,token-contract.json, versioning) is EqualExperts/kuat-mono#29 — per the contribution model these should land in the same release so the drift gate and consumers don't see the two artifacts out of sync.Test plan
npm run tokens:generate&&npm run tokens:check— greennpm run reference:check— green (passive test, link integrity, structure, token drift)npm run build:plugins&&npm run verify:plugins— greencontribute/proposing-a-token-change.md)#design-systemnote once merged🤖 Generated with Claude Code