The arc
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 — 2026
Before the matrix
Eight years of client work and open source in Japan, twenty-plus projects. One of them, a Vue admin template called lux-ui, earned 683 stars and then went quiet — the clearest lesson available about what happens when momentum lapses. Everything after this is an answer to that.
2026-05
Loose tools, no plan
The first two repositories were odd jobs: an icon generator, a place to study design systems. Nothing about them says “matrix” yet — they are here because the arc has to start honestly.
- yIcon
- yGraphify
2026-06
Foundations before products
A month spent on things nobody sees: the Next.js starter, the shared API layer, and yBlocks — the block library that later assembles every screen. Building the floor first is the only reason a dozen projects could move in parallel later.
- yAssets
- yBlocks
- yPicker
- ytools
- yApis
- yTemplate
2026-07
An instrument, and a stage
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 matrix stopped only producing and started being able to talk about what it produces.
- yPhotos
- yLookbook
- yReel
- yMotion
- yAnimationPlayground
Now
18 projects, in parallel
One developer and an AI team, working across 18 repositories at once — foundations, products, pipelines, and the tooling that keeps the whole thing observable. The long game is a one-person company whose products speak for themselves.
Contact
The fastest ways to reach me are X (@catforestai) and GitHub (@maosensen).