# Light Scene > Use when a PlayCanvas scene must read as a deliberate image rather than a flat asset preview — photoreal and cinematic, or stylized, low-poly, and palette-driven — to set key and ambient lighting, sky and image-based lighting, shadows, tone mapping and exposure, water, and a restrained post-process grade of bloom, fog, and colour. - Skill: `playcanvas/light-scene` (Agent Skill) - Install (CLI): `npx skillmds@latest add playcanvas/light-scene` - Raw SKILL.md: https://api.skillmd.com/api/skills/playcanvas/light-scene/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: playcanvas (https://skillmd.com/u/playcanvas) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/playcanvas/light-scene --- # Cinematic rendering A polished frame is lit and graded, not just populated. Treat lighting, sky, shadows, tone mapping, and post as one pass over the assembled scene, and tune every value against a real screenshot rather than from memory. ## Confirm art direction before implementation Follow the user's specified or approved direction. When it is unresolved, present concrete options using references, mockups, or inexpensive rendered variants and get approval before substantial implementation. Prefer a side-by-side variant sheet when cheap to produce. Work within the approved direction and confirm significant departures before implementing them. ## Choose the path from the brief Read the reference before wiring any pipeline. A photoreal or cinematic brief takes the runtime HDR path below. A brief whose reference is low-poly, flat-shaded, toon, or palette-driven — or whose startup, frame, or payload budget rules out the runtime pipeline — takes the stylized path: banded or flat shading through `override-shader-chunks`, a solid or gradient sky, static lighting through `bake-lighting`, and no `Water` or `CameraFrame`. A remark such as "look at the water script" is a pointer to inspect it; confirm any resulting change of art direction before integration. On either path, dynamic objects and their attachments must sample or approximate the baked or ambient occlusion so they dim to the same levels as the surfaces around them, grounded with contact shadows. ## Runtime HDR path Prefer shipped building blocks over hand-written shaders and passes. Discover them with the `reuse-scripts` skill and adapt the closest official example with `find-examples`: - the core `CameraFrame` helper for tone mapping, ambient occlusion, bloom, vignette, and grade; - a procedural sky and image-based light for ambient colour and reflections; - a shadow catcher for grounding subjects that have no lit floor. For an outdoor scene whose brief asks for reflective, photoreal water, stop before authoring the scene and read both `reuse-scripts` and `find-examples`. Use `graphics/water.example.mjs` as the initial composition recipe: it already joins the production `Water` script, sky, sun, `CameraFrame`, water layer, scene depth, and reflection pipeline. Get that complete frame rendering before replacing its assets or tuning its look; a custom normal-mapped material or tessellated plane is not that baseline. For that water scene, keep both production integrations visible in the implementation: - import and create `Water` from `playcanvas/scripts/esm/water.mjs` on the water entity, preserving the example's required render component, camera reference, water layer, depth map, and textures; - construct `CameraFrame` from `playcanvas` for the gameplay camera, set a deliberate tone map and restrained grade, call `update()`, and destroy it with the application. Do not continue to cosmetic tuning while a required integration is missing or diagnostics report a shader, texture, or framebuffer error. ## Light and expose - Establish one dominant key light with a clear direction and warm or cool intent, then add soft fill or ambient so shadows are not crushed to black. A single flat ambient with no key reads as an asset gallery. - Choose a physically based tone mapping and a deliberate exposure, then balance light intensities to that exposure, not the reverse. - Drive ambient and reflections from the sky or an environment map, not a constant colour, so materials pick up their surroundings. - Tune the HDR stack in isolation before styling it. Begin with neutral tone mapping, scene exposure `1`, procedural-sky luminance near its official-example value, bloom off, grading neutral, fog off, and reflection/specular strengths at their defaults. Capture a screenshot, then change one class of value at a time. Do not simultaneously raise key intensity, sky luminance, exposure, reflection, saturation, fog brightness, and bloom. - Treat linked procedural skies as the owner of the sun light's direction, colour, and intensity. Set the light's base intensity before assigning it to the sky and tune the sky elevation/azimuth; do not also hand-author the light transform or colour as though they remained independent. - Preserve the source assets' albedo colours. If diffuse texture colours collapse toward white or a single warm tint, reduce the HDR stack before compensating with darker material colours. ## Shadow and ground - Enable shadows on the key light and size the shadow area and resolution to the framed subject, not the whole world. Soften the penumbra rather than only raising resolution. - Ground subjects with a contact or catcher shadow when the surface beneath them is not itself lit. ## Grade with restraint - Bloom, fog, vignette, and colour grade unify a frame; overdone bloom and heavy fog destroy silhouette and depth. Start subtle and increase only against the screenshot. `CameraFrame` bloom intensity is documented for the `0` to `0.1` range; stay inside it. - Match fog colour and density to the sky so the horizon stays coherent. - Preserve surface detail through the brightest reflection path. If glare clips a large part of the frame to white or a reflection becomes an opaque black blob, rebalance exposure, light intensity, reflection strength, and shadow bias before adding more post-processing. - Compare both the brightest surface and the shadow-facing side of the hero subject in the same screenshot. Reject the grade if either broad highlight clipping or crushed-black silhouette hides texture detail. A mechanically valid frame is not visually complete while either failure remains. ## Prove the look For changes to an existing look, show old and new at the same pose in one image. If the difference is not visible, report that before spending more time tuning. Tune against pixels, not numbers. Capture the intended framing with an image-returning browser screenshot tool and inspect the returned image, as `apply-conventions` and the local agent guide require; a saved filepath is not evidence. Use two fixed poses, capture with a headless browser, and return images at accept-or-reject points only, not after every edit. Confirm the subject is exposed and readable, shadows are present but not crushed, and the grade is restrained, from the real gameplay camera at the target resolution. Confirm the post-process camera keeps rendering as it orbits and pitches. Choose the authoring surface with the `build-app` skill and set lights, camera, and scene settings through its own primitives before reaching into the Engine.