Tips for how to develop with claude.
Claude Code's default sandbox mode works great for nooq development, and provides some additional protection above normal claude usage. You don't need to change any permission settings — just accept the defaults and you're good to go.
/sandboxFor the best experience building nooq apps, we recommend using Opus with high thinking effort. In a Claude Code session:
/model and select opus/config and set thinking to highHere's what a real session looks like — from first prompt to working app, including fixing bugs along the way.
Claude reads the nooq tools, creates an app called "my-todos", writes the HTML/CSS/JS, and deploys it. You get a live URL within a minute or two.
The app shows up with an input field and an add button — a clean, working todo list.
Claude realizes the todos are only stored in memory. It switches to using nooq's built-in database so tasks persist across refreshes.
It creates a todos table, updates the JavaScript to call API endpoints, adds server-side routes, and redeploys. Refresh the page — your tasks are still there.
Claude adds a pure-JavaScript confetti animation — no external libraries needed. Check a task off and colorful confetti bursts from the checkbox.
Claude fixes the event handler to check whether the task is being checked (not unchecked) before triggering confetti. Quick redeploy and the bug is gone.
That's the loop: describe what you want, Claude builds it, you try it out, and you tell Claude what to fix or add next. No need to write code yourself.
Head back to the developer setup page to get your API token and connect Claude Code to nooq.
Get started