⚠️ Five simple tips (please read this)

1. Prompt guidelines:
   • Don’t include any technical details (unless you are technical)
   • Describe what the product is
   • Who the users are
   • What each user can do
   • Any design needs
   • Ideally build adding features gradually. Use our helper tool if you need help.
2. Codapt understands your project deeply at every step. But it doesn’t remember past chat messages, by design. So avoid messages like “do it like before.” Just describe what you want, and Codapt will handle it!
3. Once your first version is ready! Here are a few prompts you can send Codapt in case something doesn’t work as expected:

   1. 💡 Got an error?

      *“I saw this error: [paste error message] when I [describe the action]”*
      

      💡 See a white screen? (Find logs in “Settings” button)

      *“I only see a white screen. Fix this: [paste all logs]”* 
      

      💡 See a “Not found” message? that feature isn’t built yet.

      “Build this feature: [describe]”
      

      Examples:

      Based on the image below, you would send this message:

      “When I open the page, a white page appeared with an error that said: contextMap[utilName] is not a function”

      

      A second example: based on the image below, you would send this message:

      “When I clicked on “Create Deal” Button, i saw this error: { "code": "invalid_string", "validation": "datetime", "message": "Invalid datetime", "path": [ "closeDate"]}]”

      

<aside> ⚠️

If, after a few attempts, it still doesn’t work, scroll up to the message that first triggered the error and click Undo. Revise the prompt—try different wording or a new approach.

</aside>

🦾 What’s the tech stack of the web apps generated by Codapt?

Codapt generates real solid full-stack web apps, built like the real software you actually use every day (Airbnb, Uber, Booking, Dropbox…)—no Supabase shortcuts, no prefab backend tools, no lock-ins. Every part of the stack is written in code, fully customizable, extendable, and production-ready from day one. Build Real Full-Stack Software, the Kind Developers Are Proud to Ship. Stop building toys.

Frontend:

• Framework: React 18 + TypeScript
• Styling: Tailwind CSS
• Build Tool: Vite
• Testing: Vitest/React Testing Library for unit/integration tests)

Backend:

• Framework: Node.js (likely with tRPC for API layer)
• Language: TypeScript