3D Game Development

VerifiedSafe

Principles of 3D game development: rendering, shaders, physics, cameras, and lighting.

Sby Skills Guide Bot
DevelopmentIntermediate
7/24/2026
Claude CodeCursorWindsurfCopilotCodex
#game-development#3d-graphics#shaders#rendering#physics

Recommended for

Automated summary

A principles cheat sheet for 3D game development covering the rendering pipeline, shaders, physics, cameras, lighting and LOD.

Strengths

  • Covers the whole 3D stack (rendering, shaders, collisions, cameras, lighting) in one short document
  • Clear mapping tables between technique and use case (collider shapes, camera types, light types)
  • Ships an anti-pattern list that is directly actionable for performance reviews
  • Engine-agnostic, so it transfers to Unity, Unreal, Godot or WebGL work

Limitations

  • Purely conceptual: no code snippets, APIs or concrete configuration
  • Does not spell out engine-specific implementations, which differ substantially
  • Advanced topics (shadow cascades, compute shaders) get only a one-line mention
When to use it

Use it as a design reference or checklist when reviewing a 3D game's architecture and optimization plan.

When not to use it

Skip it if you need ready-to-paste code or step-by-step instructions for a specific engine such as Unity, Unreal or Godot.

Security analysis

Safe
Quality score78/100

The skill is purely informational, describing 3D game development principles. It uses only read/write/edit/glob/grep tools and contains no destructive commands, network activity, secret handling, or obfuscated content.

No concerns found

How this analysis is made

Examples

Camera feel review
Here is my third-person camera controller. Review it against 3D camera principles: smooth lerp following, collision avoidance and look-ahead. What should I change?
Shader cost triage
My fragment shader tanks the frame rate on mid-range GPUs. Walk me through profiling it and deciding what to simplify or bake.
LOD and collider plan
Help me plan LOD levels and collider shapes for an open-world scene with terrain, buildings and characters, keeping mesh colliders to a minimum.

name: 3d-games description: 3D game development principles. Rendering, shaders, physics, cameras. allowed-tools: Read, Write, Edit, Glob, Grep

3D Game Development

Principles for 3D game systems.


1. Rendering Pipeline

Stages

1. Vertex Processing → Transform geometry
2. Rasterization → Convert to pixels
3. Fragment Processing → Color pixels
4. Output → To screen

Optimization Principles

| Technique | Purpose | |-----------|---------| | Frustum culling | Don't render off-screen | | Occlusion culling | Don't render hidden | | LOD | Less detail at distance | | Batching | Combine draw calls |


2. Shader Principles

Shader Types

| Type | Purpose | |------|---------| | Vertex | Position, normals | | Fragment/Pixel | Color, lighting | | Compute | General computation |

When to Write Custom Shaders

  • Special effects (water, fire, portals)
  • Stylized rendering (toon, sketch)
  • Performance optimization
  • Unique visual identity

3. 3D Physics

Collision Shapes

| Shape | Use Case | |-------|----------| | Box | Buildings, crates | | Sphere | Balls, quick checks | | Capsule | Characters | | Mesh | Terrain (expensive) |

Principles

  • Simple colliders, complex visuals
  • Layer-based filtering
  • Raycasting for line-of-sight

4. Camera Systems

Camera Types

| Type | Use | |------|-----| | Third-person | Action, adventure | | First-person | Immersive, FPS | | Isometric | Strategy, RPG | | Orbital | Inspection, editors |

Camera Feel

  • Smooth following (lerp)
  • Collision avoidance
  • Look-ahead for movement
  • FOV changes for speed

5. Lighting

Light Types

| Type | Use | |------|-----| | Directional | Sun, moon | | Point | Lamps, torches | | Spot | Flashlight, stage | | Ambient | Base illumination |

Performance Consideration

  • Real-time shadows are expensive
  • Bake when possible
  • Shadow cascades for large worlds

6. Level of Detail (LOD)

LOD Strategy

| Distance | Model | |----------|-------| | Near | Full detail | | Medium | 50% triangles | | Far | 25% or billboard |


7. Anti-Patterns

| ❌ Don't | ✅ Do | |----------|-------| | Mesh colliders everywhere | Simple shapes | | Real-time shadows on mobile | Baked or blob shadows | | One LOD for all distances | Distance-based LOD | | Unoptimized shaders | Profile and simplify |


Remember: 3D is about illusion. Create the impression of detail, not the detail itself.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/3d-game-development-mryiqitc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/3d-game-development-mryiqitc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/3d-game-development-mryiqitc/download' --output '.skill-downloads/3d-game-development-mryiqitc/SKILL.md.part' && mv '.skill-downloads/3d-game-development-mryiqitc/SKILL.md.part' '.skill-downloads/3d-game-development-mryiqitc/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && test -s '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/3d-games' && cp -R '.skill-downloads/3d-game-development-mryiqitc' '.claude/skills/3d-games'

Cursor
test -f '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && test -s '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/3d-games' && cp -R '.skill-downloads/3d-game-development-mryiqitc' '.cursor/skills/3d-games'

Codex
test -f '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && test -s '.skill-downloads/3d-game-development-mryiqitc/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/3d-games' && cp -R '.skill-downloads/3d-game-development-mryiqitc' '.agents/skills/3d-games'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/3d-game-development-mryiqitc'

openskills read '3d-game-development-mryiqitc'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/3d-game-development-mryiqitc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills