Aariv's web studio

Evening build and QA pass across the studio’s open-source tools and case-study portfolio. Spent the last four hours tightening DOM smoke test coverage across the public repositories on my GitHub, re-recording 1080p browser walkthroughs for four tools whose earlier captures had frame stalls, and re-verifying that every charity case-study screenshot on aariv.me/studio-site builds cleanly from build.mjs with zero broken links or layout shifts. Keeping the devlog window under the 10-hour cap makes it much easier to track what shipped in each session.

Overnight build session for the studio. The case-study site (aariv.me/studio-site, screenshot) doubled to four charity sites with fresh live screenshots - each one a real site the studio shipped and maintains. Also built out the studio’s mission arm: a webOS with 10 working apps (terminal, files, synth, system monitor), a devlog timer that makes the 10-hour cap visible, a verified microgame collection, and a Slack bot now awaiting workspace approval. All vanilla, all tested in a real browser, all under my direction with agents doing the typing. The studio method is holding: spec it, build it, verify it, ship it.

I’m adhering to my promise to improve my devlog pacing near the 10-hour limit. Over the last 9.5 hours I have been focusing mostly on creating detailed markdown specs and reviews to keep OpenCode, Claude Code and Antigravity on track with their latest builds. The majority of this has been improving the layout of charity websites, playing around with brand ideas for fake brands, creating small utilities for contests and Lincoln Douglas debates to put onto my public GitHub, and testing my recent portfolio updates in browsers such as Waterfox. Creating clear specs and carefully reviewing each diff is making it a clean and organized process.

Big catch-up post for my studio work. Since late August I have been running my web-design studio out of one workspace: I direct AI coding agents (OpenCode, Claude Code, Antigravity) that do the typing while I plan the sites, review every change and test the results. In this window the studio shipped charity websites, a batch of small contest tools (public copies on my GitHub), updates to my portfolio at aariv.me, and the planning and review docs that keep the pipeline honest. Most of my logged time is Markdown for a reason: directing agents well is mostly writing precise specs and reading their output carefully. Next up: a tighter devlog cadence instead of one giant backfill. Screenshot: my portfolio, aariv.me.