nuke-creative
Nuke Creative
The family doctrine pointed at a different failure (map: references/family-map.md — creative picks the direction; nuke-design carries the render-side build craft). Elsewhere cheap generation fails toward bugs; on UI it fails toward the default: the same centered hero, the same gradient, the same three-card grid every model produces when nobody forces divergence. So the protocol forces it — commit to a direction before code, ban the defaults by name, and put a fresh critic with a screenshot between the code and the word "done". Rendered output is the material under judgment; code review alone judges the wrong artifact.
Modes
Tier vocabulary and platform mechanics: references/model-tiers.md.
| light (default) | full | |
|---|---|---|
| Shape | in-session discipline — no preflight, no run_dir, like nuke-lean | preflighted ceremony with concept wave |
| Direction | the session writes the brief + ≥3 directions itself | 3 concept agents (session), assigned stances, one artifact each |
| Judge | the session picks, reason named in the brief | 1 judge (top) scores against the brief |
| Implementer | the session | worker+, loaded with the winning concept |
| Critic | 1 fresh agent (session) | fresh critic (top) |
| Critique cycles | cap 2 | cap 3 |
| Typical trigger | any UI task where look matters | "awwwards", "best you can do", flagship pages |
plan (full only) → run preflight, print the plan block, STOP. --ask → pause at the plan for confirmation; default is no gate — the plan prints and the run starts (references/preflight.md).