Enforce prefers-reduced-motion in gpt-taste and minimalist-ui - #58
Open
rebusz wants to merge 1 commit into
Open
Conversation
Both skills carry motion (gpt-taste: GSAP pin/scrub/stack; minimalist: scroll-entry, staggered reveals, ambient drift) but neither mandated a prefers-reduced-motion fallback. The v2 default taste-skill already requires this (its 6.B + useReducedMotion skeletons), so this brings the two motion-bearing variants to parity. Docs-only; no change for default users. Co-Authored-By: Claude Opus 4.8 <[email protected]>
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
Adds an explicit
prefers-reduced-motion: reducemandate to two motion-bearing skills that currently lack one:Why
The v2 default
taste-skillalready mandates this in §6.B ("Any motion aboveMOTION_INTENSITY > 3MUST honorprefers-reduced-motion… non-negotiable") and its canonical GSAP skeletons useuseReducedMotion(). The GSAP-heavygpt-tasteand the motion-lightminimalist-uiare the two variants most likely to ship animation without the guard, so this brings them to parity. It's an accessibility correctness fix (WCAG 2.3.3) and avoids vestibular-triggering motion for users who opted out.For
gpt-taste, the "static interfaces are forbidden" stance is preserved for the default experience — the rule simply carves out users who explicitly request reduced motion.Scope
Docs-only (SKILL.md prompt text); no behavior change for default users.
Noticed while integrating (happy to send separately, kept out to stay focused): the 1–10 dials could be read from an optional project
.taste.json; the em-dash ban could note it targets rendered UI text; several near-duplicate variants could share a common core.