Skip to content
Back to search

web-motion-library

SkillWorks with Claude CodeGitHub

Use when planning, brainstorming or building websites with strong animation, scroll effects, 3D/WebGL, micro-interactions or "wow" motion; when asked for many animation ideas (e.g. "give me 50/100 ideas"), a hero concept, a scroll story, or which effects suit an audience; when choosing GSAP, Lenis, Three.js, shaders, Lottie/Rive or View Transitions; or when motion stutters, jumps or lags.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zeiad-e--web-motion-library/badge.svg)](/listings/zeiad-e--web-motion-library)

HTML

<a href="/listings/zeiad-e--web-motion-library"><img src="/api/listings/zeiad-e--web-motion-library/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Clone into your personal skills folder:

git clone https://github.com/zeiad-E/web-motion-library ~/.claude/skills/web-motion-library

Any new Claude Code session will then use it when you ask for animation ideas or build motion-heavy pages.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 57 lines
  1. ---
  2. name: web-motion-library
  3. description: Use when planning, brainstorming or building websites with strong animation, scroll effects, 3D/WebGL, micro-interactions or "wow" motion; when asked for many animation ideas (e.g. "give me 50/100 ideas"), a hero concept, a scroll story, or which effects suit an audience; when choosing GSAP, Lenis, Three.js, shaders, Lottie/Rive or View Transitions; or when motion stutters, jumps or lags.
  4. ---
  5. # Web Motion Library
  6. A reference library of web motion: ~100 effects with what they do to an audience, how to build them, what they cost, plus an idea engine, choreography rules and field-tested recipes.
  7. **Live reference implementations** (plain HTML/CSS/JS, 30 effects running plus two full home pages) are in the BrightSmile repo, folder `frontend-drafts/` (github.com/zeiad-E/brightsmile-clinic-assistant; locally `D:\Work\Agent\frontend-drafts`). Open them when you need working code for an effect in the catalog.
  8. **Core principle:** strong motion work is *one concept* told through *a few effects that hand off to each other*, with *one signature moment*, built so it stays smooth on a mid-range phone. A list of nice effects is not a design.
  9. ## Files
  10. | File | Use it for |
  11. |---|---|
  12. | `catalog.md` | The effect library: 12 families, each effect with what the visitor sees, how it's built, cost, audience impact, pitfalls |
  13. | `audience.md` | What motion does to people; fit by industry and audience; when motion hurts |
  14. | `ideas.md` | The idea engine: how to produce 20–100+ strong, varied ideas, scoring, output format |
  15. | `choreography.md` | Turning effects into one page: thread object, handoffs, pacing, section edges, hero entrance |
  16. | `tools.md` | Stack choices (GSAP, Lenis, Three.js, raw WebGL, CSS scroll timelines, View Transitions, Lottie/Rive, AI asset pipeline) and rough KB/ms budgets |
  17. | `recipes.md` | Working code patterns (pinning, smooth scroll, letter reveal, image sequence, portal, X-ray, goo, shaders, assembling object, RTL, path morph) and the performance lessons that made them smooth |
  18. ## Workflow
  19. 1. **Brief first.** Pin down: audience (who, how anxious/excited, phone share, language/RTL), goal (trust, sales, booking, delight), brand mood, budget. Read `audience.md` for the fit.
  20. 2. **Concept before effects.** Write one sentence the whole site enacts ("the visitor boots up an agent", "you step inside the clinic", "the product assembles itself"). Pick a *thread*: an object, line or colour that travels through the page.
  21. 3. **Generate wide** with `ideas.md` (trigger × subject × transformation × narrative), across *all* catalog families, not just reveal/fade.
  22. 4. **Score and cut**: impact vs effort vs audience fit. Keep 1 signature moment, 3–6 supporting effects, micro-interactions everywhere.
  23. 5. **Choreograph** with `choreography.md`: order, handoffs, pacing (loud → calm → loud), section edges.
  24. 6. **Build** with `tools.md` + `recipes.md`; prototype hard parts in plain HTML first.
  25. 7. **Verify** on a mid-range Android, with reduced motion on, keyboard only, and in RTL if relevant.
  26. ## Non-negotiables
  27. | Rule | Why |
  28. |---|---|
  29. | One signature 3D/cinematic moment per page | Stacked spectacles cancel each other and kill phones |
  30. | Animate only `transform`, `opacity`, `filter` (sparingly), canvas/WebGL | Layout properties stutter |
  31. | Never read layout (`getBoundingClientRect`) every frame; measure on resize | Forced reflow = jank |
  32. | Drive sequences step by step (await each step), never by long fixed CSS delays | After any main-thread stall, delayed transitions all fire at once |
  33. | Heavy work (mesh building, image decoding, shader compile) before or between animations, time-sliced | Otherwise the first seconds jump |
  34. | No `backdrop-filter` above an animated canvas | The browser re-blurs every frame |
  35. | Full-screen canvas: cap device pixel ratio at 1.5–2 | 4K-wide canvases melt laptops |
  36. | `prefers-reduced-motion`: still hero, simple fades, no smooth-scroll hijack | Accessibility and vestibular safety |
  37. | All text is real HTML (never baked into frames/textures) | Readable, translatable, searchable |
  38. | Every hover-only reveal also works with keyboard focus and touch | Most visitors are on phones |
  39. | Arabic/RTL: mirror directions (slides, marquees, progress) | Motion direction is part of reading direction |
  40. ## Common mistakes
  41. - Giving a list of safe UI niceties (accordion, skeleton, fade-up) and calling it a motion concept. Those are baseline polish; also deliver the concept and signature moment.
  42. - Ideas without cost or audience impact: every idea needs *why it works for this audience* and *what it costs*.
  43. - Ten wow effects on one page. Pick one; let the rest serve it.
  44. - Smooth soft gradients between every section when the brand wants crisp structure. Decide edges deliberately (`choreography.md`).
  45. - Trusting a hidden/background browser tab for timing: rAF pauses there. Test visible, or with a timer-driven rAF override for automation only.
README.md · README · 20 lines
  1. # web-motion-library
  2. A Claude Code skill: a reference library for websites with strong motion.
  3. - **catalog.md**: ~100 web effects in 12 families (scroll, 3D/WebGL, media, typography, cursor, navigation, entrances, aesthetic, micro-interactions, data, sound, AI assets), each with what the visitor sees, how it's built, cost, audience impact and pitfalls
  4. - **audience.md**: what motion does to people, fit by industry, when motion hurts, Arabic/RTL
  5. - **ideas.md**: an idea engine for producing 20–100+ varied, strong ideas, with scoring and an output format
  6. - **choreography.md**: turning many effects into one experience (thread object, handoffs, pacing, hero entrance)
  7. - **tools.md**: stack choices and rough KB/ms budgets
  8. - **recipes.md**: working code patterns and performance lessons
  9. ## Install
  10. Clone into your personal skills folder:
  11. ```bash
  12. git clone https://github.com/zeiad-E/web-motion-library ~/.claude/skills/web-motion-library
  13. ```
  14. Any new Claude Code session will then use it when you ask for animation ideas or build motion-heavy pages.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.