docs: responsive + motion next-steps (design doc, roadmap, EN/PT-BR README sync)#17
Open
Atroci wants to merge 1 commit into
Open
docs: responsive + motion next-steps (design doc, roadmap, EN/PT-BR README sync)#17Atroci wants to merge 1 commit into
Atroci wants to merge 1 commit into
Conversation
…ADME sync - docs/next-steps-responsive-and-motion.md: grounded design doc covering (1) responsive/multi-screen capture — the breakpoint-flattening seam (PageExtract.breakpoint populated then discarded in assembleTokens), light/dark dual palette via emulateMedia, per-breakpoint identity, full-height/lazy + DPR; and (2) animation accuracy — CSS keyframe bodies, rAF/MutationObserver sampling for JS-driven (GSAP) motion that bypasses WAAPI, scroll-driven + View Transitions, motion-reference video, a normalized motion-token taxonomy — with honest accuracy ceilings and 5 ordered, independently shippable PRs. - ROADMAP.md: mark shipped 0.3.0 color wins; new Phase 5 (responsive); Phase 4 motion statuses made honest (dormant exported-but-uninvoked detect/capture). - README.md: per-breakpoint/per-theme limitation + next-steps pointer. - README.pt-BR.md: full sync to current 0.3.0 EN (was pre-0.3.0 stale). - CHANGELOG.md: Unreleased section for CI hardening + docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Documentation + planning for the next focus areas, plus housekeeping. No package code change.
Design doc —
docs/next-steps-responsive-and-motion.mdGrounded in the real capture surface (cites the seams), honest about accuracy ceilings.
Part 1 — Responsive / multi-screen. The structural bug:
PageExtract.breakpointis populated then silently discarded whenassembleTokensunions every extract into one flat palette — so mobile/desktop differences dissolve and light/dark is never captured. Highest-value add is a light+dark dual palette viaemulateMedia({ colorScheme }); per-breakpoint identity is cheap to preserve via acom.tokenscout.breakpoints$extensionsarray (just stop flattening).Part 2 — Animation accuracy.
detectPageMotion/captureMotionare exported but never invoked; only ms durations reach DTCG. Motion (formerly Framer Motion) is a hybrid WAAPI+rAF engine; GSAP is rAF-only (so wrappingElement.animatecatches part of Motion, none of GSAP). Concrete upgrades:@keyframesbodies, capture delays +transition: all, rAF/MutationObserver sampling for JS-driven motion, scroll-driven (animation-timeline) + View Transitions, and a Playwright screencast video as ground-truth fallback. Ships as 5 ordered, independent PRs.Roadmap
Marks the shipped 0.3.0 color wins; adds Phase 5 (responsive); makes Phase 4 motion statuses honest (dormant exported-but-uninvoked detection/capture).
READMEs
CHANGELOG
[Unreleased]for the CI publish hardening + docs (no package change).Verification
Adversarial consistency check passed: EN↔PT-BR section parity, no stale
color-1/hex-string$valueclaims, design-doc link resolves, roadmap doesn't mark unshipped work as done.🤖 Generated with Claude Code