Creative, game & research workflows

Choose Creative, Games, or Research. Each workflow leaves editable sources and an output you can inspect.

1. BriefTask + constraints
2. BuildEditable source
3. RunOpen or play it
4. ReviewCompare the result

Creative work

Record requirements, references, candidate directions, and feedback in CREATIVE-BRIEF.md. Compare layouts, camera views, or short previews before selecting a direction.

Work	Keep	Finish with	Prompt example
Browser design	source, assets, tokens	viewport screenshots and interaction	“Implement the selected card layout; capture desktop and mobile states.”
Blender/game asset	.blend, scripts, textures, export settings	render, reopened scene, destination import	“Make the selected prop; render it and import the GLB into the project.”
Motion/video	composition, source audio, editable timeline	playback, frames, audible output, reopened project	“Animate the chosen transition; export a preview and reopen the timeline.”

Use creative workflows for templates, provenance, and evidence boundaries.

Games

Use router to find the engine’s build and test commands:

Use router. Own the dash mechanic and its existing tests. Run the project’s
documented narrow build, then play the dash path in its target runtime. Return
the changed files, test command, capture path, and any untested device boundary.

Run existing deterministic tests, then exercise the actual input-to-outcome path in the engine, browser, or emulator. A valid GLB does not establish material, scale, animation, timing, audio, input, or gameplay use. See game development.

Research

Use primary sources for drift-prone facts and label direct evidence separately from inference.

Result	Establishes
Numerical/CAS result	Its stated inputs, assumptions, software, and precision
Literature source	The source’s claim, scope, and status
Lean build	The checked statement elaborates in that environment
Formal certification	The additional reviewed conditions for the repository claim

Use math routes and scientific review. A bounded computation or compiled formalization does not establish a different theorem.

A concrete research brief

Use researcher. Does current official API documentation support setting X in
client Y? Search official documentation only. Return the direct URL, retrieval
date, supported-client wording, and whether the conclusion is evidence or
inference. Do not edit files. Write excerpts to /tmp/api-setting-research.md.

The parent can use that artifact to decide whether local client-version verification or an implementation change is justified.