Claude Code
Set up Claude Code using the official guide. Start a session in the folder containing your plan, then send the message below. The setup guide also links to its desktop interface.
Official setup guideYour plan → your first build
The plan gives your AI the instructions to build. Set up your chosen tool, hand over the folder, and let it carry the work forward. You provide decisions when needed and review the results.
Download the ZIP from your results page or email. A ZIP is a folder packed into one file: open it to unpack the contents. Keep the files together and read START_HERE.md first.
Use an AI development tool that can work with a project folder. Choose one of the options below. Its account, subscription, and usage costs are separate from your build plan.
Open the unpacked folder in your tool. Send the message below so the AI reads the complete plan and carries out the development and checks. You do not need to prompt every step or understand the technical file names.
The AI may need account access, a product decision, or permission to continue. Respond when needed, then ask it to show you how to try the result. Check the main user journey and describe anything you want changed.
Set up Claude Code using the official guide. Start a session in the folder containing your plan, then send the message below. The setup guide also links to its desktop interface.
Official setup guideOpen the desktop app and sign in. Choose the folder containing your plan, select Codex for software development, and start a chat with the message below.
Official setup guideChoose File → Open Folder and select your plan folder. Open the Agent panel, then send the message below. Agent can read and edit files in your project.
Official setup guideSelect and copy this message into your AI tool.
Read START_HERE.md and all the build-plan documents in this folder, including PROMPT.md. Use the complete plan to carry out the build autonomously, following the required order and running the checks as you go. Fix problems you find and continue without waiting for me to prompt each step. Ask me when you need a product decision, access, or permission, including before using a paid service or publishing. Keep me informed in everyday language. When the work is ready for review, explain what you built, what you tested, anything still unresolved, and how I can try it.
Try the main user journey, review any payments and account access, and check how personal information is handled. Ask your AI to explain what has been tested and what still needs attention. Get experienced help with anything you cannot confidently check.
The plan includes the detail your AI or developer needs. You can explore it here without needing to learn every technical term.
ARCHITECTURE.md
A connected view of your product: data, screens, integrations, and infrastructure. Decisions explained, trade-offs made explicit.
Also included: brand assets, an API setup guide, and an independent architecture review. Reference-based components are included when you supply a design reference.
You can give the same plan to a developer, or talk to us about a Done for you project. The build is quoted separately.
Talk about my projectTell us what you want to create. We’ll prepare the plan you can build from.
Start with my idea