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