Tessera

How I trust code I never read: 1. Heavy up-front planning sessions, PRD, specs 2. Agent self-verification loops before delivery 3. Manual QA on critical paths only No surprises. No hallucinations. A few refinements, then ready.

Today I launched 'Become AI-Native', my new training inside Builder Methods Pro. 🚀 It's a build-along style program where we redesign our processes with AI. Build custom agent skills, automations, and AI training systems, using my favorite patterns and process designs.

New in flywrite.app: I added Cursor CLI integration so it knows your current file and selection (just like it does Claude Code and Codex CLI). Now I can use my favorite markdown editor (Flywrite) with my Cursor/Grok subscription.

Brian Casel @briancasel.com · 2w ago

Scenes from my new course, Become AI-Native: 👇

All videos for my next course, Become AI-Native, are recorded and in the can. Editing, uploading now... Launching later this week in Builder Methods Pro. (pssst: Raising price for new members after launch, now's a good time to grandfather in)

Brian Casel @briancasel.com · 2w ago

Released another free tool: Skill Builder. A skill for creating skills! Includes my favorite conventions and strategy for turning processes into skills for your agents. buildermethods.com/skill-builder

Skill Builder | Turn any repeatable process into an agent skill

Skill Builder is the agent skill that builds your agent skills. It interviews you about a repeatable process, then designs, writes, and verifies a well-structured skill — plain markdown and folders, p...

buildermethods.com

Brian Casel @briancasel.com · 2w ago

Here is agentcanon. Simple, lightweight symlink setup so that claude and others read from .agents/skills and agents .md. Also comes with a handy HTML manifest to catalog all your skills, their locations, spot duplicates etc. Install it with a prompt: github.com/buildermetho...

Brian Casel@briancasel.com · 3w ago

Using skills and claude.md/agents.md continues to be the most annoying "lock-in" thing. Claude more to blame here for not embracing 'agents' standard naming. Plenty of hacks and workaround strategies, of course. All annoying (and even harder to teach newcomers). 🙄

Working on my next course, Become AI-Native (for those new to AI-assisted workflows). Hardest part to teach: Harnesses and that rapidly changing landscape. Trying to make it practical & future-proof. ChatGPT (most popular brand name) not making it easier with their inept naming and product UX.

Writing and building my next course, 'Become AI-Native'. flywrite.app is the perfect tool for this type of work (writing-heavy project with some design work). Developing & iterating with Claude, hand-editing some parts...

Last year I created Agent OS to keep coding agents on the rails. This year, I stopped using it. Today's models do worse when you micromanage how they write code. They do better when you pour everything into planning and verification.

As much as I build and ship lots of stuff (public products and many internal tools)... The big trend for me has actually been stripping back and simplifying a lot. Agents and speed of iteration means a lot of heavy-handed tooling & process can fall away.

I've been extremely anti-meeting my whole career. My teams and I always worked 99% async. Now most of my day is in meetings planning big projects. I'm the only human at these meetings. Work output? Unprecedented on all metrics. No question. Enjoyment and flow? Open question.

How to make a Slack killer: Let users log in and find their workspace without requiring 8 attempts with different emails and workspace names.

The thing that disqualified non-technical founders (can't code) has been neutralized. What you have (deep knowledge of a real problem) can't be shortcut or replaced by AI. You're not behind. You're way ahead.

Brian Casel@briancasel.com · last mo.

I built it. This is mimeohq.com Email marketing you own. Your list. Your flows. Your emails. Just plug in a sender (Resend, Postmark, or SES). Manage it all in the UI or with agents. Opening soon. See demo video 👇

Mimeo: Own your email marketing stack

Email automation built agent-first. Your list, your flows, your sending. Hosted for a flat $79/mo, or yours forever for $499.

mimeohq.com

Domain purchased. Gonna build the thing I've talked myself out of building for 15+ years.

Zack Gilbert @zackgilbert.com · 4w ago

The difference between vibe coding and building: Vibe coding is prompting and hoping. Building is a methodical, predictable workflow. No surprises. Just your vision, made real. See my entire building process here. Free. https://buildermethods.com/workshop

Free Workshops | Builder Methods

Free ~60-minute workshops from Builder Methods — learn the method for building custom apps with AI, and how to make AI native to everything you do.

buildermethods.com

There are obviously a ton of amazing tools that have helped us build Eventually, but I want to call out one especially: @briancasel.com Builder Methods. The community, the videos, the workshops, but especially the tools that Brian shares have all been extremely crucial for us.

Zack Gilbert@zackgilbert.com · 4w ago

Welp. @eventuallyticketing.com is launching on producthunt.com today. We’ll see if anyone likes it or finds it interesting.

Brian Casel@briancasel.com · last mo.

Product built. Now writing copy to explain it. With flywrite.app of course.

Domain purchased. Gonna build the thing I've talked myself out of building for 15+ years.

Spruced up my Claude Code status bar today.

Sales slowed down for a little while there. Then I remembered I hadn't updated my email sequences and automations in a while. Turns out customers still read emails.

Brian Casel@briancasel.com · last mo.

First time in a while I'm optimistic about starting software products again. Seeing a new shape emerge: Familiar problems and tool categories solved in a way that gets accelerated by AI adoption instead of eaten by it. Requires rethinking product shape and biz model. Marketing still hard though.

Domain purchased. Gonna build the thing I've talked myself out of building for 15+ years.

Domain purchased. Gonna build the thing I've talked myself out of building for 15+ years.

If you feel like you have to review every line of code AI writes, the bottleneck isn't AI. It's micromanagement. Move that energy into planning and verification. Own the what and the proof. Let the agent own the how. That's what unlocks bigger builds.

New demo video for flywrite.app - Have a look!

Flywrite | The markdown writing app with an agent terminal

A markdown writing app with a terminal for Claude Code and other CLI agents to help you create your best work.

flywrite.app

Build Kits solve the blank page problem for builders. Pre-scoped specs, designs, and ready-made prompts for building common apps. Use them as starting points and customize your build. Members get access to the growing collection: https://buildermethods.com/kits

Build Kits | Ready-made starter kits for shipping AI apps

Build Kits are ready-to-build starter kits for shipping real apps, tools, and products with AI — each with pre-shaped specs, designs, prompts, and video guides.

buildermethods.com

Unpopular opinion: A domain expert who can't code is MORE qualified to build tools for their field than a pro developer is. If you know your problem space better than most, you're way ahead. Building is learnable.

"It's too expensive to build my own tool for that."...No longer applies. The busywork you assumed as just part of the job could be a weekend build (think of what could you replace that busywork with?)

In flywrite.app, your AI agents are one keystroke away. Launchers open a new terminal with something already running: a plain shell, Claude Code, or Codex — each on its own shortcut. Add launchers for your own commands, and remap any keyboard shortcut in settings.