Repository navigation
chore(design-system): remove the legacy tokens and document MD3 - #371
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
launchpad | 4c8409d | Commit Preview URL Branch Preview URL |
Sep 23 2026, 11:59 AM |
TheMeinerLP
force-pushed
the
feat/md3-content-pages
branch
from
September 23, 2026 11:53
ee39573 to
7712c2b
Compare
- Drop the pre-MD3 colour tokens from @theme: the bg/text/muted/border neutrals, the numeric brand-50…900 ramp, secondary-*, brand-primary and white. The glow's raw brand colours move to :root as --brand-magenta / --brand-cyan, outside @theme, so they mint no utilities. The brand gradients stay for gradient text. - The skip link uses the surface-container-high / on-surface roles and the design system's 3px secondary focus indicator. - Remove brand-scale.spec.ts and the now-empty PENDING_MIGRATION: the governance test fails on any violation outright. Contrast tests drop the muted-token checks; a new test pins that the legacy classes no longer resolve. - Rewrite the tailwind-design skill for the MD3 contract, primitives and governance, fix its references (paths, the Shiki fix, examples), and add a UI primitives section to AGENTS.md. Verified: build, 389 tests, quality gate without regression, and a local Lighthouse accessibility run of 0.98–1.0 on the home, blog, team and community POI pages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ZzvomAnwjAS3et96Avp7s
TheMeinerLP
force-pushed
the
feat/md3-cleanup
branch
from
September 23, 2026 11:57
49ef364 to
4c8409d
Compare
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
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.
Stacked on #370 (
feat/md3-content-pages); part of the OpenSpec changeadopt-md3-design-system. Review the diff againstfeat/md3-content-pages.Changes
chore(design-system): remove the legacy tokens and document MD3
neutrals, the numeric brand-50…900 ramp, secondary-*, brand-primary
and white. The glow's raw brand colours move to :root as
--brand-magenta / --brand-cyan, outside @theme, so they mint no
utilities. The brand gradients stay for gradient text.
the design system's 3px secondary focus indicator.
governance test fails on any violation outright. Contrast tests drop
the muted-token checks; a new test pins that the legacy classes no
longer resolve.
governance, fix its references (paths, the Shiki fix, examples), and
add a UI primitives section to AGENTS.md.
Verified: build, 389 tests, quality gate without regression, and a
local Lighthouse accessibility run of 0.98–1.0 on the home, blog, team
and community POI pages.
Testing
pnpm test: 389 passedpnpm quality: no regression (ESLint 201 errors / 17 warnings, TypeScript 16), baseline unchanged in this branch🤖 Generated with Claude Code
https://claude.ai/code/session_012ZzvomAnwjAS3et96Avp7s