Prompts for the supported ToonLab workflow

Using the ToonLab game-dev skill, integrate @call-me-sensei/toonlab into this
existing Three.js scene. Inventory every renderable root and material. Assign
stable ToonLab target ids, rendering domains, material ids, and semantic roles.
Apply the Call Me Sensei bundle in strict mode through the documented focused
runtimes for the domains actually present. Preserve the scene's geometry, XZ
layout, cameras, gameplay, dynamic physics, navigation, and frame loop. Run the
app's typecheck, tests, build, and visual smoke check. Finish only when the
style audit is ready or report each remaining blocker with a concrete fix.

Using the ToonLab toon-shading or environment skill as appropriate, create a
true before/after comparison for the supplied model. The before side must use
its normal Three.js PBR material and the same camera, pose, lights, exposure,
background, and source textures as the after side. The after side may change
only the selected ToonLab shader/profile. Do not flatten, unlight, or otherwise
degrade the before side. Verify that the comparison demonstrates the shader's
effect rather than a scene-lighting difference.

Using the ToonLab asset-sourcing skill and whichever ToonLab MCP servers are
connected, load get_anime_game_profile and confirm the project's sourcing
policy. Search project/local Library first, then ToonLab Gallery, then allowed
external open sources. Validate provenance, license, anime-style support, and
policy decision before selection. Generate only after the searches fail and a
custom asset gap has been recorded and approved. Report the selected stable id,
source, license, dimensions, semantic domain, and material-role readiness.

Use ToonLab MCP to call list_live_labs, choose the named public Lab, and call
get_lab_features before editing. Create a schema-valid starter with
create_lab_document, make only requested semantic changes, and validate the
result. Save it to my Library only if I asked for persistence. Keep preview
camera, stage, lighting, playback, and comparison state out of the portable
document.

Use ToonLab MCP to find a seamless material for the named surface. Search my
Library, ToonLab Gallery, and policy-permitted external sources first. If they
are insufficient, record the exact material gap, call
get_generation_capabilities, show me the enabled material provider and exact
credit cost, and wait for approval. Then generate one grouped material asset,
poll it to ready, save it with save_generated_asset, and report every included
map, resolution, provenance field, and gap id.

After Library, Gallery, and permitted external searches fail, record a custom
gap for the named asset and get my approval. Call get_generation_capabilities
and choose Meshy or Tripo explicitly based on the required operation. Generate
with a fresh UUID idempotency key, poll every returned job id, save the ready
model with save_generated_asset, and validate its license/provenance, scale,
semantic domain, material roles, and ToonLab style result before use.

Using the ToonLab vegetation-sky skill, create the requested tree, shrub,
grass, or groundcover with the public vegetation runtime. Keep species/recipe,
seed, geometry, palette, and placement separate from the Tree/Grass/Flower
shader profile. Emit stable modeled-part and material-role labels, preserve
the recipe for regeneration, and verify LOD and shadow behavior. Do not use the
repository-only experimental species engine.

Using the ToonLab rockgen and rock-ground-shaders skills, create or edit the
requested rock asset with @call-me-sensei/toonlab/rockgen and style it with
@call-me-sensei/toonlab/rock-shader. Keep geometry identity, seed, LOD,
collision, and baked channels in the rock document; keep reusable appearance in
the rock shader profile. Validate the portable documents and verify the result
from multiple useful views. Do not deep-import repository compilers or test
fixtures.

Using the ToonLab scene-style-application skill, load the selected portable
Style Bundle. Inventory and explicitly label only the domains present in this
scene, audit in strict mode, and stop before mutation if any target, material
role, required mask, or adapter is missing. Apply the accepted plan atomically,
preserve asset identity and current scene conditions, then verify that every
populated slot has an owning runtime and that teardown restores the source
materials.

Using the ToonLab visual-verification skill, inspect the requested result at
the camera ranges and lighting states that matter to the game. Check isolation,
silhouette, source-texture preservation, cool/blue shadow response, material
roles, LOD transitions, and outliers. Run the project's normal typecheck, tests,
and build. Report what passed, what remains host-owned, and every unsupported or
custom gap; do not call the result complete from a single favorable screenshot.