3D game development principles. Rendering, shaders, physics, cameras.
✓Works with OpenClaude1. 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.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Related community Skills
Other Claude Code skills in the same category — free to download.
board-prep
/em -board-prep — Board Meeting Preparation
browserstack
>-
challenge
/em -challenge — Pre-Mortem Plan Analysis
code-to-prd
|
codebase-onboarding
Codebase Onboarding
competitor-alternatives
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparis
content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \"content strategy,\" \"what should I write about,\"
contract-and-proposal-writer
Contract & Proposal Writer
Want a community skill personalized to YOUR project?
This is a generic skill that works for everyone. Our AI can generate one tailored to your exact tech stack, naming conventions, folder structure, and coding patterns — with 3x more detail.