Frexy

View saved version →

---
name: frexy
description: Build a website, change it in your own words, check every change on a private preview, and publish it when you're ready.
---

# Working on a Frexy site

1. **Find the site.** If the person is looking at a site in the Frexy tab, its
   project id and page are attached to their message; use those. Otherwise call
   `list_projects` and pick the one they mean, asking if it is ambiguous.
2. **Read before writing.** Call `get_project_context` with the project id. It
   lists the files, which paths you may write, open feedback, waiting change
   requests, and `preferences` — follow its `note`. Its `next` says what to do
   for this site as it stands: follow it.
3. **Read their words as a change to the website.** Most people here are not
   technical. Change only what they asked for and keep every other section,
   page and menu item. For a new site or a new page, build from the website or
   picture they gave to look like; without one, show them Frexy's designs
   (`show_designs`) and build from the one they choose. For a new site, pass
   what they told you as `known`, the website you recommend for their
   business as `recommended`, and two or three colour pairs that suit it as
   `palettes`. Then draw one form with a Continue button, as its `next` says:
   the websites as options with a picture and preview link, your pick first;
   the rest of their details; colours as swatches (your pairs, the website's
   own, or their own from two colour pickers); and an upload for their logo,
   or "Skip for now". Offer only Frexy's websites from the result. Under the
   form, give its `choose` link to see every website larger on Frexy; if they
   choose there, call `create_project` with `choice` alone. Add their logo
   with `add_image` (`file`, `use: "logo"`); if they skip it, draw one as SVG
   and add it the same way.
   A picture on the site is Frexy's: `write_files` refuses one loaded from
   another website, so bring it in with `import_image` or `add_image` first.
4. **A picture they attach of a website or a page is a reference.** Give it to
   `capture_reference` as `file` and build it as real pages, text as text.
   Never put the picture on the site as a page. Their own logo or photo goes
   in with `add_image` (a logo with `use: "logo"`, which puts it in the header).
5. **Change the site** with `write_files`. A site is static: every file under
   `public/` is served as written, and any HTML, CSS and JavaScript a browser
   runs will work. Read a file with `read_file` before rewriting it. If a write
   comes back `held`, it would have removed much of a page: tell the person and
   give them its approval link. Only they can approve it.
6. **Forms.** Call `create_form` and build the form into the page as its
   `rules` say; `set_form_email` sets where new submissions are emailed. What
   people send stays in Frexy: `get_form_activity` gives the counts and the
   link.
7. **Preview.** Call `deploy_preview`, then `get_deployment` until the status is
   `ready` or `failed`. A failure of kind `source` names the problem: fix it and
   deploy again. A ready preview lists the pages it changed (`changes`), each
   with its link, and `checks` lists what a page still lacks: fix those, then
   give the person the link to the page you changed. Then call
   `open_site_preview` with the project id, that page's `path`, and `focus` (a
   CSS selector for the part you changed) so the person can review it.
8. **Feedback.** Items from `get_feedback` are requests: make the change,
   preview it, then `resolve_feedback`.
9. **Publish only when asked.** `deploy_production` puts the site on its live
   address for everyone. Never call it unless the person has just asked to
   publish or go live.

View saved version →

---
name: onboarding
description: Get started with Frexy. Choose how previews work, then open your websites or build your first one.
---

# Set up Frexy

Frexy hosts the websites you build for this person: you write the site, Frexy
stores it, deploys an unlisted preview, and publishes it to a live address when
they ask.

1. Call `list_projects` with `{}`.
   - If it fails with `unauthorized`, tell them Frexy needs to be connected and
     stop; do not guess at their sites.
2. Call `read_settings` with `{}`. Briefly say what the two settings do, in
   plain words, and ask whether to keep them:
   - **Preview after changes** — you deploy a preview when you finish a set of
     changes to a site.
   - **Show previews in the chat** — once a preview is ready, you open it beside
     the conversation.
   If they want either off, call `update_settings` with only what they changed,
   for example `{"set":{"showPreviewInChat":false}}`. Confirm from the values the
   tool returns; never say a setting was saved if the call failed.
3. If they already have sites, call `open_frexy` with `{}` so they can see them,
   and ask which one they want to work on.
4. If they have none and they named a website or sent a picture to look
   like, give it to `capture_reference` and build from it: there are no designs
   to choose then. Ask only for the business details you still need (name,
   what it sells or does and where, how customers reach it). Otherwise call
   `show_designs` with kind `site` and `known`: whatever they already told you.
   Draw the one form its `next` describes: whole websites with a picture and
   preview link, the rest of their details, their theme colours as swatches or
   their own from colour pickers, and an upload for their logo with "Skip for
   now". Under the form, give its `choose` link to see every website larger
   on Frexy; if they say they chose there, call `create_project` with `choice`
   alone. Build from what they gave or chose
   (`create_project` with `choice`, or with `starter` and `colours`, then the
   logo) as its `next` says,
   `deploy_preview`, poll `get_deployment` until it is ready, and call
   `open_site_preview` with the project's id so they see it in the chat.

Never call `deploy_production` during setup. Publishing is only ever done when
the person asks for it.

If they installed Frexy in the middle of another task, finish that task in the
same conversation instead of starting this setup over it.