Pandai · 03 / 12

Applications. What to actually USE a coding agent for.

Eight worked examples. Real prompts. What you see in your browser. What login you need. What the agent responds back.

The eight examples

What you can ship this week.

01 · Documents

Pitch deck

Google Slides via Chrome. 5 slides, your brand colors, ready to share.

02 · Documents

Brand intro video

Remotion project scaffolded. 60-sec mp4 rendered. Ready to upload.

03 · Email

Bill summary

90 days of receipts → CSV. Recurring subscriptions surfaced.

04 · Spreadsheets

Anomaly detection

Q3 daily revenue. 3 outliers found. Causes cross-referenced from Gmail.

05 · Spreadsheets

P&L generator

Stripe + Midtrans + payroll → Income statement. Formatted, ready for the board.

06 · Spreadsheets

Excel cleanup

Formulas typed, conditional formatting applied, totals computed.

07 · Diagnostics

Website audit

Lighthouse run. 4 scores. Top fixes ranked by estimated savings.

08 · Extraction

KTP OCR

Indonesian ID photo → structured JSON. NIK on clipboard.

You'll need a coding agent

The Chrome session is the moat.

Your real browser is signed into Vercel, Twilio, your bank, your email, your Gmail, your Sheets. The agent that shares your Chrome session can do anything you're already logged into. The one that spawns its own can't.

defaultClaude Codeshares your real Chrome session

also-goodPi"this one is yours"

maybeCodexuntested for chrome sessions

avoidCursorspawns its own browser

avoidClinespawns its own browser

Your turn

Pick one. Ship it. Real artifact, real user.

Pattern: anything you've manually done 3+ times this month is a candidate. Spend an hour. Use a coding agent. Ship the artifact.

← Back: 02/12 Under the hood. All modules →