opinions on what's changing. how-to from real builds. notes on ai, craft, indie tech.
⦿ featured
Shipping UI with Claude Chat, Design, and Code falls apart at the handoffs. Here's the seven-fix loop that replaced my old vending-machine workflow.
claude.ai, claude code, the ide extension, desktop + mcp, computer use, the api — same model, different wrappers. when to use each, and where each one breaks.
claude skills dropped in october 2025 and the ecosystem is already useful. here's which ones — official and community — are actually worth installing.
Why I had Claude build this site from scratch instead of using Framer or Lovable — the admin backend is the real product, and hosted builders quietly own the part that matters.
No single tool tells you the whole truth about web performance. Here's the working set — pagespeed, webpagetest, crux, RUM — and what each is actually good for.
Beyond the OpenAI and Anthropic axis, a quieter wave of AI startups is doing the most interesting work. Eight names worth knowing — what they make, why it matters, and the pattern they share.
Every model gets replaced. Every IDE gets replaced. The system you build around them is the only thing that survives the next release. Here's what mine looks like.
Why I built the cursor reveal on ctrlsze.studio's homepage, how I worked out the interaction in plain English before writing any code, and what makes a small effect like this earn its keep.
What I'd tell myself on day one — about emails, domains, business registration, free tiers, legal pages, and the AI workflow that would have saved me months.
A practical playbook for shipping a studio site with a product subdomain using Next.js, Vercel, Cloudflare, and Claude. Real timelines, real prompts, no fluff.