Replace ALL top-level sections of the CURRENTLY SELECTED page with a generated list of components. This OVERWRITES the page — it does NOT create a new page (use create_page) and does NOT append a single section (use add_section). Use when the user asks to build/replace/redesign an entire page. Each top-level component should be wrapped in a container.

Create a NEW blank page in the project and (by default) select it. Returns the new page's id and fileName. The page starts nearly empty — fill it with replace_page_content or add_section, and point a navbar/link at it with link_page. Use THIS to add an additional page; use replace_page_content (NOT this) to overwrite the current page's content.

Point an existing link at a project page — the same wiring the UI's 'Link to' picker does. Pass the link's targetPath (from read_page) and the target page (id or name). For a navbar link this sets its page target so the href and active state stay in sync; for a plain link or button it sets href to the page's ./slug.html. Use after create_page to wire a navbar to the new page.

Insert a new section into the current page. Use for adding discrete sections (hero, features, pricing, CTA) to an existing page. Appends to the end by default; to place it somewhere specific, pass position plus the targetPath of the component to place it next to.

Modify an existing component. By default this edits the selected component. To edit a component identified by read_page, provide its targetPath; an explicit path overrides the canvas selection. Preferred: provide component — the full replacement component tree (compact DSL OK), best for structural changes. Alternative: provide html — the complete modified HTML string. Fallback: provide patch — JSON Patch (RFC 6902) for tiny single-property tweaks. Supply exactly one. Preserve existing IDs: an id kept in the edit keeps the styles attached to it; an id you drop loses them.

Remove a component from the current page entirely. Use this instead of emptying a section's contents — an emptied section leaves a stray blank div on the page. Deletes the selected component by default; pass targetPath (from read_page) to delete a component you did not select.

Insert a pre-built block from the catalog and optionally customize its content. STRONGLY preferred over generating from scratch when a matching block exists. The block re-themes on insert — its colour and font classes resolve against THIS site's theme, so the result is meant to differ from the catalog thumbnail (a screenshot of the block in the template it came from).

Update site settings — SEO title/description, site URL, structured data (JSON-LD), per-page SEO overrides, language, theme tokens (light + dark), Google fonts, dark mode toggle, and site-wide custom CSS for component-level restyling (globalTheme.customTailwindConfig). Provide ONLY the fields that change. general/seo are SITE-WIDE; use page to change ONE page. Also used to match the theme to a reference IMAGE's vibe: sample its palette into brand/surface tokens and ALWAYS set BOTH light and dark variants.

Commit this site to a specific visual direction, and apply it (fonts, type roles, palette swatches). Call this ONCE, BEFORE generating a new site's first page — a site with no committed direction has nothing for later edits to stay consistent with, and the result drifts to generic. Prefer a directionId from the sampled menu; supply the custom fields only when the user's brief clearly calls for something the menu doesn't cover. Not needed when editing a site that already has a direction.

Apply Swebsy's built-in scroll-reveal animation in one step — a smart, per-section staggered entrance on headings, text, images, buttons, and cards (navbars/footers skipped). Prefer this over hand-placing animate-* classes whenever the user asks to animate the page or site, or wants a consistent reveal.

Read the current page structure and addressable component target paths. Call this BEFORE editing a named or relative page component that is not the current selection. The default sections read lists every top-level section with its target path — enough to pick the one to edit. When copying content between components, use detail: full WITH the targetPath of the one section you're copying, not a whole-page read. Also call it AFTER applying edits to verify the result.

Load deep, on-demand guidance for a specific area before acting on it (e.g. before adding animations, composing a new page, writing copy, building forms, editing the nav, or reusing components with symbols). Returns the full instructions for that skill.

Start a pairing session. Returns a single-use pairUrl — give it to the user to click; opening it connects their Studio tab automatically. (Also returns the raw code/port for manual entry.)

Report bridge status, siteName, selected page, and editorReady, plus a short theme summary (fonts, default color mode, brand colors). After creating or opening a site, wait until editorReady is true and siteId matches the expected site before editing.

List the project's pages (id, name, fileName, section count, which one is selected). Call this instead of guessing a page name for select_page or link_page.

Refresh and list installed site templates with names, descriptions, tags, fonts, preview URLs, and thumbnail URLs. Works from Home or Studio.

Create a site and open it in Studio. Omit templateId for Swebsy's standard blank site; provide an installed template ID to import that template unchanged. Then poll swebsy_status until editorReady is true and siteId matches before editing.

List saved sites newest-first as metadata only: IDs, internal names, status, timestamps, template ID, page count, and whether each site is open.

Open a saved site by ID in the paired tab and return its metadata. Idempotent if it is already open. Poll swebsy_status for the expected siteId and editorReady before editing.

Rename a saved site's internal Studio/Home name. This does not change its SEO or public title settings.

Select a page in the connected Studio project.

Read the currently selected component (type, classes, attributes, text). Secrets are never surfaced.

List the project's SYMBOLS (reusable components that stay in sync across every page). Returns each symbol's id, name, component type, instance count, and how many pages use it, plus a health report of BROKEN linkage: orphans (copies whose main was deleted — editing them changes nothing elsewhere), unregistered (instances the main doesn't list back, so edits propagate one way only) and ghosts. Repair any of it by calling promote_to_symbol on one affected section. Use before add_symbol_instance to find the symbol id.

Promote an existing component into a reusable SYMBOL so it can be shared, in sync, across pages. Pass its targetPath from read_page (e.g. the navbar or the CTA band). Also REPAIRS broken linkage (see list_symbols → health): re-promoting an orphaned copy rebuilds its main and re-links every other copy of it, and re-promoting a symbol registers instances it had lost. Returns the symbol id (for add_symbol_instance) and a repaired count; copies whose structure has diverged too far are reported as detached — delete_section + add_symbol_instance those instead.

Add a linked INSTANCE of an existing symbol (see list_symbols) to the CURRENT page. The instance stays in sync with the symbol main and every other instance — the way to reuse one navbar/footer/CTA across pages. Select the target page with select_page first.

Load the static Swebsy builder guidance (component system, theme classes, conventions) that the in-app AI Builder is primed with.

List the available deep-guidance skills (animation, page-composition, copywriting, forms, nav) with one-line summaries.

List the pre-built block catalog (ids + labels) available to insert_block.

Capture a styled screenshot of the current page at a fixed viewport, written under .swebsy-agent/screenshots/. Returns the file path. Scope it with targetPath when verifying ONE section — a whole-page PNG downscales so far that component detail is unreadable.

List managed assets in the open site with whole-project usage counts. References are checked across every page, shared symbols, styles, and site settings. Use imagesOnly:true and unusedOnly:true before deleting unused gallery images.

Upload a local image file into the open site's asset library and return the src to use on an image component. This is the ONLY way to get your own imagery (screenshots, logos, textures, mockups) into a site — an image with an empty src gets a random stock photo instead. Reads the file from the agent's own filesystem, so pass a path you can see (for example a screenshot you just captured). The asset is stored in the project and travels with static export and project JSON.

Delete one managed asset from the open site's asset gallery. By default this refuses assets referenced by any page, shared symbol, style, or site setting; call swebsy_list_assets first. force:true also clears live component references and should be used only when that is explicitly intended.

Export the site to .swebsy-agent/exports/. Static files via the site exporter and/or the project JSON (with assets). Returns outDir, the exported page paths, and per-kind file counts — verify a build by grepping those HTML files.