Timeline
How a pile of scattered projects became a matrix.
Not a résumé — the order things were built in, and why that order is the point.
2018 — Apr 2026
Before the matrix
Eight years, nearly twenty projects — frontend, backend, cloud, UI, AI, all of it. Breadth was there; each line still ran on its own, not yet converged into one.
2026-05
Going all-in on Claude Code, the first leap in output
Knowledge and experience finally connected, with nothing left blocking them. A decade of what looked like scattered accumulation started compounding, all at once.
- yIcon
2026-06
Foundations before products
A month spent entirely on things nobody sees: the Next.js starter, the UI foundation layer, the shared API layer, and yBlocks — which later assembled every screen. Building the floor first is the only reason a dozen projects could move in parallel afterward. Fable 5 appeared briefly that month and was gone again; at the time it read as an episode, nothing more.
- yAssets
- yBlocks
- yPicker
- ytools
- yApis
- yTemplate
2026-07
The second leap, a central brain and a public stage
Fable 5 returned globally on 1 July, and the second leap in output dates from that day. The same month yPulse started watching all of it — activity, releases, changelogs, collected every day — which made the matrix measurable instead of merely busy. Days later yStage went up so it could also be seen. Measurement and display arrived in that order on purpose.
- yPulse
- yStage
- yGenshinColor
- yClip
- yDesktopTemplate
2026-08
Learning to show the work
Storyboards as code, a promo-film studio, the photography archive, and a lab where whole design languages compete before one graduates. The two months after the leap were the steepest stretch yet: the rulebook, the foundations and the system landed one after another. The matrix stopped only producing and started being able to talk about what it produces.
- yPhotos
- yLookbook
- yReel
- yMotion
- yAnimationPlayground
2026-09
Collections, industry templates and native apps
Fable 5.1 arrived on 1 September, when daily token use first passed 880 million. Then yCollections began recording what was saved and used, yCrmTemplate turned existing design work into a complete CRM template, and yListen brought the matrix to native macOS listening and translation. Alongside them, yBlocks developed card families and chart standards, yLookbook and the animation lab expanded their interactive work, and yPulse added release records, distribution drafts and traffic tracking. At the end of the month, yAtlas graduated from yLookbook into its own site for mathematical films and interactive experiments.
- yCollections
- yCrmTemplate
- yListen
- yAtlas
2026-10
Experiments become applications and shared engines
yIsobath takes yLookbook’s disk visualization to the desktop, surveying real disks and shipping installers. yPlotter brings the repeated implementations behind Drafting Sheets into one engine. yAgentKit collects tasks, approvals and artifact previews into a reusable agent workspace, with an experimental local Codex bridge and read-only code reviews.
- yIsobath
- yPlotter
- yDiorama
- yAgentKit
Now
25 projects, in parallel
One developer and an AI team, moving 25 repositories forward at once — foundations, products, pipelines.
Contact
The fastest ways to reach me are X (@catforestai) and GitHub (@maosensen).