unity-rendering
Unity rendering pipelines (Built-in / URP / HDRP), Shader Graph, Renderer Features, Volume framework, post-processing, materials, lighting, and GPU Resident Drawer. USE WHEN: choosing or migrating rendering pipeline, writing/editing shaders (Shader Graph, HLSL, ShaderLab), tuning lighting, debugging draw calls, configuring Volume profiles, custom render passes. DO NOT USE FOR: 2D Renderer specifics (use `unity-2d-lighting`); UI Toolkit rendering (use `unity-input-ui`); profiling-only questions (use `unity-performance`).
What this skill does
# Unity Rendering
## Pipeline selection
| Pipeline | Use when | Avoid when |
|---|---|---|
| **URP** | Mobile, indie, mid-fidelity, broad platform reach, custom Renderer Features | Cinematic AAA, volumetrics, screen-space GI |
| **HDRP** | High-end PC/console, photoreal, advanced lighting | Mobile, WebGL, low-spec hardware |
| **Built-in** | Legacy projects, very specific shaders not portable | New projects (default to URP) |
Switching pipeline mid-project is painful — pick once, upfront.
## Shader Graph (URP/HDRP)
```
Vertex stage → object-space → world-space transforms, vertex displacement
Fragment → albedo, normal, metallic, smoothness, emission, AO
Custom Function node → write HLSL inline for branchless ops
Subgraph → reusable groups; export as .shadersubgraph
```
Author URP shaders in Shader Graph by default. Drop to handwritten ShaderLab/HLSL only when SG can't express the math (e.g. compute, geometry, custom render textures).
## Volume framework (URP/HDRP)
```csharp
// Per-camera profile override
var volume = camera.GetComponent<Volume>();
if (volume.profile.TryGet<Bloom>(out var bloom)) {
bloom.intensity.value = 1.5f;
bloom.threshold.value = 0.9f;
}
```
Global volume + per-trigger local volumes; use weights for smooth transitions (e.g. entering interior).
## Renderer Features (URP)
Add custom passes (outline, fog, decal) by extending `ScriptableRendererFeature` + `ScriptableRenderPass`. Inject at `BeforeRenderingTransparents`, `AfterRenderingPostProcessing`, etc.
```csharp
public class OutlineFeature : ScriptableRendererFeature {
public Material outlineMat;
OutlinePass _pass;
public override void Create() => _pass = new OutlinePass(outlineMat);
public override void AddRenderPasses(ScriptableRenderer r, ref RenderingData d)
=> r.EnqueuePass(_pass);
}
```
## GPU Resident Drawer / BatchRendererGroup (Unity 6)
Big draw-call wins for static + lots of instances. Toggle GPU Resident Drawer in Quality settings; objects must be **Static** + share materials/meshes; auto-instances them on the GPU.
## Lighting
| Need | Use |
|---|---|
| Static scenes (level geo) | Baked Global Illumination (Progressive Lightmapper GPU) + Light Probes for dynamic objects |
| Outdoor day-night cycle | Mixed lighting (Shadowmask) + dynamic skybox |
| Stylized cel-shading | Custom Shader Graph with ramp texture |
| HDRP photoreal | Volumetric lights + Screen-Space GI + Adaptive Probe Volumes |
Reflection Probes: bake on key viewpoints; use box projection for indoors; pure realtime probes only for hero objects.
## Anti-patterns
| Anti-pattern | Fix |
|---|---|
| Different shader per material variant | Material Property Block via `Renderer.SetPropertyBlock` |
| Switching shaders at runtime | Pre-warm with shader variants collection asset |
| Per-frame material instantiation | `renderer.material` clones — use `sharedMaterial` for reads, `MaterialPropertyBlock` for per-instance overrides |
| Camera.Render() in Update | Use Render Texture + `Camera.targetTexture` once |
| Mixing pipelines (URP shader on Built-in) | Convert via `Edit > Render Pipeline > Universal > Convert Selected Materials` |
## Production checklist
- [ ] Pipeline asset set in Graphics + Quality settings
- [ ] Volume profiles configured for global + relevant local triggers
- [ ] Shader variants collection generated and preloaded for the build
- [ ] Static objects flagged Static; lighting baked
- [ ] Light Probes / Reflection Probes placed
- [ ] Frame Debugger inspected — no surprise opaque draws on UI
- [ ] HDRP-only: Adaptive Probe Volumes configured if static GI is critical
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.