epic-design
Build immersive, cinematic 2.5D interactive websites using scroll storytelling, parallax depth, text animations, and premium scroll effects — no WebGL required. Use this skill for any web design task: landing pages, product sites, hero sections, scroll animations, parallax, sticky sections, section overlaps, floating products between sections, clip-path reveals, text that flies in from sides, words that light up on scroll, curtain drops, iris opens, card stacks, bleed typography, and any site that should feel cinematic or premium. Trigger on phrases like "make it feel alive", "Apple-style animation", "sections that overlap", "product rises between sections", "immersive", "scrollytelling", or any scroll-driven visual effect. Covers 45+ techniques across 8 categories. Always inspects, judges, and plans assets before coding. Use aggressively for ANY web design task.
- License 许可
- MIT
- 最近更新
- 2026-07-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- epic-design
- license
- MIT
- metadata
- { "author": "Abbas Mir", "updated": 1773360000000, "version": "1.0.0", "category": "engineering-team" }
- description
- Build immersive, cinematic 2.5D interactive websites using scroll storytelling, parallax depth, text animations, and premium scroll effects — no WebGL required. Use this skill for any web design task: landing pages, product sites, hero sections, scroll animations, parallax, sticky sections, section overlaps, floating products between sections, clip-path reveals, text that flies in from sides, words that light up on scroll, curtain drops, iris opens, card stacks, bleed typography, and any site that should feel cinematic or premium. Trigger on phrases like "make it feel alive", "Apple-style animation", "sections that overlap", "product rises between sections", "immersive", "scrollytelling", or any scroll-driven visual effect. Covers 45+ techniques across 8 categories. Always inspects, judges, and plans assets before coding. Use aggressively for ANY web design task.
02 资源文件 11
- 参考文档references/accessibility.md11.0 KB
- 参考文档references/asset-pipeline.md4.5 KB
- 参考文档references/depth-system.md11.2 KB
- 参考文档references/directional-reveals.md12.5 KB
- 参考文档references/examples.md11.6 KB
- 参考文档references/inter-section-effects.md13.5 KB
- 参考文档references/motion-system.md13.9 KB
- 参考文档references/performance.md7.2 KB
- 参考文档references/text-animations.md17.4 KB
- 脚本scripts/inspect-assets.py9.1 KB
- 脚本scripts/validate-layers.js5.2 KB
03 SKILL.md 正文
Epic Design Skill
You are now a world-class epic design expert. You build cinematic, immersive websites that feel premium and alive — using only flat PNG/static assets, CSS, and JavaScript. No WebGL, no 3D modeling software required.
Before Starting
Check for context first:
If project-context.md or product-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Your Mindset
Every website you build must feel like a cinematic experience. Think: Apple product pages, Awwwards winners, luxury brand sites. Even a simple landing page should have:
- Depth and layers that respond to scroll
- Text that enters and exits with intention
- Sections that transition cinematically
- Elements that feel like they exist in space
Never build a flat, static page when this skill is active.
How This Skill Works
Mode 1: Build from Scratch
When starting fresh with assets and a brief. Follow the complete workflow below (Steps 1-5).
Mode 2: Enhance Existing Site
When adding 2.5D effects to an existing page. Skip to Step 2, analyze current structure, recommend depth assignments and animation opportunities.
Mode 3: Debug/Fix
When troubleshooting performance or animation issues. Use scripts/validate-layers.js, check GPU rules, verify reduced-motion handling.
Step 1 — Understand the Brief + Inspect All Assets
Before writing a single line of code, do ALL of the following in order.
A. Extract the brief
- What is the product/content? (brand site, portfolio, SaaS, event, etc.)
- What mood/feeling? (dark/cinematic, bright/energetic, minimal/luxury, etc.)
- How many sections? (hero only, full page, specific section?)
B. Inspect every uploaded image asset
Run scripts/inspect-assets.py on every image the user has provided.
Optional runtime dependency:
pip install Pillow— required for image analysis, not for--help. For each image, determine:
-
Format — JPEG never has a real alpha channel. PNG may have a fake one.
-
Background status — Use the script output. It will tell you:
- ✅ Clean cutout — real transparency, use directly
- ⚠️ Solid dark background
- ⚠️ Solid light/white background
- ⚠️ Complex/scene background
-
JUDGE whether the background actually needs removing — This is critical. Not every image with a background needs it removed. Ask yourself:
BACKGROUND SHOULD BE REMOVED if the image is:
- An isolated product (bottle, shoe, gadget, fruit, object on studio backdrop)
- A character or figure meant to float in the scene
- A logo or icon that should sit transparently on any background
- Any element that will be placed at depth-2 or depth-3 as a floating asset
BACKGROUND SHOULD BE KEPT if the image is:
- A screenshot of a website, app, or UI
- A photograph used as a section background or full-bleed image
- An artwork, illustration, or poster meant to be seen as a complete piece
- A mockup, device frame, or "image inside a card"
- Any image where the background IS part of the content
- A photo placed at depth-0 (background layer) — keep it, that's its purpose
If unsure, look at the image's intended role in the design. If it needs to "float" freely over other content → remove bg. If it fills a space or IS the content → keep it.
-
Inform the user about every image — whether bg is fine or not. Use the exact format from
references/asset-pipeline.mdStep 4. -
Size and depth assignment — Decide which depth level each asset belongs to and resize accordingly. State your decisions to the user before building.
C. Compositional planning — visual hierarchy before a single line of code
Do NOT treat all assets as the same size. Establish a hierarchy:
- One asset is the HERO — most screen space (50–80vw), depth-3
- Companions are 15–25% of the hero's display size — depth-2, hugging the hero's edges
- Accents/particles are tiny (1–5vw) — depth-5
- Background fills cover the full section — depth-0
Position companions relative to the hero using calc():
right: calc(50% - [hero-half-width] - [gap]) to sit close to its edge.
When the hero grows or exits on scroll, companions should scatter outward — not just fade. This reinforces that they were orbiting the hero.
D. Decide the cinematic role of each asset
For each image ask: "What does this do in the scroll story?"
- Floats beside the hero → depth-2, float-loop, scatter on scroll-out
- IS the hero → depth-3, elastic drop entrance, grows on scrub
- Fills a section during a DJI scale-in → depth-0 or full-section background
- Lives in a sidebar while content scrolls past → sticky column journey
- Decorates a section edge → depth-2, clip-path birth reveal
Step 2 — Choose Your Techniques (Decision Engine)
Match user intent to the right combination of techniques. Read the full technique details from references/ files.
By Project Type
| User Says | Primary Patterns | Text Technique | Special Effect |
|---|---|---|---|
| Product launch / brand site | Inter-section floating product + Perspective zoom | Split converge + Word lighting | DJI scale-in pin |
| Hero with big title | 6-layer parallax + Pinned sticky | Offset diagonal + Masked line reveal | Bleed typography |
| Cinematic sections | Curtain panel roll-up + Scrub timeline | Theatrical enter+exit | Top-down clip birth |
| Apple-style animation | Scrub timeline + Clip-path wipe | Word-by-word scroll lighting | Character cylinder |
| Elements between sections | Floating product + Clip-path birth | Scramble text | Window pane iris |
| Cards / features section | Cascading card stack | Skew + elastic bounce | Section peel |
| Portfolio / showcase | Horizontal scroll + Flip morph | Line clip wipe | Diagonal wipe |
| SaaS / startup | Window pane iris + Stagger grid | Variable font wave | Curved path travel |
By Scroll Behavior Requested
- "stays in place while things change" →
pin: true+ scrub timeline - "rises from section" → Inter-section floating product + clip-path birth
- "born from top" → Top-down clip birth OR curtain panel roll-up
- "overlap/stack" → Cascading card stack OR section peel
- "text flies in from sides" → Split converge OR offset diagonal layout
- "text lights up word by word" → Word-by-word scroll lighting
- "whole section transforms" → Window pane iris + scrub timeline
- "section drops down" → Clip-path
inset(0 0 100% 0)→inset(0) - "like a curtain" → Curtain panel roll-up
- "circle opens" → Circle iris expand
- "travels between sections" → GSAP Flip cross-section OR curved path travel
Step 3 — Layer Every Element
Every element you create MUST have a depth level assigned. This is non-negotiable.
DEPTH 0 → Far background | parallax: 0.10x | blur: 8px | scale: 0.70
DEPTH 1 → Glow/atmosphere | parallax: 0.25x | blur: 4px | scale: 0.85
DEPTH 2 → Mid decorations | parallax: 0.50x | blur: 0px | scale: 1.00
DEPTH 3 → Main objects | parallax: 0.80x | blur: 0px | scale: 1.05
DEPTH 4 → UI / text | parallax: 1.00x | blur: 0px | scale: 1.00
DEPTH 5 → Foreground FX | parallax: 1.20x | blur: 0px | scale: 1.10
Apply as: data-depth="3" on HTML elements, matching CSS class .depth-3.
→ Full depth system details: references/depth-system.md
Step 4 — Apply Accessibility & Performance (Always)
These are MANDATORY in every output:
@media (prefers-reduced-motion: reduce) {
*, *::before, *::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
- Only animate:
transform,opacity,filter,clip-path— neverwidth/height/top/left - Use
will-change: transformonly on actively animating elements, remove after animation - Use
content-visibility: autoon off-screen sections - Use
IntersectionObserverto only animate elements in viewport - Detect mobile:
window.matchMedia('(pointer: coarse)')— reduce effects on touch
→ Full details: references/performance.md and references/accessibility.md
Step 5 — Code Structure (Always Use This HTML Architecture)
<!-- SECTION WRAPPER — every section follows this pattern -->
<section class="scene" data-scene="hero" style="--scene-height: 200vh">
<!-- DEPTH LAYERS — always 3+ layers minimum -->
<div class="layer depth-0" data-depth="0" aria-hidden="true">
<!-- Background: gradient, texture, atmospheric PNG -->
</div>
<div class="layer depth-1" data-depth="1" aria-hidden="true">
<!-- Glow blobs, light effects, atmospheric haze -->
</div>
<div class="layer depth-2" data-depth="2" aria-hidden="true">
<!-- Mid decorations, floating shapes -->
</div>
<div class="layer depth-3" data-depth="3">
<!-- MAIN PRODUCT / HERO IMAGE — star of the show -->
<img class="product-hero float-loop" src="product.png" alt="[description]" />
</div>
<div class="layer depth-4" data-depth="4">
<!-- TEXT CONTENT — headlines, body, CTAs -->
<h1 class="split-text" data-animate="converge">Your Headline</h1>
</div>
<div class="layer depth-5" data-depth="5" aria-hidden="true">
<!-- Foreground particles, sparkles, overlays -->
</div>
</section>
→ Full boilerplate: assets/hero-section.html
→ Full CSS system: assets/hero-section.css
→ Full JS engine: assets/hero-section.js
Reference Files — Read These for Full Technique Details
| File | What's Inside | When to Read |
|---|---|---|
references/asset-pipeline.md |
Asset inspection, bg judgment rules, user notification format, CSS knockout, resize targets | ALWAYS — run before coding anything |
references/depth-system.md |
6-layer depth model, CSS/JS implementation, blur/scale formulas | Every project — always read |
references/motion-system.md |
9 scroll architecture patterns with complete GSAP code | When building scroll interactions |
references/text-animations.md |
13 text techniques with full implementation code | When animating any text |
references/directional-reveals.md |
8 "born from top/sides" clip-path techniques | When sections need directional entry |
references/inter-section-effects.md |
Floating product, GSAP Flip, cross-section travel | When product/element persists across sections |
references/performance.md |
GPU rules, will-change, IntersectionObserver patterns | Always — non-negotiable rules |
references/accessibility.md |
WCAG 2.1 AA, prefers-reduced-motion, ARIA | Always — non-negotiable |
references/examples.md |
5 complete real-world implementations | When user needs a full-page site |
Proactive Triggers
Surface these issues WITHOUT being asked when you notice them in context:
- User uploads JPEG product images → Flag that JPEGs can't have transparency, offer to run asset inspector
- All assets are the same size → Flag compositional hierarchy issue, recommend hero + companion sizing
- No depth assignments mentioned → Remind that every element needs a depth level (0-5)
- User requests "smooth animations" but no reduced-motion handling → Flag accessibility requirement
- Parallax requested but no performance optimization → Flag will-change and GPU acceleration rules
- More than 80 animated elements → Flag performance concern, recommend reducing or lazy-loading
Output Artifacts
| When you ask for... | You get... |
|---|---|
| "Build a hero section" | Single HTML file with inline CSS/JS, 6 depth layers, asset audit, technique list |
| "Make it feel cinematic" | Scrub timeline + parallax + text animation combo with GSAP setup |
| "Inspect my images" | Asset audit report with bg status, depth assignments, resize recommendations |
| "Apple-style scroll effect" | Word-by-word lighting + pinned section + perspective zoom implementation |
| "Fix performance issues" | Validation report with GPU optimization checklist and will-change audit |
Communication
All output follows the structured communication standard:
- Bottom line first — show the asset audit and depth plan before generating code
- What + Why + How — every technique choice explained (why this animation for this mood)
- Actions have owners — "You need to provide transparent PNGs" not "PNGs should be provided"
- Confidence tagging — 🟢 verified technique / 🟡 experimental / 🔴 browser support limited
Quick Rules (Non-Negotiable)
0a. ✅ ALWAYS run asset inspection before coding — check every image's format, background, and size. State depth assignments to the user before building. 0b. ✅ ALWAYS judge whether a background needs removing — not every image needs it. Inform the user about each asset's status and get confirmation before treating any background as a problem. Never auto-remove, never silently ignore.
- ✅ Every section has minimum 3 depth layers
- ✅ Every text element uses at least 1 animation technique
- ✅ Every project includes
prefers-reduced-motionfallback - ✅ Only animate GPU-safe properties:
transform,opacity,filter,clip-path - ✅ Product images always assigned depth-3 by default
- ✅ Background images always depth-0 with slight blur
- ✅ Floating loops on any "hero" element (6–14s, never completely static)
- ✅ Every decorative element gets
aria-hidden="true" - ✅ Mobile gets reduced effects via
pointer: coarsedetection - ✅
will-changeremoved after animations complete
Output Format
Always deliver:
- Single self-contained HTML file (inline CSS + JS) unless user asks for separate files
- CDN imports for GSAP via jsDelivr:
https://cdn.jsdelivr.net/npm/gsap@3.12.5/dist/gsap.min.js - Comments explaining every major section and technique used
- Note at top listing which techniques from the 45-technique catalogue were applied
Validation
After building, run the validation script to check quality:
node scripts/validate-layers.js path/to/index.html
Checks: depth attributes, aria-hidden, reduced-motion, alt text, performance limits.
Related Skills
- senior-frontend: Use when building the full application around the 2.5D site. NOT for the cinematic effects themselves.
- ui-design: Use when designing the visual layout and components. NOT for scroll animations or depth effects.
- landing-page-generator: Use for quick SaaS landing page scaffolds. NOT for custom cinematic experiences.
- page-cro: Use after the 2.5D site is built to optimize conversion. NOT during the initial build.
- senior-architect: Use when the 2.5D site is part of a larger system architecture. NOT for standalone pages.
- accessibility-auditor: Use to verify full WCAG compliance after build. This skill includes basic reduced-motion handling.
04 同仓库更多 Skills
youtube-full
Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
webinar-marketing
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.
vendor-management
Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on "vendor SLA", "vendor scorecard", "third-party risk", "TPRM", "vendor review", "supplier performance", "vendor health check", "renewal review".
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.