Communitygithub.com

MengTo/Skills

Use when creating or refining WebGL-heavy landing pages and you need to steer toward a specific visual outcome (premium, technical, playful, cinematic) while balancing conversion clarity, performance, and implementation complexity.

What is Skills?

Skills is a Codex agent skill that use when creating or refining WebGL-heavy landing pages and you need to steer toward a specific visual outcome (premium, technical, playful, cinematic) while balancing conversion clarity, performance, and implementation complexity.

Works with~Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/MengTo/Skills/tree/HEAD/agent-skills/web-design/webgl-landing-steering

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

WebGL Landing Steering Skill

Use this skill to steer outcomes

Map landing-page goal to WebGL direction before writing code.

1) Define the page intent

Identify the primary conversion and brand signal:

  • Premium / luxury / minimal confidence
  • Technical / infrastructure / data authority
  • Playful / consumer / social energy
  • Cinematic / launch / storytelling impact

Also capture:

  • Device mix (desktop-heavy vs mobile-heavy)
  • Motion tolerance (prefers-reduced-motion policy)
  • Production constraints (deadline, team skill, maintenance budget)

2) Choose the WebGL lane

Pick one dominant lane; avoid mixing 3-4 heavy effects in the hero.

Lane A: Subtle depth field (high conversion safety)

Use for: SaaS, productivity, B2B tools where readability wins.

  • Visuals: soft gradient meshes, slow parallax planes, light bloom
  • Motion: low amplitude, always secondary to copy
  • Stack: Three.js plane shaders or lightweight shader canvas
  • Rule: hero text contrast and CTA prominence first

Lane B: Data/particle intelligence (technical credibility)

Use for: AI, infra, analytics, developer products.

  • Visuals: particle flows, node networks, vector fields, wireframes
  • Motion: purposeful directional flow toward CTA area
  • Stack: Three.js + custom shader/points, optionally GPGPU for dense fields
  • Rule: communicate "system behavior," not random sparkles

Lane C: Object-centric 3D product moment (feature clarity)

Use for: hardware, apps with strong product visuals, launches.

  • Visuals: central GLTF model, controlled camera orbit, material highlights
  • Motion: interaction-driven or timeline-based reveal
  • Stack: Three.js + GLTF/DRACO/KTX2 pipeline
  • Rule: one hero object, short loop, fast first meaningful paint fallback

Lane D: Immersive cinematic scene (brand campaign)

Use for: campaign pages where wow factor is the main KPI.

  • Visuals: volumetrics, heavy postprocessing, dense scene composition
  • Motion: choreographed sequence with scroll chapters
  • Stack: Three.js + postprocessing + optional GSAP ScrollTrigger
  • Rule: provide a static/mobile fallback and strict performance gates

3) Steering matrix by landing page type

  • Waitlist / pre-launch: Lane A or B. Keep copy legible and quick to load.
  • Product feature page: Lane A or C. Demonstrate product truth, not abstract noise.
  • Pricing / high-intent page: Mostly Lane A. Keep WebGL decorative only.
  • Enterprise trust page: Lane B with restrained palette and low noise.
  • Consumer app growth page: Lane B with playful palette, but cap CPU/GPU load.
  • Campaign microsite: Lane C or D with explicit fallback for lower-end devices.

4) Quality gates before shipping

Pass these gates before adding more visual complexity:

  1. Message gate:
  • Hero headline + CTA readable in under 3 seconds.
  • WebGL never blocks understanding of offer.
  1. Performance gate:
  • Cap pixel ratio: Math.min(devicePixelRatio, 1.5-2).
  • Target stable frame time on common mobile devices.
  • Lazy-load heavy assets; show immediate non-WebGL poster/fallback.
  1. Accessibility gate:
  • Respect prefers-reduced-motion (still frame or low-motion mode).
  • Maintain color contrast over animated backgrounds.
  1. Reliability gate:
  • Handle context loss and resize.
  • Dispose geometries/materials/textures in SPA route changes.

5) Implementation strategy by risk

  • Low risk (fastest): CSS + canvas illusion, minimal shaders
  • Medium risk: Three.js scene with 1-2 meshes, lightweight post FX
  • High risk: multi-pass shaders, dense particles, advanced postprocessing

Default to low/medium risk for conversion pages unless user explicitly asks for campaign-grade immersion.

6) Prompting template for Codex-style execution

Use this prompt pattern when asked to build a WebGL landing hero:

"Build a [lane] WebGL hero for a [page type] with [brand adjectives]. Primary goal: [conversion]. Constraints: [device mix], [performance budget], [reduced motion policy]. Implement fallback first, then enhance with WebGL. Keep hero copy clarity as priority over visual complexity."

7) Common failure patterns and corrections

  • Failure: "Looks cool but conversion dropped."
    • Fix: reduce motion amplitude, darken/soften background, raise CTA contrast.
  • Failure: "Mobile stutters."
    • Fix: reduce particle count, lower DPR cap, remove expensive postprocessing.
  • Failure: "Visual style feels generic."
    • Fix: pick one signature motif aligned to brand (grid, wave, orbit, shards).
  • Failure: "Team cannot maintain shader complexity."
    • Fix: simplify to modular Three.js scene with documented parameters.

Output format when applying this skill

Return:

  1. Recommended lane and why
  2. Visual spec (palette, motion behavior, composition)
  3. Technical stack and complexity tier
  4. Fallback behavior
  5. Performance + accessibility checklist
  6. Build order (MVP first, enhancement second)

Individual skills in this repo

This repo contains 9 individual skills — each has its own dedicated page.

MengTo/Skills

Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to record or re-record browser actions, show cursor clicks and zooms, make Dribbble/UI inspiration or product demo recordings, or asks whether Codex, Playwright, or an MCP can produce a natural browser demo video.

MengTo/Skills

Generate ElevenLabs text-to-speech audio from scripts or inline text using local voice profiles. Use when the user asks for ElevenLabs, text-to-speech, TTS, narration, voiceover, speech audio, or voice generation; load voice names, voice ids, emails, owners, and account-specific defaults only from local config outside the skill.

MengTo/Skills

Profile, audit, and optimize frontend page performance with emphasis on animation work, memory-leak risks, long-session slowdowns, CSS animations, canvas/WebGL requestAnimationFrame loops, marquees, skeletons, GSAP/Three/Matter effects, timers, listeners, and observers. Use when the user asks to make animations performant, pause offscreen animations, look for memory leaks, profile pages that slow the computer over time, fix janky scrolling, reduce CPU/GPU use, or repeat the "only play in view" optimization on React/Vite/Next/frontend pages using Codex Browser.

MengTo/Skills

Turn a reference video into a super detailed recreation or inspiration prompt. Use when the user provides, mentions, uploads, links, or points to a video and asks to analyze the design, UI, animations, transitions, scroll interactions, typography, colors, assets, WebGL/Three.js, storytelling, section-by-section behavior, or to create a prompt/article that recreates the page, app, interaction, or motion system.

MengTo/Skills

Create an on-scroll animation trigger using IntersectionObserver with Tailwind-friendly animation classes and keyframes. Use when asked for scroll-reveal, animate-on-scroll, or sequencing element animations when they enter the viewport.

MengTo/Skills

Use when designing or implementing product-grade web motion like Stripe, Linear, Apple, and Vercel. Covers motion principles, easing/duration defaults, choreography patterns, scroll/hover interactions, performance, accessibility (reduced motion), and implementation guidance.

MengTo/Skills

Create premium cinematic web motion systems with GSAP, ScrollTrigger, and Lenis. Use for luxury editorial websites, creative studio portfolios, Awwwards-style interactions, smooth scroll reveals, staggered text, parallax, pinned sections, magnetic hover states, custom cursors, and mouse-reactive layered movement.

MengTo/Skills

Create cinematic scroll-driven landing pages with Lenis smooth scrolling, GSAP ScrollTrigger, scroll-linked progression, staggered text reveals, sticky card stacks, parallax backgrounds, scroll-scrubbed transitions, footer reveals, and immersive preloaders. Use when analyzing or building premium editorial scroll experiences, sticky project stacks, kinetic typography, or section-by-section storytelling.

MengTo/Skills

Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.

Related Skills