Tidemason
I build small tools, AI-assisted experiments, and practical personal systems.
Tidemason is my public home base for current projects, retired ideas, and notes from learning how to build, ship, validate, and archive small products in public.
Silas Lee · 文西, a solo maker learning to build and validate small products in public.
Small tools, AI-assisted experiments, public utilities, and retired product attempts.
To keep the trail readable: what is alive, what failed, and what each project taught.
Current Focus
World Cup 2026 match times in your own timezone, with calendar downloads.
A small web tool for checking World Cup 2026 match times locally and exporting games to a calendar.
Lesson: Specific public utilities are easier to explain than broad productivity systems.
Local-first prospect notes and follow-ups for manual outreach work.
A Chrome extension for saving manual outreach context, follow-up cards, and local templates without scraping or background tracking.
Lesson: Some useful tools should stay close to the user's existing workflow instead of trying to replace it.
Small Apple Apps
A focused expiry tracker for skincare and beauty products.
A compact utility can be more honest than a product that pretends to own an entire category.
App Store
A small decision tool for reviewing recurring subscriptions.
Everyday decision tools need a very sharp repeat-use moment to keep earning attention.
App StoreIndex at a glance
Current projects I want people to see first.
Match Time Calendar, Signal Notebook
Small tools that are still live.
OpenGlow, Kept
Things I tried to understand the shape of a problem.
Junxi / Mycelial Breath, NoticeFlow, ReplyCopilot
Stopped work, kept for what it taught.
csv-debugger, offlineaudit-csv
Branches that never became complete products.
audit-csv
Launch notes, product notes, and postmortems from building in public.
Signal Notebook is live in the Chrome Web Store, Why I'm archiving old experiments
Notes
About
I am Silas Lee · 文西. This site keeps track of what is alive, what has been archived, and what I learned from building small software in public.
The point is not to make every project look successful. The point is to keep the trail readable enough that future projects can compound from it.