
renderer
Architecture rules for GPU rendering with TypeGPU/WebGPU. Use when adding or changing render passes, shaders, frame orchestration, GPU resources, culling, terrain, shadows, or visual performance work.
- Installs
- 259
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/dzhng/skills --skill renderer- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads renderer automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
GPU renderer
The renderer is TypeGPU over WebGPU. It draws plain frame inputs the application hands it and never reaches into simulation or app state. These are the flaws that sink a 3D experience; check a change against each before writing it.
- Fixed-view cost never grows with world size. For a fixed camera and render size, submitted geometry, shadow casters, and per-frame lists are bounded by what the view can see or cast into, and screen-space work by pixels. Store the world map-wide; select from it spatially. Frustum clipping does not make vertices free.
- One owner per contract. Frame orchestration, camera, depth convention, targets, culling, lighting, timing, and resource lifetime each have one owner every pass shares. Extend it; a second copy drifts.
- Shared contracts change together. Depth and lighting are engine-wide: every pass reads the same convention and every material the same shading path. A per-pass exception is a future visual bug.
- No GPU resource without a lifetime owner. Everything is allocated through the registry, rebuilds swap in whole, and repeated resize/rebuild/reset returns to baseline.
- Pixels prove correctness, not counters. An optimization is accepted only with an interleaved A/B on the real GPU and an image that shows the subject still drawn correctly.
FAQ
What does the renderer skill do?
Architecture rules for GPU rendering with TypeGPU/WebGPU. Use when adding or changing render passes, shaders, frame orchestration, GPU resources, culling, terrain, shadows, or visual performance work.
How do I install renderer?
Run npx skills add https://github.com/dzhng/skills --skill renderer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/renderer/ (personal) or .claude/skills/renderer/ (project).
Which AI agents can use renderer?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is renderer safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains renderer?
It is published by dzhng in dzhng/skills. It has 259 recorded installs.
More from dzhng/skills
refactor-clean
dzhng/skills
Open the skill to read its SKILL.md instructions.
implement-spec
dzhng/skills
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.