Sample: Running a studio on Claude, the actual workflow

1 min read

This is a sample post for testing the design. Delete it before launch.

People ask what “running a studio on AI” means day to day. It’s less magic than it sounds. Mostly it’s a folder of prompts, a few scripts and a habit of writing things down.

The morning script

Every client repo has the same entry point. This is the whole thing:

#!/usr/bin/env bash
set -euo pipefail
git pull --rebase
npm ci
npm run test -- --reporter=dot
claude -p "Read TODO.md and the last 5 commits. List what changed, what's blocked, and the next three tasks for today, in that order. Keep it short." > standup.md

And the tiny helper that turns a client email into a ticket:

export function toTicket(email) {
  const title = email.subject.replace(/^(re|fwd):\s*/i, '').trim();
  return { title, body: email.text, labels: ['client'], estimate: null };
}

Placeholder grid image, wide

A wide image breaks out of the text column.

Common questions

Do clients know you use AI? Yes. It’s in the proposal. Nobody has pushed back; they care that it ships and that a human is accountable.

What does it cost per month? About $400 across all tools for four people. Less than one day of a contractor.

Next week I’ll share the prompt folder itself.