fix: graceful degradation for motion-heavy sites (closes #39)#56
Open
YAMRAJ13y wants to merge 1 commit into
Open
fix: graceful degradation for motion-heavy sites (closes #39)#56YAMRAJ13y wants to merge 1 commit into
YAMRAJ13y wants to merge 1 commit into
Conversation
…loses JCodesMore#39) When a site is packed with dynamic effects (WebGL/canvas scenes, big GSAP timelines, lots of staggered scroll animations), the skill currently tries to faithfully rebuild every one of them in a single pass. That's where it falls apart - the build breaks and you're left with nothing usable, which is what JCodesMore#39 is describing. This reworks the approach so motion sits on top of a correct static clone instead of being a prerequisite for it: - Get a pixel-accurate static skeleton compiling first (zero animation), then add motion back in priority order, verifying the build after each step. For effects that aren't realistically worth rebuilding by hand (shaders, complex timelines, Lottie), drop in a looping muted video or a screenshot and move on. - A "motion complexity triage" recon step that detects the animation stack (Framer Motion, GSAP/ScrollTrigger, Lenis, Three.js/WebGL/canvas, Lottie, particles, video backgrounds) and tiers the page light/moderate/heavy so the strategy matches the workload. - A couple of "what not to do" notes and a motion-tier line in the final report so anything deferred is surfaced, not silently dropped. Edited the source skill and regenerated the 9 platform copies with scripts/sync-skills.mjs. Docs/prompt only - no code touched.
YAMRAJ13y
force-pushed
the
fix/issue-39-motion-heavy-graceful-degradation
branch
from
June 30, 2026 04:51
fd23ce6 to
3f0f87b
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
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.
Takes a crack at #39 — sites with a lot of dynamic effects currently tend to fail outright when you try to clone them.
The root of it is that the clone-website skill treats every animation as something it has to reproduce exactly. On a heavy site (WebGL, chained GSAP, dozens of staggered reveals) the agent tries to rebuild all of it in one pass, the build breaks, and you end up with nothing usable — which lines up with what the issue describes.
This makes motion a layer on top of a working static clone instead of a hard requirement:
I edited the source skill and regenerated the platform copies with the existing sync script, so this is docs/prompt only — lint/typecheck/build aren't affected.
Closes #39.