claude
5f5d3d7c99
CI / check (pull_request) Successful in 6s
Two real-capture terminal screenshots for the "Getting the AI Out of the Browser" blog draft (post #17116): - m4-agent.png: a real `claude -p` invocation on the demo tasks-app asking "what does this project do?". The response correctly names tasks.py, cli.py, and the add/list/done CLI commands, proving the agent is wired to real files. - m4-diff.png: real `git diff` after adding a `delete` command that touches both cli.py and tasks.py. Shows green additions in both files, the two-file change that copy-paste used to fumble. Rendered locally via headless Chrome (Claude Design MCP was offline; local file:// URL substitutes cleanly). Cropped tight to the terminal panels. Uploaded to WP as media 17178 (agent) and 17179 (diff); embedded in draft #17116 with captions; post scheduled for Thu 2026-07-09 10:00 America/New_York. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
Blog posts (jpaul.me)
Drafts of blog posts for jpaul.me that promote and add value around The Workflow course. This folder is not course content; it lives here only so the drafts are version-controlled alongside the material they describe. Pull it out before any public GitHub mirror push if you don't want the drafts shipped publicly.
Conventions
- One Markdown file per post, numbered in intended publish order:
NN-slug.md. - Each file opens with a metadata block (suggested title, slug, meta description, tags) for easy paste into WordPress; delete it before publishing or keep it as notes.
- Screenshots are left as
[insert a screenshot referencing XYZ here]placeholders for Justin to fill before publishing. - Voice: conversational, first-person, value-first. Course link is a soft CTA, not the whole point; each post should stand on its own for a reader who never takes the course.
Publishing cadence & manifest
Structure: announcement + getting-started, then a weekly series. Hybrid granularity: one post per module for the durable core (Units 1–2), one post per unit for the faster-moving back half (Units 3–5), plus a capstone finale. 17 posts total.
| # | File | Covers | Working title |
|---|---|---|---|
| 01 | 01-announcing-the-workflow.md |
Announcement / thesis | Your AI Already Writes Good Code. That's Not Your Problem. |
| 02 | 02-getting-started-the-copy-paste-problem.md |
Module 1 + setup | The Copy-Paste Problem (and How to Actually Get Started) |
| 03 | 03-version-control-safety-net.md |
Module 2 | Git Is Undo for the AI (and Memory It Can Read Back) |
| 04 | 04-version-control-for-words.md |
Module 3 | Version Control Isn't Just for Code: Start With Your Words |
| 05 | 05-getting-the-ai-out-of-the-browser.md |
Module 4 | Let the AI Edit Your Files (Yes, Really: Here's Why It's Safe) |
| 06 | 06-commit-the-ai-config.md |
Module 5 | Commit the AI's Config, Not Just the Code |
| 07 | 07-branches-sandboxes.md |
Module 6 | Let the AI Try Something Reckless, on a Branch |
| 08 | 08-worktrees-parallel-agents.md |
Module 7 | Stop Making Your Agents Take Turns: Git Worktrees |
| 09 | 09-remotes-and-hosting.md |
Module 8 | Your Repo Lives on One Disk. That's One Spilled Coffee From Gone. |
| 10 | 10-issues-task-layer.md |
Module 9 | Who Picks This Up? Writing Issues for a Team of Humans and Agents |
| 11 | 11-reviewing-code-you-didnt-write.md |
Module 10 | The AI's Code Looks Right. That's the Problem. |
| 12 | 12-collaboration-humans-and-agents.md |
Module 11 | Half Your Teammates Aren't Human (and the Loop Doesn't Care) |
| 13 | 13-revert-reset-recovery.md |
Module 12 | Your AI Just Force-Pushed Over a Day of Work. Now What? |
| 14 | 14-unit3-automate-checking-shipping.md |
Unit 3 (M13–19) | AI Made Writing Code Cheap. Now Automate the Catching. |
| 15 | 15-unit4-extend-the-ai.md |
Unit 4 (M20–23) | Giving the AI Hands: Extending It Into Your Real Systems |
| 16 | 16-unit5-ai-in-the-loop.md |
Unit 5 (M24–27) | Letting the AI Off the Leash (Without Getting Bitten) |
| 17 | 17-capstone-the-full-loop.md |
Capstone | The Full Loop: One Feature, End to End |
Each file's top-of-file HTML comment holds the suggested title, slug, meta description, and tags for WordPress. Titles above are starting points; every post also carries an alt title in its metadata block.
Before publishing: checklist
[COURSE LINK]placeholders filled with the course URLhttps://git.jpaul.io/justin/ai-workflow-course. At public launch: (a) if the GitHub mirror becomes the public home, swap these to the mirror URL; (b) inline cross-post references ("announcement post", "last post", "course lab") currently all point at the course home; repoint them to the specific jpaul.me post URLs (or wiki module pages) once those exist.- Fill every
[insert a screenshot referencing XYZ here]placeholder with a real image. - Decide whether to keep or strip the top-of-file metadata comment block.