AI workflows and CloudCannon 🤝

General
1

A couple of new things:

  1. We’ve published an Agent Skills repo for Astro users, aimed at helping you migrate existing :astro: sites to CloudCannon, in addition to helping you set up visual editing via Editable Regions.

    Check it out at https://github.com/CloudCannon/agent-skills, and let us know how you get on, as we’ll keep updating the skills based on feedback.

  2. I wrote a post thinking through the question of 1. how well your AI agent can actually work with your content. (Obvious) spoiler: it probably comes down to how accessible your code and content is, just one more reason why Git-based is such a solid approach.

If you’re using AI, I’m curious what you’re using: which coding assistants? Cursor / Claude / Copilot / something else? Any particular agents, skills, or workflows that have saved you time?

5 Likes
2

Hey David - I’m currently building a few sites based off the Astro Starter, and was pleasantly surprised when I noticed all those skills show up in the repo. I’m using OpenCode for the most part, but having those skills there as a way to educate the agents on how to structure pages and create/edit components is really helpful.

I have a workflow question for you though… as a developer, being able to point an agent at a repo is great, but one of the main draws of CloudCannon is being able to give our non-developer users the ability to edit a site without needing access to the code repo. Is there (going to be) any way to enable those users to interact with a CloudCannon project via AI, and be able to do things like build out pages with components, do bulk SEO metadata updates, or even a global search-replace? That would be pretty powerful…

3 Likes
3

Hi Michael, great to hear the skills have been helpful! Feel free to open issues or discussions on them if you like :slight_smile:

To your question: our current focus is squarely on making sure devs and site owners get up and running faster with CloudCannon. It’s how we think we can make the biggest difference for agencies who, for example, might need to quickly rescue a portfolio of sites and stand them up in a new CMS. But down the line, we’ll definitely be looking at how to make a content editor’s workflows more efficient.

We don’t currently have firm (i.e. roadmapped) plans on adding non-dev AI features to CloudCannon. I agree those would be powerful features to have (metadata updates in particular would be really helpful), but there the risk/reward equation skews towards the riskier side when you start involving AI and users who tend towards the non-technical.

Always happy to hear more thoughts though!

2 Likes