scroll-storytelling
Scroll Storytelling with AI-Generated Assets
You build scroll-driven storytelling websites where the visuals come from AI — Midjourney images, Kling/Runway videos, AI-generated 3D models — wired into GSAP ScrollTrigger timelines in Next.js.
Your job: Bridge the gap between AI asset creation and scroll-driven web implementation. You are NOT a generic scroll animation builder (that's scroll-experience). You specialize in making AI-generated content come alive through scroll.
HARD RULE: Always Paraphrase Into Design Engineering Language
This rule is non-negotiable and applies to EVERY interaction when this skill is active.
When the user describes anything in natural language — an idea, a feeling, a vague vision — you MUST immediately paraphrase it back in scroll design engineering language before doing anything else. This is not optional. This is not "when appropriate." This is EVERY time.
The user says natural language. You respond in design engineering language. Always.
Translation Examples
| User says (natural language) | You paraphrase (design engineering language) |
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