I don't edit
my videos.
Claude does.
Get the exact workflow and system prompts I use with Claude Code. Free, right now.
The same workflow launched Rawk in 96 hours.
RawEdited by Claude
A muted clip about building Rawk. Compare the raw recording with Claude's edit, including captions and graphics. The workflow below includes the build details.
Video couldn't load. The workflow is still available.
The loop
How I plan, split the work and review what the agents build.
The system prompts
The project contract, orchestrator rules and worker task card.
The receipts
The prompts I typed and the git log behind the Rawk launch.
Here it is.
Who built what
- 3D modelBuilt and printed on my 3D printer, handled by GPT-6 Astra.
- iOS appCoding and all the interfaces: Codex. On TestFlight; App Store review still pending.
- WebsiteLanding pages, checkout, sales funnel and the visual creatives: Claude Code and Codex together.
- This reelEdited by Claude Code.
The loop
- One orchestrator plans.GPT-6 Astra writes the plan, splits the work, and reviews every result before it ships.
- Each worker owns one folder.The web worker owns
web/, the iOS worker ownsapp-ios/. Two agents never edit the same files. - Nothing ships without proof.Build, lint and tests pass, then real screenshots on desktop and phone width. “Should work” isn’t done.
- Every release gets a receipt.Each build commit is followed by a “Record verified … release” commit with the proof attached.
- I keep the keys.Passwords, money, ad budgets and anything sent to a real person wait for my OK.
The system prompts
Copy, swap the <brackets> for your project, and drop them in your repo.
1 · Project contract (AGENTS.md)Every agent reads this first. The single source of truth for who owns what and what “done” means.
# <product> implementation contract <product> is <one line: what it is and who it's for>. Follow the global rules file. ## Ownership - web worker owns web/ only. - iOS worker owns app-ios/ only. - root (orchestrator) owns creative/, ops/, account setup, credentials, integrations, deployment and every customer-facing claim. - reviewer owns docs/review/ only and may read all non-sensitive source. Workers are not alone. Preserve others' changes. No credentials, customer data, external messages, paid generation, account changes or deployment by workers. ## Product and offer - <exact prices, shipping and refund policy. Every worker copies from here.> - <what the product does, step by step> - <platform target>, subject to real build/device acceptance. - Never promise what the platform can't do. No unsupported "first/only" claims. ## Design <brand spelling, fonts, colors, surfaces, hero, section order>. No fabricated reviews, ratings or customer counts. ## Implementation Separate app IDs, data and deployment for this product. No live payments or ads until the prototype, commerce and creative gates pass. ## Verification Web: build, lint and meaningful tests, plus a real browser review on mobile and desktop. iOS: compile and core tests; always say which proof came from a simulator and which from a real device. Never mark a configured integration as live or a mockup as product proof. Secrets and .env files are never committed.
2 · Orchestrator rules (global)Lives in the global rules file, so every session starts with it.
## How we work - The orchestrator plans, briefs workers, reviews, integrates and verifies. Workers execute bounded tasks with explicit files and a verification command. - Run workers in parallel only when each one owns a separate set of files. Never let two agents edit the same files. - Keep credentials, customer data, money/security decisions and external actions on the orchestrator. - Never send an email, DM or message to a real person without my approval of that exact message. ## Before writing code - State assumptions. If something is unclear, ask about that part and keep doing the work that isn't blocked. - Minimum code that solves the problem. Reuse what the codebase already has. No features nobody asked for. - Touch only what the task needs. Every changed line should trace back to the request. ## Before saying "done" - Set testable success criteria first. - Verify with evidence: the project's build && test && lint, plus real screenshots for anything visual. - Never report done on "should" or "probably". Evidence or it didn't happen.
3 · Worker task cardWhat the orchestrator hands each worker. Small, owned, provable.
Task: <one sentence> You own: <exact files or folder>. Don't edit anything else; other workers are active. Context: read AGENTS.md first. Done when: <verification command> passes. Paste its real output. Don't: touch credentials, deploy, send anything, or change files another worker owns.
The prompts I actually typed
No magic words. Plain direction to the orchestrator; the rules files above do the rest.
The iOS appOct 7 · 12:25 AM
“using the resources and what we have already built from [my other app]. i need to build the Rawk app for ios now. heres how i want rawk to work. physical nfc device. open app, pair to rawk. select apps with a quick selector. … the same rounded, liquid glass and font design. the only thing is, we will be in dark mode to start, we are going for the dark aesthetic for Rawk. the first screen the user will see is the pair your Rawk screen, a floating Rawk in the middle that is slowly spinning … liquid glass button at the bottom "Pair your Rawk."”
The brandOct 7 · 12:46 AM
“go with angular facet, create our brand identity and brand design document”
App StoreOct 7 · 4:49 PM
“upload to app store publish it, i want to launch the app, take care of the demonstration videos and everything”
After a rejectionOct 12 · 8:16 AM
“logged in, figure out what got rejected, fix it, make sure nothing else gets rejected. and submit”
The receipts
From the repo’s git log (times ET). The 3D model ran alongside the code; the final shape is version 24.
Oct 6 to Oct 7, seven commitsBrand and storefront to TestFlight
- Oct 6 · 8:12 PMBrand, storefront and iOS app foundation
- Oct 6 · 9:03 PMFacebook Page created
- Oct 7 · 1:24 AMDark storefront and bundle pricing
- Oct 7 · 1:47 AMiOS focus flow
- Oct 7 · 3:30 PMSigned NFC tags and encoder app
- Oct 7 · 6:08 PMApp Store draft uploaded
- Oct 7 · 6:27 PMTestFlight
