uichemy_create_project
Creates a new UiChemy project from layouts in the UiChemy template library, using the copy, fonts and colours passed in. Quickest way to a whole site: give each page only its name (leave sections out). The layouts are then picked here, the way the UiChemy dashboard picks them, every page is built at once, and the reply lists every page's text slots, to write in one uichemy_set_text call (then uichemy_open_preview shows the site). Give sections only to choose layouts yourself. It is the only way to start a project here: every site is built from the template library, and HTML, CSS or JavaScript written elsewhere is not imported. For library sections as code in the user's own React app, uichemy_get_page_code is the tool. Each page is a list of sections, normally a navbar first and a footer last; a home page usually has 8 to 12 sections (hero, social proof, features, how it works, testimonials, pricing or offer, FAQ, CTA) and an inner page 5 to 8. Text and image slots belong to the layout: uichemy_template_slots lists them with their maximum length and what each one is for. A slot left empty shows its token on the page, an image slot left empty keeps the template's stock photo. Keep copy within each slot's limit: copy far over it is cut at a word boundary, and the reply lists it. Two sections using the same layout share the same copy, so use each layout once per project (navbar, footer and sections marked global excepted); a repeat is switched to a fresh layout of the same kind with its copy moved across, and an unknown layout or font is replaced, all named in the reply. The project is built either way; polish what the reply lists with uichemy_set_text or uichemy_replace_section. Inner pages carry sections about their own subject. On every page after the first, the hero is that page's header: it says what the page holds and what is further down, and leaves the brand story and pitch to the home page and the sections below. Image slots take urls, so a generated picture needs to be uploaded first. category files a page in the sitemap (Blog, Legal, Site Extras...); pages without one are filed under Core Pages. brief fills the project's Scope tab and is required, as are headingFont, bodyFont and all five palette colours. store: true builds an online store the way the UiChemy app does: Home is the storefront (woo-navbar first, footer last, woo- sections between), the nine standard shop pages are added wearing Home's woo-navbar - as do the core and legal pages - the blog pages wear the normal navbar (its search finds posts), and every page the one normal footer. Only for a site that sells products online - not a service business called a shop (barber, coffee, repair). The result names any slot left unfilled and any layout that was not found.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"pages": "<pages>",
"headingFont": "<headingFont>",
"bodyFont": "<bodyFont>",
"palette": "<palette>"
},
"name": "uichemy_create_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The project's name. When the user has not named the business, a fitting name works; it can be renamed later in UiChemy. | |
| brief | No | REQUIRED - send it on the first call; a call without it builds nothing. It fills the project's Scope tab. | |
| pages | Yes | Pages in order; the first is the home page. | |
| store | No | An online store that sells products: every page but the blog's wears the woo-navbar, the blog pages the normal navbar, every page one normal footer; plus the nine standard shop pages (Shop Page, Product Category, Product Single, Product Search Results, My Cart, Checkout, My Account, Order details, Track Your Order). | |
| palette | Yes | All five slots, as #RGB or #RRGGBB. | |
| bodyFont | Yes | A Google Font family name for body text. | |
| headingFont | Yes | A Google Font family name for headings. | |
| createCanvas | No | Also do what the editor's "Continue to design" does on first open — colour roles, the section style's band colours, the export section list, every page marked built — with no AI call, so the project needs no editor visit. Same as uichemy_create_canvas afterwards. | |
| sectionStyle | No | With createCanvas: the section style to pin (default subtle_01). Without one the canvas rolls a random one. |