본문으로 건너뛰기
cccskills
무료GitHub에 공개

webgl-landing-steering

Choose a visual direction for landing pages using WebGL, a browser graphics technology. Balance brand style with readable copy, clear calls to action, mobile performance, accessibility, and implementation effort, then define fallbacks and build priorities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Choosing a visual direction for a WebGL landing page
  • Planning a launch page around a 3D product model
  • Improving mobile performance and reducing motion
  • Defining static fallbacks and implementation priorities

포함된 파일(5)

  • SKILL.md5.0 KB
  • demo/index.html16.1 KB
  • demo/preview.jpg66.2 KB
  • demo/PROMPT.md1.9 KB
  • REFERENCES.md351 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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)

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build woven fabric in Three.js with visible threads, realistic sheen, seams, and thick hems. The skill covers folds that preserve texture proportions, light passing through thin cloth, and variations in dye and wear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating backlit curtains
  • Differentiating linen, silk, and wool
  • Adding hems and stitches for close-up views
MengTo/Skills7천2026년 10월 18일 업데이트

Build falling leaves in Three.js and similar 3D scenes, with visible front, edge, and back views as they tumble and drift. Coordinate wind, scene depth, camera-aware recycling, and performance checks for a convincing autumn effect.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding falling autumn leaves to a 3D scene
  • Coordinating leaf tumble, sideways drift, and wind
  • Managing leaves around buildings and camera movement
MengTo/Skills7천2026년 10월 18일 업데이트

Add coordinated seasonal transitions to an existing 3D scene. Blend foliage, lighting, sky, ground, snow, and particles from one shared state while preserving camera controls and interactions, so the same place remains recognizable throughout spring, summer, fall, and winter.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Add a four-season selector to an outdoor 3D scene
  • Show seasonal changes in an architectural walkthrough
  • Coordinate foliage, sunlight, sky, and ground appearance
MengTo/Skills7천2026년 10월 18일 업데이트

Create or integrate detailed 3D models with smooth outlines and believable edges for close-up views. Prepare lower-detail versions for distant viewing, prioritize loading, and measure rendering costs in the actual scene.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a detailed 3D model for close-up views
  • Replacing visibly faceted curves with smoother geometry
  • Preparing detailed architectural assets for rendering
MengTo/Skills7천2026년 10월 18일 업데이트

Prepare detailed 3D materials that remain clear in close-up views. The skill guides texture resolution, physically based material maps, surface mapping, filtering, and progressive loading while checking download size and GPU memory use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Prepare wood, stone, and fabric materials for close-up views
  • Fix texture seams, grain direction, and normal map orientation
  • Preserve floor and foliage detail at oblique or distant views
MengTo/Skills7천2026년 10월 18일 업데이트

Create realistic metal surfaces in Three.js by combining structured reflections, studio lighting, scratches, fingerprints, and beveled edges. Includes polished, brushed, and aged finishes for objects such as tools, rings, and metal product parts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Fixing metal that looks like gray plastic
  • Creating polished or brushed metal finishes
  • Adding patina and worn edges
MengTo/Skills7천2026년 10월 18일 업데이트

MengTo의 스킬 모두 보기

이 스킬의 문제 신고