agentleFS
Oliyflemishspeaking560Oliyflemishspeaking560/threejs-game-skills/skills/threejs-aaa-graphics-builder/SKILL.md

threejs-aaa-graphics-builder

Skill0 starsChanged 5 months agoMITView on GitHub

Upgrade Three.js games from basic/prototype visuals to premium AAA-inspired browser graphics. Combines art-direction critique, procedural model building, mandatory external asset sourcing decisions, threejs-3d-generator assets, threejs-image-generator concept/texture workflows, scene visual polish, material/texture libraries, world prop kits, VFX, render pipeline, and visual scorecard gates. For premium games with characters, vehicles, ships, weapons, buildings, signature props, skies, textures, decals, logos, icons, or GUI art, load the relevant generator skills before deciding procedural assets are enough.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the director credential probe before using key unavailable as a skip reason and paste the SET/MISSING output.

    line 34
  2. Distinctive:

    Create an asset sourcing ledger for each high-value surface: procedural / threejs-image-generator / threejs-3d-generator / hybrid, plus …

    line 35
  3. Distinctive:

    Add missing graphics architecture: material library, procedural textures/decals, model factories, world prop kit, VFX system, render …

    line 43
  4. Very specific:

    Run the credential probe, then fill the external asset sourcing ledger per surface: procedural Three.js factory, threejs-image-generator 2D …

    line 44
  5. Very specific:

    Add lighting/render/material polish after authored forms exist.

    line 46
  6. Distinctive:

    Add event-driven VFX tied to gameplay state.

    line 47
  7. Distinctive:

    Verify renderer diagnostics, desktop/mobile screenshots, console/page errors, canvas pixels, imported asset budgets, and playability.

    line 49
  8. Distinctive:

    Do not make primitives look AAA by adding glow.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Three.js AAA Graphics Builder

Purpose

Own the production graphics pass. Convert basic screenshots into authored, high-density, performance-aware visual experiences.

Use When

Screenshots still look basic, models look primitive, worlds are sparse, UI/world art feels generic, or the user asks for premium, AAA, high-fidelity, showcase, or less-basic graphics.

Required References

These references are required phase-entry gates, not optional reading:

  • Load references/visual-scorecard.md before scoring, judging completion, or making any premium/AAA/showcase claim.
  • Load references/implementation-blueprint.md before changing graphics architecture, materials, VFX, rendering, diagnostics, or broad visual systems.
  • Load references/model-recipes.md before building or upgrading hero/player, obstacle, enemy, pickup, world-kit, material, or prop models.
  • Load references/render-recipes.md before changing lighting, tone mapping, shadows, fog, post-processing, materials, or render composition.
  • Load references/checklists/aaa-game-quality-gate.md and references/checklists/aaa-visual-scorecard.md before declaring a game premium, AAA, showcase, complete, release-ready, or less basic.
  • Load the relevant checklist before focused work: references/checklists/procedural-model-quality.md, references/checklists/material-lighting-quality.md, or references/checklists/performance-safe-visual-detail.md.
  • Load references/prompt-templates.md only when the user asks for reusable prompts, a graphics-pass prompt, or a task template.

For broad "still looks basic", premium, AAA, high-fidelity, showcase, or less-basic graphics work, load all four references as the first action in the phase. Track them in a reference ledger with yes/no, path, and failure reason. Do not mark the graphics phase complete while any required reference is skipped.

External asset sourcing gate:

  • For premium/AAA/showcase/high-fidelity/less-basic graphics with a hero/player, character, creature, boss, vehicle, ship, building, weapon, signature prop, complex pickup, or hero environment piece, load threejs-3d-generator before deciding procedural geometry is enough.
  • For premium/AAA/showcase/high-fidelity/less-basic graphics with concept needs, texture/material references, decals, logos, faction marks, icons, GUI art, skies, backgrounds, title/menu art, or image-to-3D inputs, load threejs-image-generator before deciding 2D external assets are not needed.
  • Run the director credential probe before using key unavailable as a skip reason and paste the SET/MISSING output.
  • Create an asset sourcing ledger for each high-value surface: procedural / threejs-image-generator / threejs-3d-generator / hybrid, plus outputs or skip reason.
  • not-needed is valid only after the relevant skill was loaded and the ledger explains why external generation would not improve a non-hero support surface, or why the credential probe or attempted generation shows a real blocker.
  • For premium hero surfaces, procedural-only is not an allowed final answer unless there is real blocker evidence. At least one high-value surface must show a 3D generator task ID, downloaded GLB/GLTF/FBX path, image generator output path, or documented hybrid chain.

Workflow

  1. Capture or inspect active desktop/mobile screenshots.
  2. Score visuals across art direction, hero/player, obstacles, rewards, world, materials, render, VFX, UI, and performance evidence.
  3. Add missing graphics architecture: material library, procedural textures/decals, model factories, world prop kit, VFX system, render pipeline, diagnostics.
  4. Run the credential probe, then fill the external asset sourcing ledger per surface: procedural Three.js factory, threejs-image-generator 2D reference/texture, threejs-3d-generator 3D generation, or a hybrid.
  5. Upgrade every weak visible surface, not only one hero object.
  6. Add lighting/render/material polish after authored forms exist.
  7. Add event-driven VFX tied to gameplay state.
  8. Re-score screenshots. Continue until every premium category is at least 2/3 or report exact blockers.
  9. Verify renderer diagnostics, desktop/mobile screenshots, console/page errors, canvas pixels, imported asset budgets, and playability.

Core Rule

Do not make primitives look AAA by adding glow. First build authored forms, then materials, then lighting, then effects.

Final Response

Report the reference ledger, credential probe output, external asset sourcing ledger, score before/after, production surfaces upgraded, files changed, screenshots/artifacts, renderer diagnostics, imported asset diagnostics when relevant, and remaining blockers. For premium/AAA/showcase claims, include the filled visual scorecard exactly as defined in references/visual-scorecard.md, including average and automatic failures remaining.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.