How to Outline a Unity Shader Graph from an Effect Brief

Shader Graph outlines invent custom HLSL. Nodes only from the allowlist.
The matching generator is the Unity Shader Graph Node Outline from an Effect Brief (No Asset Claims) (Unity Shader Graph Node Outline From An Effect Brief No Asset Claims) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Lock Unity version and pipeline from Inputs
Outline a Unity Shader Graph node graph from an effect brief. Never claim Asset Store packs or invent undocumented nodes. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Effect brief: [Brief]
Unity version I lock (or UNKNOWN): [Unity]
Shader Graph package version I lock (or UNKNOWN): [SG]
Node allowlist (or DEFAULT built-in names only): [Nodes]
Target pipeline I lock (URP/HDRP/UNKNOWN): [Pipeline]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max nodes: [Max]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
List nodes only from the allowlist
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief nouns, Unity status, SG status, Nodes policy, Pipeline, Lang, Max. Forbidden: invented Asset Store claims, undocumented nodes.
- Effect map: inputs (color, time, UV) present or NOT IN INPUTS.
- Node outline: up to Max nodes. Each has name from Nodes/DEFAULT, purpose, input/output sockets named only if in Brief or Nodes.
- Wire notes: connections between listed nodes only.
- Refuse list: invented custom HLSL nodes, invented paid assets, invented URP features if Pipeline UNKNOWN.
- Diff notes: Banned/Never cuts.
- Version note: quote Unity and SG; if UNKNOWN write unknown.
- Compliance pass: Banned/Never hits. Node count vs Max. Gaps list of five. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Refuse Asset Store claims
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Shader Graph outline from Brief + Nodes only. Not HLSL authoring and not VFX Graph.
- Never claim Asset Store packs or invent undocumented nodes.
- Stay at or under Max nodes.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Leave package version unknown if blank
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (unity shader graph, no asset claims, shader graph node outline) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.