Cooked with Claude

The business leader’s playbook for getting things done in the AI age

I am not a developer. My background is in consulting, building companies, and advising startups.

A few months ago, I discovered Claude Code. Since then I’ve started using Claude not as an assistant but as an execution engine — and the shift has been profound.

This site documents what I’ve built and what I’ve learned. Most Claude Code content online is written by developers for developers. This site is for business leaders — founders, operators, senior professionals — who want things done.

Articles

Why this site

How it started, how it’s going

The difference between an assistant who knows and an assistant who can

Cheap to do, expensive to carry

The tasks worth automating first

Skills are the new apps

Your mind is for having ideas, not holding them

Remove yourself from the loop

“Do it for me”

The first automation I built with Claude Code

From idea to live site in one session

The company that runs itself

Off the record

Curiosity and a mentor

The 30-second audit

What done actually means

When to trust the AI, when to check the source

Your capture system should work from your phone

A few commands that changed how I work

The inbox is not where things get done

When your tools talk to each other

The system that checks itself

One browser for the AI

The daily login health check

Your personal OS needs a status page

Your phone is now an API endpoint

When the API says no, automate the UI

The two-minute task you should automate anyway

The remote control of Claude Code

A different kind of Claude Code power user

How One Automation Killed a Daily Manual Task

Your command vocabulary

Your AI team is burning money while it sleeps

Claude Code for business owners

How to use Claude Code if you’re not a developer

Claude Code vs ChatGPT for business

My morning brief

How I automated my EA briefings with Claude Code

Orchestration is the new programming

The Silent Failure Problem

From user to fleet operator — the four phases of working with AI

What you’re actually paying for at a coworking space

The Tool Priority Hierarchy

Context engineering, not prompt engineering

The CLAUDE.md setup that makes everything work

Setting up Playwright and why it matters

Hooking Up Claude Code with Telegram

Your content team is now an org chart

Setting up Google Workspace with Claude Code

Use Google Antigravity to set up Claude Code on your machine

Using Claude as a Thinking Partner

Inbox Anywhere

Setting up Obsidian and why

Your project needs a boot sequence

The Idea Bank: A Content Capture System That Runs Itself

Advice Is Not Action

Setting up your first skill

How I Built a Personal Operating System with Flat Files

The One-Word Trigger

Building an editorial calendar that runs itself

The Difference Between Delegation and Abdication

The Second Brain Actually Works Now

How to Run Your Weekly Review with AI

The Memo You Never Wrote

How to Give Claude Code Memory Across Sessions

How I Query My Product Analytics Without Opening a Dashboard

Institutional Memory Is a Skill

Running separate AI contexts for each client

How I use Claude Code to prep for important meetings

How we fixed a Google Business Profile with Playwright — without touching the API

How I track birthdays and follow-ups without a CRM

From screenshots to board report in one session

Your morning automation stack

The Automation You Should Have Retired Six Months Ago

The 15-Minute Invoice

The AI Legal First Pass

The Bot That Talks Back

What 155 sessions taught me about how I actually work