Experiment · 2026
Chess analyzer
A chess analysis tool built so I could see my own games clearly — without borrowing someone else’s interface.
- Role
- Design and engineering
- Status
- building
- Year
- 2026
- Stack
- TypeScript, Next.js, Stockfish
Chess analyzer
I wanted to understand my games, not collect engine evaluations. The analyzer is a study instrument: lines, structure, and the moments I actually misjudged.
Problem
Most chess tools either shout numbers at you or hide the interesting decisions behind a wall of engine output.
Why
I learn faster when I can reconstruct a position than when I am told I was worse by 1.7.
What was difficult
Making engine analysis feel quiet. The evaluation is useful; the noise around it is not.
Decisions
Board first. Commentary second. Engine lines as a supporting voice, not the product.
Architecture
A browser-first board, a local engine worker, and a thin layer for storing games I want to revisit.
What exists
A working analyzer I use after sessions. The writing about it is the other half of the work.
Lessons
A tool becomes clearer when you decide who it is for. This one is for me, studying my own games.
Related
- vs-pod
A personal development environment I could actually live in — not another dashboard of widgets.