Turns a thread, skill, spreadsheet, or Claude/ChatGPT project into a polished, visual Agent-Native app: populated domain screens with the in-app agent working behind contextual controls. Use when a user invokes `/turn-into-app`, or asks to turn a workflow, skill, spreadsheet, or project into an app, UI, workbench, or dashboard, including from Claude or ChatGPT on the web.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
The canonical home for this skill is turn-into-app in BuilderIO/skills
Give a proven workflow an Agent-Native app face and agent brain. Start with populated domain screens. Object controls send work to the agent; the object shows progress and receives the result. Avoid form-under-stepper layouts.
create_workspace_app.npm,
pnpm, or npx, edit files, or start a server there, and never invent a
Builder branch URL: report what Dispatch returned.On an interactive local host, after the plan (step 2) and before installing, ask once: On your machine (some setup) or Hosted with Builder (a free Builder account). Skip it on browser hosts or when the route is set (by the person, a resumed run, Local File Mode, an existing workspace, or headless); where it runs says which wins.
/turn-into-app /some-skill), read that skill and package
it immediately, even at the start of a thread. A supplied path or attachment
is the source.Project context counts only when the host puts it in the current context. The MCP connector does not read hidden project chats, private URLs, account settings, or credentials. Never claim private access, invent an importer, add fake OAuth, or scrape a logged-in page; ask for an export.
Read the spreadsheet guide before working a workbook. The boundaries:
Decide and proceed. Take the source's recommended option, otherwise the most conventional default, and record it as an assumption. Never ask about visuals, copy, layout, template, or integrations.
Beyond the hosting question, ask once, with your recommendation, only when:
Headless means no question tool and no live chat (claude -p, codex exec,
a harness, a scheduled or delegated run, a prompt saying nobody can answer);
when unsure, assume headless. Interactive: ask with the question tool, or end
your message with the question and your recommendation. Headless: never end
the turn on a question. For reasons 1 and 2, print it with your
recommendation, record the assumption in the brief, and keep building (stop
and report only when nothing is identifiable); for reason 3, skip the blocked
step (no write, deploy, or guessed workspace), finish the rest, and report it
as pending. Confirmation happens in the conversation; the generated app never
opens on a mapping or setup screen.
Copy and update this checklist. Aim for 45 minutes; note the start time
(date). If review starts after 35 minutes, run one pass and list open criteria.
- [ ] 0 Host classified, source picked
- [ ] 1 Source read, brief drafted
- [ ] 2 Design decided; plan and estimate shown; where it runs asked
- [ ] 3 Real scaffold, onboarding config, local sign-in
- [ ] 4 Actions, domain surface, sample data, agent moments, agent instructions
- [ ] 5 Running; screenshots reviewed and refined (two passes by default)
- [ ] 6 Typecheck, doctor, build; app handed over; final reportResume an unfinished run instead of starting a second app. When the working directory holds an app this skill started for the same source (a completed scaffold or actions, but no review screenshots), verify the completed stages from its git status, brief, schema, and actions. Open with what exists, the next stage, and the active work left ("Found a half-built app. The data model and actions are done; screens and checks are next, about 10 more minutes."). Resume at the first unverified stage without rerunning scaffolding or replacing completed work.
Read the whole source (a large workbook or export in bounded chunks), then fill in the source-brief template; it has a reading recipe per source type. It names the job, at most three agent moments, the invariants, data hazards, source of truth, and assumptions. Never turn a one-off answer, private data, or an unverified result into product behavior.
Read the UI direction guide now. Decide these and add them to the brief under App design:
app.homePath), domain navigation, chat kept as its own destination, panes
that fill the viewport, and the header title as the only page title.Source steps become states of objects (Draft, Checked, Approved), never a stepper, numbered tabs, or a wizard. Chrome stays quiet: no eyebrow, subtitle, repeated title, or stat strip over visible data. Show the plan in your message (a saved file is not shown) in plain words: the job, what the person sees first, how it looks and why that suits the work, and what the agent does where. Name the steps (install, scaffold, checks, dev server, headless browser) and estimate work time from the source and host, with external setup waits apart. Codes, direction names, tokens, and the tie-break stay in the brief. Then ask where the app runs and wait, unless that question is skipped.
Choose a short slug and never overwrite an app. Run standalone creation from its parent directory, noting that the nested app is its own Git repository:
npx --yes @agent-native/core@latest create <slug> --standalone --template chat
cd <slug>
pnpm installInside an existing Agent-Native workspace (a parent package.json has
agent-native.workspaceCore; create beneath it delegates to add-app), run
from the workspace root:
pnpm exec agent-native add-app <slug> --template chatRead the generated AGENTS.md and any build-an-app skill. This skill
overrides guidance that skips the design record, screenshots, or build; leaves
DESIGN.md unchanged; omits AUTH_DISABLED or says not to set it; or stops
the dev server. Use another first-party template only if it materially fits.
If a scaffold or install step fails, times out (no output for 5 minutes), or is denied, the app does not exist yet. Retry once where a retry could help, then stop and report the exact command, the failure, and what is on disk. Never hand-build the app in another stack, edit a pinned dependency version to force an install, or continue in a half-created directory; a workaround the user requests is named in the report.
Then save the brief as docs/brief.md, append the domain surface's design to
DESIGN.md (UI direction guide, section 4), and follow
the run and deploy guide to set
onboarding.firstRun in agent-native.json (the shared setup, never a
credential form or a hardcoded key) and AUTH_DISABLED=1 in the ignored
.env before the first screenshot.
defineAction files in actions/. The UI calls
them with useActionQuery and useActionMutation from
@agent-native/core/client/hooks; the agent calls the same actions. No
/api/* route for app data and no LLM call from the browser.@agent-native/core/local-artifacts, per the scaffold's storing-data
skill), SQL holds only an index, and the app is local-only. Files a thread's
run happened to write are examples, not the source of truth.sendToAgentChat from @agent-native/core/client/agent-chat with
openSidebar: true, chatTarget: "local", ids and a bounded summary in
context, and submit: true (false when the user should edit the prompt
first). The object shows its working state at once, never stays busy without
a run behind it, and receives the result through an action, with attribution
and Accept, Edit, Retry (UI direction guide, section 7). Follow-ups stay in
the same thread; no second prompt box. Label deterministic controls plainly,
and never use sparkle, wand, magic, or robot icons.AGENTS.md, the
system prompt, and the display name (UI direction guide, section 5).AgentSidebar with one AgentKit
controller and transport: no legacy AssistantChat, no second stream owner.A spreadsheet becomes a live workbench, not a sheet clone (spreadsheet guide, section 5).
Start the dev server as the run and deploy guide says, then follow the review loop:
/ (desktop and phone, light and dark, then the main agent control
clicked). It must land on the domain route; a sign-in card or a restarting
server is not a pass./ off
the domain route, an empty or form-only first viewport, scaffold tokens,
clipped text, raw markdown, sideways scroll, console errors) overrides the
mean..tmp/ui-review/out/. Installed design skills
are optional; the review loop limits them.Exercise the real path, not only the files: / opens the domain route with
sample data; every AI-labeled control opens the sidebar with its bounded
prompt (with a provider, the result lands and persists; without one, the
object does not stay busy, and say so); actions persist (read the row back);
application state updates.
Run pnpm typecheck and pnpm agent-native:doctor (plain pnpm doctor is
pnpm's own command), then stop the dev server, remove AUTH_DISABLED from
.env, and run pnpm build. Fix a non-zero exit or a doctor finding; the
"production configuration errors" block printed with exit 0 is the deploy
checklist, not a defect (run and deploy guide). Deploy only when asked or
when the provider is already configured. Then hand the app over as that guide
says: an interactive run on the person's machine restarts it with --open, a
headless run stops it.
Lead with the app, plainly:
--open hand-off; else where
it is and how to open it. Hosted: what Dispatch returned (per mode).Under a short Details heading: directory; PID and stop command, if running; absolute screenshot paths, rubric scores, and open criteria; verification with evidence labels, and what the review click left behind; a deployment URL only if real.
Report what exists, not what was intended. Never claim the app exists without a path and a verification result. If the scaffold never completed, a step was worked around, or the app is not the real Agent-Native scaffold, that is the headline, and the build is not complete.
turn-into-skill packages a workflow that needs no UI.
BuilderIO/agent-native
cf9ff10
Canonical home
since Sep 10, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.