Home/Blog/How to Sketch a Blender Geometry Nodes Tree from an Effect Brief
Blog

How to Sketch a Blender Geometry Nodes Tree from an Effect Brief

P
promptstudio
How to Sketch a Blender Geometry Nodes Tree from an Effect Brief

Node trees invent asset packs. Nodes only from the allowlist.

The matching generator is the Blender Geometry Nodes Tree from an Effect Brief (No Asset Claims) (Blender Geometry Nodes Tree 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 the Blender version

Sketch a Blender Geometry Nodes tree from an effect brief. Never invent node names beyond Blender's known set you are allowed, asset packs, or render benchmarks. 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]
Blender version I lock (or UNKNOWN): [Version]
Node names I allow (comma list or CORE for distribute/join/set-position/noise only): [Nodes]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max node groups: [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.

Build groups from allowed nodes

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:

  1. Honesty ledger: Brief nouns, Version, Nodes policy, Lang, Max. Forbidden: asset pack claims, celebrity stills, invented FPS.
  2. Effect map: inputs/outputs from Brief.
  3. Tree sketch: up to Max groups. List nodes only from Nodes/CORE. Socket names. No fake screenshots.
  4. Socket list: each group inputs/outputs.
  5. Refuse list: invented asset URLs, celebrity likeness, render farm quotes.
  6. Diff notes: Banned/Never cuts.
  7. Version note: UNKNOWN if blank.
  8. Compliance pass: Banned/Never hits. Group 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 celebrity stills and packs

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:

  • Geometry Nodes from Brief only. Not DaVinci and not Unreal.
  • Never invent asset packs, celebrities, or FPS claims.
  • Honor Max groups.
  • 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 polycount 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 (blender geometry nodes, no asset claims, geometry nodes tree) 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.