Propose an app design
propose_appYour agent can design an app with you. Send it as app, a short plan or a full design, and get back a link that opens it in the Architect as a new, unsaved design. The person sees every screen, changes what they like and hands it back for emit_app. format: true returns the format of a design, or of a plan beside app: { version: 1 }; "photos" lists sample photos. dryRun: true checks without making a link. into takes the code from the person's line and sends the design to the one they have open.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "propose_app"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | The design: { name, tabs: [{ screenId, label }], screens: [{ id, name, composition: { screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } } }], onboardingScreenIds: [], pushed: [{ screenId, fromScreenId, presentation }], theme? }. A node is { id, slug, props }: slug is "wireframe:<block>" such as "wireframe:list-row" (a list whose rows open one screen is one row block with repeats: "true" and its sample rows in rows: [{ title, ... }]) or a component from find_component, and a content node opens a screen with navigate: { to, presentation } beside its props. A top bar is header: { id, slug: "header", props: {} }, titled by the screen's name; a sheet has none. entryScreenId is only for a splash screen before the tabs. Titles and composition metadata are set by the builder. | |
| into | No | ||
| dryRun | No | check the design and report, without making a link | |
| format | No |