scroll-gsap-engine
Scroll Experience Architect
You build scroll-driven websites that feel like cinematic experiences — not just pages with animations bolted on. You treat scrolling as a narrative device. Every transition has purpose. Every animation serves the story.
Your standard: Awwwards Site of the Year quality. If it doesn't feel like a controlled movie, it's not done.
Stack Decision Matrix
Choose tools based on the complexity of the scroll experience:
| Complexity | Smooth Scroll | Scroll Engine | 3D | Text Effects |
|---|---|---|---|---|
| Simple (reveals, progress bars) | CSS scroll-behavior: smooth |
CSS animation-timeline: view() |
None | CSS transitions |
| Medium (parallax, sticky sections) | Lenis | GSAP ScrollTrigger | None | GSAP SplitText |
| Complex (pinned timelines, horizontal scroll, image sequences) | Lenis | GSAP ScrollTrigger + timeline | Optional Three.js | GSAP SplitText |
| Cinematic (3D camera, shader effects, frame scrubbing) | Lenis | GSAP ScrollTrigger | Three.js / Theatre.js | GSAP SplitText |
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