UiChemy AI Website Creator

View saved version →

---
name: build-site-from-brief
description: Build a new multi-page website project in UiChemy from a business brief, choosing real section layouts from the UiChemy library and writing the copy. Use when the user asks to create, generate or draft a website for a business.
---

Use this skill when the user wants a new website built from a description, a client brief, or a business type.

Inputs to gather from the user's message first: business name and type, audience, tone, pages wanted, colours or fonts if any. If the business type or name is missing, ask one batched question. For everything else, make a sensible choice and state it.

Steps:
1. Call `uichemy_section_spec` once and follow its rules for copy length, type scale and colour tokens. Do not guess limits.
2. Call `uichemy_list_section_kinds` to see which section kinds exist.
3. For each section on each page, find a layout:
   - Describe what you want to `uichemy_search_layouts`, or narrow a kind with `uichemy_find_templates`.
   - Call `uichemy_template_slots` for the chosen layout and write copy that fits each slot and its character cap.
   - Before building, call `uichemy_check_layouts` on the shortlist so two layouts that share slots do not show identical copy.
4. Pick a palette (hex values) and a heading and body font that suit the brand.
5. Call `uichemy_create_project` with the pages, palette, fonts and the copy you wrote. A real page has a navbar, five to eight sections and a footer, with every slot filled.
6. Call `uichemy_validate`, then `uichemy_check_responsive` for each page. Fix what they report with `uichemy_set_text`, `uichemy_set_section_style` or the other edit tools, then re-run the check.
7. Give the user the project name, the page list with each page's sections, the palette and fonts, and anything you could not fix.

Rules:
- Write copy from the brief only. Do not invent awards, client names, statistics, testimonials, prices or addresses. Where a fact is missing, write neutral copy or ask.
- Images: use only URLs the user supplied or that `uichemy_upload_image` returned. Leave an image slot empty rather than inventing a link.
- This skill creates a project in the user's own UiChemy account. Say so before you create it.

View saved version →

---
name: edit-site-design
description: Change the look or content of an existing UiChemy project, including colours, fonts, buttons, spacing, copy, logo, sections and pages. Use when the user asks to restyle, rewrite, add, remove, reorder or fix part of a site they already have in UiChemy.
---

Use this skill when the user names or implies an existing UiChemy project and wants a change.

Steps:
1. Identify the project. If the user did not name one, call `uichemy_list_projects` and ask which, unless exactly one fits.
2. Read before writing:
   - `uichemy_get_project` for pages, sections, palette and fonts.
   - `uichemy_get_page` for the slot tokens on a page. Copy edits need real tokens from here.
   - `uichemy_get_colors` before choosing a colour role.
3. Make the smallest set of edits that does what was asked:
   - Colours and type: `uichemy_set_palette`, `uichemy_set_fonts`, `uichemy_set_type_scale`, `uichemy_set_button_design`, `uichemy_set_card_design`, `uichemy_set_spacing`, `uichemy_set_section_style`.
   - Copy: `uichemy_set_text`. For several edits at once, use `uichemy_batch`.
   - Structure: `uichemy_add_section`, `uichemy_replace_section`, `uichemy_reorder_sections`, `uichemy_duplicate_section`, `uichemy_add_page`, `uichemy_rename_page`, `uichemy_reorder_pages`.
   - Images and logo: `uichemy_set_images`, `uichemy_set_logo`, with URLs the user supplied.
4. Run `uichemy_check_responsive` on each page you changed and `uichemy_validate` on the project. Report what they found and what you fixed.
5. Summarise what changed in plain words, per page.

Confirm first, every time:
- `uichemy_remove_page`, `uichemy_remove_section`, `uichemy_remove_post` and `uichemy_delete_project` cannot be undone from here. Name exactly what will be removed, ask the user to confirm, and call the tool only after a clear yes in this conversation.
- `uichemy_delete_project` needs the user to type or confirm the exact project name. Never fill `confirmName` on the user's behalf without that confirmation.

Do not:
- Call `uichemy_save_section_template`. It is a development-only tool and is not part of any user workflow.
- Change a project the user did not ask you to touch.
- Invent facts when rewriting copy.

View saved version →

---
name: export-to-wordpress
description: Mark a finished UiChemy project as exported for Elementor or Gutenberg and show which projects are ready for the UiChemy WordPress plugin to pull. Use when the user says the site is done, asks to send it to WordPress, or asks what has been exported.
---

Use this skill when the user wants to hand a finished project to WordPress.

Steps:
1. Identify the project with `uichemy_list_projects` if the user did not name it.
2. Run `uichemy_validate` and `uichemy_check_responsive`. If either reports faults, tell the user and offer to fix them first. Do not mark a project exported while known faults remain unless the user says to go ahead.
3. Ask which builder, Elementor or Gutenberg, if the user has not said.
4. If the project came from an import, call `uichemy_sync_builders` first so the builder code is published.
5. Call `uichemy_mark_exported` with the project and builder.
6. Call `uichemy_list_exported` to confirm the project now appears, and tell the user the next step happens inside their WordPress site: open the UiChemy plugin there and pull the project.

Rules:
- To put a project live as a site on a UiChemy address, say what you are about to do, ask the user to confirm, then call `uichemy_publish_site`, and report the address with `uichemy_publish_status`. `uichemy_list_sites` shows their sites. `uichemy_unpublish_site` takes one offline, and it also needs the user's confirmation first.
- This plugin does not connect custom domains, change DNS, or log in to a WordPress site. For WordPress, the user pulls the project with the UiChemy WordPress plugin. Say so if asked to deploy to their own hosting or domain.
- Do not describe pricing or plans. If the account cannot export, say that and link https://app.uichemy.com/support.

View saved version →

---
name: get-started
description: Orient a new user to the UiChemy AI Website Creator, confirm which UiChemy account is connected, and list their projects. Use when the user first connects, asks what this plugin can do, or when any UiChemy call is refused.
---

Use this skill when the user has just connected UiChemy, asks what they can do here, or a UiChemy tool returns an access error.

1. Call `uichemy_whoami`. Report the account it returns and what that account can reach. If it says the account lacks access to create projects, say so plainly and point the user to https://app.uichemy.com/support. Do not retry in a loop.
2. Call `uichemy_list_projects` and show the user's projects, newest first, by name. Do not show internal ids unless the user asks for one or a later step needs it.
3. Offer the four things this plugin does, in one short list:
   - Build a new multi-page WordPress-ready site from a brief.
   - Edit an existing UiChemy project: colours, fonts, copy, sections, pages.
   - Import a site you already have (HTML, CSS, JS or a zip) into UiChemy.
   - Mark a finished project as exported so the UiChemy WordPress plugin can pull it into Elementor or Gutenberg.

Rules:
- Only act on the connected user's own UiChemy projects.
- Never ask for a password, API key or token. Sign-in happens through UiChemy's own sign-in screen.
- Do not describe prices, plans or upgrades. If a feature is unavailable on the user's plan, say that, and link https://uichemy.com/pricing/ as information only.

View saved version →

---
name: import-existing-site
description: Import a website the user already has (HTML, CSS and JS written in chat, or a zip) into a new UiChemy project, verify the import, and prepare it for WordPress export. Use when the user wants to bring an existing static site or AI-generated site into UiChemy.
---

Use this skill when the user supplies site code or a zip and wants it in UiChemy.

Steps:
1. Call `uichemy_import_spec` once. Follow what it says the importer accepts and how to verify an import. Do not guess the format.
2. Choose the path:
   - Files the user pasted or you wrote in this chat: `uichemy_import_files`.
   - A zip at an https URL the user gave: `uichemy_import_zip` with `zipUrl`.
   - A zip the user attached: `uichemy_import_zip` with `zipData` only if the file is small enough to pass directly; otherwise ask for a URL.
3. Tell the user a new project is being created in their UiChemy account, then run the import.
4. Verify with `uichemy_get_project` and `uichemy_validate`. If the import spec lists a known failure signature that matches, apply its fix. Otherwise report the problem and what you tried.
5. Run `uichemy_check_responsive` on each page and report overflow or unreadable text.
6. When the user wants builder-ready output, call `uichemy_sync_builders` for the project and report the result.

Rules:
- Import only code the user owns or has the right to use. If the user asks you to copy a third-party site they do not control, decline.
- Do not fetch or scrape sites yourself. Work only from what the user supplied.
- Never include credentials, API keys or personal data from the source files in your replies.