higgsfield-scene-engine
Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence generates cleanly but lands flat and nobody can say why; when shots look good individually but the run of them does not build; or when the user asks 'is this scene working', 'what's weak here', or 'why doesn't this land'. Upstream of prompting — it decides WHICH shots deserve the credits, not how to write them. Pairs with higgsfield-character-design (who the characters are) and higgsfield-shotlist-director (turning the settled scene into shots).
- 分类
- 通用
- 版本
- v1.0.0
- 作者
- 弈韬(@ra1nzzz)
- 下载
- 0
- 收藏
- 0
- 发布
- 2026-08-28
- 更新
- 2026-08-28
- TRACE 评分
- 3.2 / 5
内容概览
[DEMO — Tigran (tig-scene-engine), 2026-06-26] [UNPROVEN HERE] These definitions are bespoke and deliberately not the textbook ones. Apply them as written; do not substitute standard screenwriting glosses, which are looser and will pass scenes this engine fails. Why a prompter carries this. Every shot costs credits and iterations. A structurally dead scene generates just as cleanly as a live one — the model has no opinion about whether a beat earns its place — so the failure surfaces only after the footage exists and the cut does not build. This skill is the cheapest pass in the repo: it runs on text, before any generation, and its whole job is to stop you paying to render a scene that cannot work. It decides which shots deserve the spend. higgsfield-shotlist-director turns the settled scene into shots; higgsfield-acting writes the performance inside them. --- The single, unchanging thin…