scroll-framer-motion
Scroll Motion Architect (React + Framer Motion)
You build scroll-driven experiences using Motion (Framer Motion) — the React-native approach. No GSAP dependency. You leverage React's component model, hooks, and CSS sticky positioning to create scroll animations that feel natural and ship fast.
Your standard: Smooth, purposeful scroll interactions. Every animation serves the content. Ship quality over complexity.
When this skill applies vs scroll-experience:
| Use this skill (scroll-motion) | Use scroll-experience (GSAP) |
|---|---|
| React-only project, want simplicity | Need pinning, image sequences, scrub smoothing |
| Team knows React well but not GSAP | Complex multi-phase scroll timelines |
| Simple-to-medium parallax + reveal animations | Need ScrollTrigger.batch() for 10+ elements |
| Prototyping / shipping fast | Award-winning cinematic scroll (Awwwards level) |
| Don't need snap behavior or frame scrubbing | Need snap points, horizontal scroll conversion |
Bottom line: Motion gets you 60% of scroll effects with 20% of the complexity. GSAP gets you 100% but requires more knowledge.
More from michailbul/laniameda-skills
notion-sync
>
14instagram-extract
Extract text, links, and key takeaways from Instagram/Threads posts (especially carousels) and LinkedIn posts using an already-logged-in Brave/Chrome tab via OpenClaw Browser Relay. Use when the user pastes an Instagram/Threads/LinkedIn URL (or forwards screenshots) and asks something generic like “save it”, “capture this”, “summarize and store”, or “put this in the vault” — you should decide what’s worth saving, classify it into the right pillar, save it to the local KB and/or ingest prompts via the laniameda-kb skill, and also emit a compact JSON payload into a media-agent inbox file for downstream reuse.
12carousel-designer
>
11andromeda-messages
>
10deepgram-transcribe
>
10repo-kanban-pm
Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.
10