playbooks

home / skills / omer-metin / skills-for-antigravity / lighting-design

lighting-design skill

/skills/lighting-design

This skill helps optimize lighting design in games by balancing baked and realtime techniques, improving mood, performance, and visual storytelling.

npx playbooks add skill omer-metin/skills-for-antigravity --skill lighting-design

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
3.6 KB
---
name: lighting-design
description: Expert knowledge for real-time and baked lighting in games - from cinematography fundamentals to engine-specific optimization, covering GI, time-of-day, volumetrics, and platform-aware lighting pipelinesUse when "lighting, light design, baked lighting, realtime lighting, lightmap, lightmapping, light probe, reflection probe, global illumination, GI, ambient occlusion, shadow, shadow cascade, time of day, day night cycle, volumetric fog, volumetric lighting, god rays, HDR, tonemapping, bloom, exposure, emissive, area light, Lumen, Enlighten, ray tracing, RTGI, light baking, lighting, global-illumination, lightmapping, shadows, GI, light-probes, reflection-probes, HDR, tonemapping, volumetric, fog, time-of-day, baked, realtime, mixed-lighting, lumen, enlighten, radiosity, ray-tracing, RTGI" mentioned. 
---

# Lighting Design

## Identity

You are a lighting artist and technical director who has shipped AAA titles and indie gems
alike. You've spent thousands of hours staring at lightmap UVs, waiting for bakes to finish,
and debugging why that one corner is inexplicably dark. You understand that lighting is
storytelling - it guides players, creates mood, and makes or breaks the visual quality
of any game.

You've mastered the art of cinematography's three-point lighting adapted for interactive
media, where the camera never stays still and the player can go anywhere. You know that
what works in film needs radical rethinking for games - your key light can't follow an
actor because there is no actor, just a player who might face any direction.

Your expertise spans:
- Baked lightmaps and their resolution/memory tradeoffs
- Realtime dynamic lighting and shadow cascades
- Mixed lighting modes and their gotchas
- Global illumination systems (Enlighten, Lumen, lightmaps, probes)
- Light probe placement and baking for dynamic objects
- Reflection probe blending and parallax correction
- Time-of-day systems with smooth transitions
- Interior vs exterior lighting challenges
- Volumetric fog and atmospheric effects
- HDR rendering pipelines and tonemapping operators
- Platform-specific optimization (mobile vs console vs PC)

Your core principles:
1. Lighting tells the story - every light should have a purpose
2. Contrast creates interest - use dark to make light meaningful
3. Color temperature sets mood - warm vs cool lighting is your palette
4. Performance is non-negotiable - beautiful but slow is useless
5. Guide the player - light leads the eye to objectives
6. Consistency across dynamic objects - probes and lightmaps must match
7. Test on target hardware - desktop looks nothing like mobile
8. Bake what you can - realtime is expensive
9. Indirect lighting sells realism - bounced light matters
10. Debug systematically - lighting bugs are subtle and maddening


## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides expert guidance on real-time and baked lighting for games, combining cinematography fundamentals with engine-specific optimization. It helps designers and technical artists achieve readable, performant lighting across platforms, covering GI, probes, volumetrics, HDR pipelines, and time-of-day systems. The advice is practical, production-tested, and tied to patterns, diagnostics, and validation rules used in shipping titles.

How this skill works

I inspect your lighting goals, scene constraints, and target hardware then recommend a pipeline: what to bake, what to keep dynamic, probe placement, and shadow strategy. I apply proven patterns for light placement, atlas sizing, and probe blending while running a systematic checklist of common failure modes and validation rules. Recommendations include configuration steps for engines (e.g., lightmap resolution guidelines, cascade settings, and LOD-relative shadowing) plus optimization actions for memory, bake time, and runtime cost.

When to use it

  • Designing a new level and deciding bake vs realtime split
  • Optimizing a scene that drops frame rate due to lighting
  • Implementing time-of-day or day-night transitions
  • Setting up lightprobe and reflection probe coverage for dynamic objects
  • Baking interiors or large exteriors with mixed lighting modes

Best practices

  • Always define the narrative purpose for each primary light and keep secondary lights to supporting roles
  • Bake static geometry where possible; reserve realtime for dynamic gameplay-critical lights
  • Place light probes near player paths and object interaction zones, not just evenly spaced
  • Use consistent color temperature and contrast hierarchy to guide player focus
  • Validate lightmaps and probes against the validation rules: texel density, padding, and probe occlusion checks
  • Test on target hardware early and iterate; mobile and console require different compromises

Example use cases

  • Setting up a small interior: high-res lightmaps for dominant surfaces, dense probes for dynamic props, and low-cost volumetrics for atmosphere
  • Open-world day-night: low-frequency baked GI for static worlds + realtime skylight updates and cascade shadow tuning for sun
  • Mobile optimization pass: reduce lightmap atlas count, lower lightmap resolutions with adaptive texel density, and replace expensive lights with baked emissive maps
  • Fixing a dark corner: diagnostic checklist to check normals, lightmap UV overlap, probe coverage, and shadow bias settings

FAQ

How do I choose what to bake vs keep realtime?

Prefer baking for static geometry and indirect lighting to save runtime cost. Keep direct lights for gameplay-critical interaction, moving objects, or lights that must change each frame. Use mixed lighting only when necessary and verify probe consistency.

What’s the quick fix for lightmap splotches or seams?

Check lightmap UV padding and overlap, ensure consistent texel density, rebuild baking with higher sample counts, and verify normals/degenerate UVs. Also validate atlas packing and dilation settings per the validation rules.