Skip to content
Skillpedia
General coding48k · #3069

3d-games

Helps your agent understand 3D game development principles. Useful for creating games with three-dimensional graphics, including rendering and shaders.

What it does

This AI agent helps understand the basic principles of creating 3D games. It explains how graphics are drawn on screen, how to create visual effects with 'shaders', how to simulate physics and collisions, and how cameras and lighting work.

When to use it

  • ✓When learning about 3D game development.
  • ✓When wanting to understand how game graphics are made.
  • ✓When optimizing the performance of a 3D game.

Example of what to ask your AI

“How does 3D graphics rendering work in a game?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/game-development/3d-games/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/game-development/3d-games/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

It details the steps in the rendering process, from transforming objects to displaying them on screen. It also explains techniques to make games faster and visually interesting.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill 3d-games

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/game-development/3d-games/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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

  • Frame-rate-independent smoothing; test camera collision and teleports
  • 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 Reduced detail based on measured visual error
Far Low-detail mesh or billboard when visually appropriate

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

Use when implementing or profiling a 3D rendering pipeline, shaders, colliders, cameras, lighting or level-of-detail transitions.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Verification

Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.

FAQ

What is the 'rendering pipeline'?

It's the path that 3D game data takes to be turned into an image you see on screen, going through stages like vertex processing and pixel coloring.

What are 'shaders'?

They are small programs that control how 3D objects are drawn, defining colors, textures, and lighting effects, allowing for unique visuals like water, fire, or cartoons.

Why use simple shapes for collisions instead of complex models?

Using simple shapes (like boxes or spheres) to detect collisions is much faster and more efficient for the computer, allowing the game to run better, even if the objects look complex visually.

Details

Original description by the author

3D game development principles. Rendering, shaders, physics, cameras.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#3069
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills