Skip to content
cccskills
FreePublished on GitHub

build-vesperfall-review-assets

Prepare Vesperfall game assets as paired transparent PNG cards and live 3D previews. Track each model’s actual source, expose available animations, and validate catalog displays, ground contact, and review pages through tests and browser checks.

OriginalShow the original description

Build truthful Vesperfall asset-library review pairs from transparent PNG references and live Three.js, FBX, or img2threejs models. Use when adding a character, enemy, prop, or equipment asset to the Vesperfall catalog; creating a card-PNG plus inspector-model treatment; exposing an isolated model or moveset route; or standardizing provenance, grounding, tests, and Codex-browser validation for game art review.

MengTo/Skills

Run score Not tested

See how to install

Good for

  • Adding characters or equipment to the Vesperfall catalog
  • Pairing transparent PNG cards with live 3D previews
  • Reviewing animations and ground contact on an isolated page
  • Verifying asset sources and catalog behavior

Files included (4)

  • SKILL.md3.4 KB
  • agents/openai.yaml273 B
  • references/catalog-contract.md1.7 KB
  • scripts/validate_pair.py1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Build Vesperfall Review Assets

Create one reviewable asset pair without confusing catalog media, imported files, procedural factories, and future contracts.

Workflow

  1. Inspect repository truth before choosing a model path.
    • Locate shipped PNG, FBX, GLB, textures, runtime factories, and declared-but-missing paths.
    • Prefer a shipped FBX/GLB when it is the actual runtime source.
    • Use $img2threejs only when reconstructing from an image in code. Never relabel imported geometry as img2threejs.
    • Do not claim a GLB or texture exists because code declares a future URL.
  2. Produce the transparent catalog reference.
    • Reuse or derive from the production portrait when it already matches the asset identity.
    • Normalize catalog copies to 512×512 RGBA unless the project contract says otherwise.
    • Keep transparent corners and avoid baked floor, halo, or shadow.
    • Store project-bound output under public/asset-catalog/<category>/.
  3. Build the live model preview.
    • Put loading/model construction in a small asset-specific module.
    • Preserve runtime provenance in userData: source paths or factory, action count, sockets, and review-only status.
    • Attach equipment to named sockets. Keep materials, renderer, mixers, events, and animation frames disposable.
    • Frame from measured bounds. Ground from foot/contact geometry, not the lowest weapon tip.
  4. Pair the catalog surfaces.
    • Card/grid: transparent PNG only, with no canvas.
    • Selected inspector: one live model canvas plus truthful format label.
    • Add a button to an isolated preview or moveset route.
    • Keep fallback media visible until WebGL/model loading is ready.
  5. Build the isolated review route.
    • Expose the real action library when clips exist.
    • Provide restart, pause/play, action selection, drag rotation, source paths, and provenance.
    • For procedural motions, mark runtime, contract, and candidate actions separately.
  6. Validate before committing.
    • Run scripts/validate_pair.py <png> <model-source>.
    • Add inventory tests for exact paths, RGBA dimensions, preview kind, and route.
    • Test every motion/contact point deterministically when grounding changes with animation.
    • Run build, lint, full tests, and git diff --check.
    • Use the Codex in-app browser only. Verify desktop and mobile, card PNG/no canvas, inspector model/one canvas, preview navigation, grounding, scroll, overflow, broken media, and console warnings/errors.
  7. Commit the narrow task and hand off its exact SHA before deployment reconciliation.

Read references/catalog-contract.md when changing catalog types, provenance language, or review-route behavior.

Required reporting

Report:

  • PNG path, dimensions, and alpha status
  • model source or procedural factory
  • whether the model is imported, runtime procedural, or review-only reconstruction
  • preview route and available actions
  • test/build/browser proof
  • exact commit SHA

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

3d-cloth-material

FreeSummary

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/Skills7KUpdated Oct 18, 2026

3d-falling-leaves

FreeSummary

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/Skills7KUpdated Oct 18, 2026

3d-four-seasons

FreeSummary

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/Skills7KUpdated Oct 18, 2026

3d-high-poly-models

FreeSummary

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/Skills7KUpdated Oct 18, 2026

3d-high-resolution-textures

FreeSummary

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/Skills7KUpdated Oct 18, 2026

3d-metal-material

FreeSummary

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/Skills7KUpdated Oct 18, 2026

See all skills by MengTo

Report a problem with this skill