Andreas Reinhold / reiniandClaude Opus 5
24eb811f34
2.0.0 took Tailwind out of the stack, but the texts Boost copies into every application still taught its utilities: the core guideline said "built on Tailwind CSS", the always-on material-3 guideline wrote every rule as `bg-primary`, `type-*`, `rounded-corner-*`, `state-layer` and `medium:`, and both skills' tables and examples did the same. None of those classes exists in 2.0's stylesheets, so an agent following the guideline wrote markup that compiled to nothing. Found moving ReStride onto 2.0: its CLAUDE.md, and SealShare's, carry these texts. The guidelines and skills now teach what 2.0 has: component and layout component props (`gap="space200"`, `hide-from="medium"`), the `md-type-*`, `md-ink-*` and interaction classes, and `--md-sys-*` tokens in the application's own CSS, with breakpoints as range media queries. UPGRADE.md §1, §2 and §4 describe the finished move instead of the in-between state, and header comments that pointed at the removed tokens/utilities.css and tailwind.css, or called a component "still Tailwind", say what is true now. BoostVocabularyTest runs DesignGuard over the code in every shipped guideline and skill (fenced Blade and CSS, and each inline class list), so a text that teaches a class the stylesheets do not define fails the suite; it finds 268 violations in the texts as 2.0.0 shipped them. The guard's own table of what it reports is exempt. BoostResourcesTest now asks the design skill for each breakpoint's prop value and media query instead of the removed `medium:` variants. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
29 lines
1.1 KiB
JavaScript
29 lines
1.1 KiB
JavaScript
/**
|
|
* M3's window size classes, for scripts that ask the viewport width.
|
|
*
|
|
* The same four numbers as the stylesheets' range media queries (`@media (width >= 840px)`) and the
|
|
* layout components' `hide-below`, `hide-from` and `stack-below` props; compact is everything below
|
|
* `medium`. `from('expanded')` and `upTo('medium')` return MediaQueryLists on that same range
|
|
* syntax, so a script and a stylesheet never disagree at the boundary pixel.
|
|
*/
|
|
export const breakpoints = Object.freeze({
|
|
medium: 600,
|
|
expanded: 840,
|
|
large: 1200,
|
|
'extra-large': 1600,
|
|
})
|
|
|
|
const width = (name) => {
|
|
if (!(name in breakpoints)) {
|
|
throw new Error(`Unknown breakpoint "${name}". Use one of: ${Object.keys(breakpoints).join(', ')}.`)
|
|
}
|
|
|
|
return breakpoints[name]
|
|
}
|
|
|
|
/** Matches at and above the class's lower edge, like `medium:`. */
|
|
export const from = (name) => window.matchMedia(`(width >= ${width(name)}px)`)
|
|
|
|
/** Matches below the class's lower edge, like `max-medium:`. */
|
|
export const upTo = (name) => window.matchMedia(`(width < ${width(name)}px)`)
|