How it works
A straight-line explanation before you read any syllabus PDFs — built for busy engineers and designers in Japan.
Before — scattered tabs
- Profiler captures live only on one laptop
- README files read like marketing blurbs
- Designers and engineers debate spacing without a shared token sheet
After — shared receipts
- Weekly capture filenames everyone can grep
- README sections for cuts, risks, and tester scripts
- Spatial UI tokens mirrored in prefabs
Six beats we repeat
- Read the non-goals section first — it saves arguments later.
- Freeze scope on paper before opening engine tools.
- Ship a rough playable before polishing shaders.
- Upload captures even when embarrassed — mentors need context.
- Publish your cut list to the cohort channel.
- Archive the repo with a tag that matches the syllabus week.
Need the studio workflow diagram?
Open Spatial Computing Studio