add_component
ChatGPTCopy a ready-made interface component into the site: button, card, input, textarea, label, badge, separator, alert, accordion, dialog or tabs. They are styled with the site theme and need no setup. Call it with no component name to list them.
add_package
ChatGPTUse this when the site needs a package that is not already installed — animation, a carousel, dates, maps or charts. Installs one approved package into the site workspace. Call it with no package name to see what is approved; anything else is refused.
check_domain
ChatGPTUse this when the user asks whether a domain name is available, especially Kenyan ones such as market.co.ke, shop.ke, brand.me.ke, school.ac.ke or org.or.ke. Returns available, taken or unknown, with the registrar price when known. An available name is not a reservation: it must be registered, and availability can change before checkout.
connect_domain
ChatGPTUse when the user wants their own domain on a published site. Adds the domain and returns the exact DNS records to set. The site must be published first, and the domain must be one the user already owns — this does not register one.
create_form
ChatGPTUse this when the website needs an enquiry or booking form. Creates a Shika Form for one of the user's sites and returns the embed and hosted URLs. Submissions land in the Shika dashboard.
create_site
ChatGPTUse this when the user wants a new website and the plan has a free slot. Creates the site and starts its preview. Check get_account first, and pass an idempotency_key so a retried call does not build the site twice.
delete_file
ChatGPTUse this when the user wants one file removed. Irreversible through these tools, so confirm first when the file is something the user provided.
duplicate_site
ChatGPTDuplicate a website into a new draft site with its latest files, plan and photos. Uses a new plan slot and does not copy the live app or version history. Use only when the user explicitly asks for a copy.
edit_file
ChatGPTUse this when changing a small part of a file. The find text must appear exactly once, so the edit is unambiguous. For larger rewrites use write_file with the full content.
get_account
ChatGPTUse this when you need the user's websites or how many site slots their plan has left. Call it first, so you can offer to continue an existing site or start a new one.
get_form_submissions
ChatGPTUse this when the user asks what customers sent through a form. Returns the latest submissions for one of the user's Shika Forms.
get_site
ChatGPTUse this when you need one website's live state: its preview URL, whether the workspace is running, and the latest site-check findings. Poll it after create_site or while the workspace warms up. It never changes the site.
get_site_analytics
ChatGPTRead a published site's traffic summary: requests, unique visitors, status codes, latency and recent paths. Empty until the analytics agent reports; do not invent numbers.
list_files
ChatGPTUse this when you need the workspace file map before reading or editing. Lists path and line count for code and content files, and is read-only.
list_forms
ChatGPTUse this when the user asks which forms exist, or needs a form's embed URL or submission count.
list_sites
ChatGPTUse this when the user asks which websites they have: name, kind, status and the site uuid every other tool needs. Use get_account instead when the plan or slot count matters too.
load_site_recipe
ChatGPTUse this when the kind of site is known and you want the sections, content and checks that kind needs. Pass name (or kind), for example restaurant, and load it before laying out pages.
preview_logs
ChatGPTUse this when the preview is blank, a page will not load, or an import fails. Returns the dev server log tail, where Vite and React report the real error — read it before changing code.
publish_site
ChatGPTUse this when the user has explicitly asked to publish and the site check reports nothing blocked. Makes the website live at its public address. Refuses while the check is failing or another session is editing the site.
read_file
ChatGPTUse this when you need a file's current content, before editing it. Large files are paged. Read before writing so you do not overwrite work you have not seen.
read_plan
ChatGPTUse this when resuming a site, after a long gap, or when unsure what is left to build. Returns the stored plan: pages with their status, the shared components, notes and the next step.
remove_domain
ChatGPTRemove a custom domain from a published site, after the user explicitly confirms. It deletes managed DNS records the platform created, but leaves records in an external DNS provider for the user to remove. Never call with confirm true until the user has said yes in this conversation.
run_site_check
ChatGPTUse this when the site is ready to verify before publishing. Runs a real-browser check of layout, contrast, accessibility, content and SEO, and takes a few minutes. Poll get_site for the findings; publishing is refused while anything is blocked.
test_form
ChatGPTWrite a realistic test response into one of the site forms and remove it again. This verifies the inbox stores submissions; it does not send or test email delivery. A required file upload cannot be tested automatically.
write_file
ChatGPTUse this when creating a file or replacing one completely; the live preview updates immediately. Max 512 KB per call. It overwrites the existing file, so read it first.