01
Shared concept
The umbrella idea stays fixed so route differences are legible instead of accidental.
Shared brief. Fixed contract. Visible delta.
Crest Alpha
One prompt enters. Multiple routes answer. Compare craft, motion, hierarchy, and restraint without the noise.
Routes
12
Contract
1
Signal
Clear
Bias
Low
Benchmark frame
One brief.
Strict packaging.
The catalog is only useful if the inputs stay stable. Each route ships against the same brief and the same output contract.
02
Route ownership
Each route solves one problem shape. No cross-route edits. No hidden cleanup outside scope.
03
Visible finish
Compare structure, taste, responsiveness, and motion in the artifact itself, not in an after-the-fact explanation.
Route matrix
Twelve ways to answer
the same ask.
Different routes expose different strengths. Some reward interaction design. Others stress systems depth, pace, or explanatory clarity.
Web
01
Single-file brand or editorial experience.
Snake
02
Arcade feel, feedback loops, tuning discipline.
Dashboard
03
Density, hierarchy, and operator readability.
Maproom
04
Layering, annotation, and spatial explanation.
Physics
05
Interaction credibility and material feel.
CMS
06
Workflow realism, utility, and control layout.
Signal read
Read the artifact,
not the excuse.
Strong routes make decisions early. Weak routes compensate with explanation. The catalog is built to expose that difference quickly.
Fast heuristics
Three checks that matter
Does the first screen establish intent instantly?
0-5 sec
Does interaction add meaning instead of decoration?
scroll
Does the finish hold together on mobile?
resize
Calibration note
What usually separates the best runs
Not raw complexity. Usually it is tighter hierarchy, sharper copy, better motion restraint, and a cleaner sense of where to spend detail.
The best route outputs feel inevitable. Every part looks intentional. Nothing reads like filler.
Protocol
Prompt. Build.
Package. Compare.
The workflow is simple by design. Complexity belongs inside the route, not in the evaluation setup.
Step 01
Prompt
Use one shared brief and route-specific constraints only where required by the contract.
Step 02
Build
Let each route solve its own shape: game, website, dashboard, map, or tool surface.
Step 03
Package
Emit only the required files so the results stay legible and comparable.
Step 04
Compare
Review the artifacts directly. Score clarity, craft, finish, responsiveness, and control.
Current route
Open the `web` benchmark and judge the work on the page.
This route is tuned for immersive single-file websites with a clear point of view.