Loading...
Loading...
Found 11 Skills
Use when calling the CloudCannon API from code — constructing a client, finding a site or organisation UUID, reading or writing files on a hosted site programmatically, triggering and inspecting builds, or reaching a CloudCannon endpoint the CLI has no command for (DAMs, backups, sync history, site scans, screenshots, provider connections, copying or deleting a site).
Use when running a CloudCannon site locally with `cloudcannon dev` — starting the local editing loop so the user can edit in the CloudCannon editor and see the site rebuild, choosing the build command per SSG, and reading the `/__api` surface the server exposes.
Use when a CloudCannon site uses Bookshop — `*.bookshop.yml` files, `@bookshop/*` packages, `_bookshop_name` keys, `bookshop:live`, or `partial "bookshop"` calls or `{% bookshop %}` tags. Covers how Bookshop works, maintaining a site that stays on it, and migrating it to editable regions.
Use when adding Visual Editor support to a CloudCannon site, setting up editable regions, debugging visual editing issues, or making page sections editable in the CloudCannon preview.
Use when running the CloudCannon CLI — logging in, listing or creating sites, reading and writing files on a hosted site, triggering and inspecting builds, changing a site's build configuration, reading form submissions, or finding out which command and flags exist for a task.
Get a site ready for Rosey translation, with the CloudCannon connector (RCC) as an optional visual-editing layer. Use when the user wants to add multilingual support, internationalize a site, set up Rosey, replace an existing i18n system (astro-i18n, next-intl, path-based routing, etc.), or upgrade from RCC v1 to v2.
Structured design dialogue before CloudCannon work that has more than one sensible answer — a migration's editability tradeoffs, how to model a collection or page builder, restructuring content or config, or an ambiguous "make this work with CloudCannon". Explores intent and constraints, then presents a design for approval before implementation. Not for single well-defined tasks, clear bug fixes, or a detailed spec.
Use when adding snippet support to a CloudCannon site, configuring MDX components, Hugo shortcodes or Eleventy shortcodes and includes for the Content Editor, debugging snippet round-trip issues, or setting up inline HTML snippets in markdown content.
Migrate an existing SSG site to work with CloudCannon. Use when the user wants to onboard a site to CloudCannon, add CMS support, or make a template CloudCannon-compatible.
Use when configuring a site for CloudCannon for any of the following. Download the JSON schemas before writing any configuration (see the top of SKILL.md). - Setting up cloudcannon.config.yml or .cloudcannon/initial-site-settings.json - Generating a baseline with the CloudCannon CLI - Adding or modifying Collections, Inputs, Structures, or Select Data - Setting up Structures for Array and Object Inputs - Configuring Collection URLs - Troubleshooting missing fields or Input types
Translate a multilingual site with AI. Covers Rosey locale JSON files (untranslated + stale entries) and per-locale content directories (MDX/MD with frontmatter: split-by-directory collections, or a Hugo site's content_fr/). Use when the user wants to translate locale files, fill in missing translations, update stale translations, bulk-translate a locale, or translate per-locale content directories (blog_fr/, content_fr/).