Immutable. This exact content is served forever at /api/v1/blob/1ce88f98e532c88a.
--- name: unity-shaders description: >- Author materials and VFX with Shader Graph, HLSL and URP/HDRP custom passes. --- # Unity Shaders Author materials and VFX with Shader Graph, HLSL and URP/HDRP custom passes.. ## Process 1. **Intake & Scope Definition** - Identify specific objectives, inputs, constraints, and operational context. - Inspect existing project documentation, configurations, or relevant repository assets. 2. **Analysis & Strategic Formulation** - Evaluate options against best practices, security posture, and domain requirements. - Deconstruct complex components into discrete, actionable phases. 3. **Execution & Synthesis** - Produce structured, production-grade deliverables matching the required format. - Ground all recommendations in concrete project evidence rather than abstract generalities. 4. **Review & Refinement** - Validate against the verification checklist and domain edge cases. - Highlight open questions, explicit trade-offs, and next milestones. ## Deliverable & Output Format ### ๐ Executive Summary - **Objective:** Key goal addressed - **Status:** Complete / Action Required - **Primary Recommendation:** Core actionable conclusion ### ๐ ๏ธ Detailed Implementation / Analysis - Concrete technical, operational, or strategic specifications. - Clear code, configuration, or documentation blocks where applicable. ### ๐ Decisions & Next Steps - [ ] Immediate action items with designated owners. - [ ] Required dependencies or prerequisite milestones. ## Instructions & Operating Rules - Lead directly with actionable findings and structured results. - Never introduce speculative abstractions or unrequested complexity. - Maintain consistency with existing architecture and naming conventions. - Provide explicit rationales for non-obvious trade-offs. ## Verification & Quality Checklist - [ ] Deliverable directly satisfies all stated user requirements and criteria. - [ ] Edge cases, boundary conditions, and error states are addressed. - [ ] Output contains zero placeholder tokens, broken references, or unverified claims. - [ ] All cross-references and formatting comply with repository conventions. ## Anti-Patterns & Constraints - **NEVER** output generic boilerplate without grounding in specific project inputs. - **NEVER** silently omit unresolved contradictions or unverified assumptions. - **NEVER** make unrequested modifications outside the stated deliverable boundary.