Roc, your AI builder
Roc is the AI builder inside Instroc. You describe what you want in plain language, and Roc designs the app, writes the code, wires up the backend, and rebuilds the preview so you can see the result. This page explains how Roc approaches new builds and changes, how it asks questions, how it remembers your preferences, and what it deliberately refuses to do.
What Roc builds
When you start a new project, Roc does not hand you a single placeholder page. It builds a complete, multi-page app with real navigation, mobile-friendly layouts, and a working backend when your idea needs one (Roc enables Instroc Cloud automatically whenever the request implies data, sign-in, or forms).
Design is treated as a first-class part of the build. Roc commits to a specific color palette and font pairing for each app, so the result has its own personality rather than a generic look. Because the theme lives in one place, follow-up requests like "make it warmer" or "make it darker" are quick and cheap. For photographic subjects, Roc pulls real photography from the built-in stock photo library instead of leaving gray placeholder boxes, and the images need no attribution.
If you paste a URL into your message, Roc reads that page and uses it to ground the build. This is a handy way to bring in real menu items, service descriptions, or product copy from an existing site.
How Roc handles changes
Modifications work differently from new builds. Roc searches your project and reads the relevant files before touching anything, then makes minimal, surgical edits. It will not refactor unrelated code or restyle parts of the app you did not ask about. A single request can still touch multiple files when the change genuinely spans them.
Every change lands as a new version, so you can always step back. See Live preview for how versions, diffs, and restore work.
Clarifying questions and plan mode
On a new project, Roc asks two to four quick questions on a card above the chat input before it starts building: your app's name, the visual direction (with concrete moods like "Elegant & minimal", "Bold & playful", "Dark & modern", or "Warm & friendly"), and any functional detail that would change the build. You can move through them with Back, Skip, Next, and Continue, skip them all, or just say "just build it".
For complex requests, Roc may offer to create an implementation plan first. You can also switch on the Plan toggle yourself; in plan mode Roc writes a step-by-step plan for you to review before any code is written. On existing projects Roc only asks questions when a design request is genuinely vague, otherwise it simply acts. And when you are just discussing ideas, Roc describes what it would change and asks "Want me to build this?" instead of jumping straight into code.
Project memory
Roc remembers how you like to work, per project. Style, audience, and color preferences persist across the conversation, so you do not have to repeat them. Feedback shapes future output too: when you downvote a response or revert a version, Roc treats that as a signal about what to avoid next time.
Automatic error fixing
If a build fails after one of Roc's changes, Roc fixes it automatically and the fix costs nothing. The reasoning is simple: if the AI broke the build, the AI repairs it for free, and your preview keeps showing the last working version in the meantime.
Runtime errors are detected too. The editor shows a badge when errors are found in the running app, and you can click it to start a fix. Unlike build-error fixes, runtime error fixes do use credits, but at a reduced rate. You can also type /troubleshoot in chat (the command also answers to "debug" and "diagnose") or use the Troubleshoot button to have Roc explore your app, find issues, and fix them. For prompting techniques that reduce errors in the first place, see Best practices.
What Roc will not do
Roc holds a few lines that protect the quality of what you ship. It will not fake a backend: no using browser localStorage as a database, no mocked sign-in flows, and no suggestions to bolt on an external backend service, because Instroc Cloud provides the real thing.
Roc also never asks you to paste API keys into chat. Keys for connected services belong on the Integrations tab, where they are stored server-side and always redacted. When a request needs a service like Stripe, Roc shows a connect card that takes you to the right place instead. See Integrations for the full list.
The more concrete your first prompt, the better the first build. Name your app, mention who it is for, and paste a link to any existing site you want Roc to draw content from.