Would be great if you and other folks can try to use the repo, install prerequisites, then run the commands. That is what the presentation is, but making it work for yourself and others is when the real magic will happen 🔮🎪🤹

Such an epic talk, forgot about this. Will add to examine docs. Also v4 beta xzy out soon, lots of good changes and fixes. Still need some feedback from you though 😉

Just submitted a speaker session for Umbraco US Fest this year titled: Automate All the Things: Building & Evolving Umbraco Sites with YOLO-Mode AI Agents 🚀 ... what could go wrong 😅

MCPs are amazing. Here's a good list github.com/modelcontext.... Easy to configure in RooCode. Also saw Matthew Wise created an Umbraco MCP, IMO that is a game changer for sure. You could prob create an amazing Umb app from empty to something pretty awesome very fast without even touching Umbraco.

6. You may find on each iteration it gets something wrong, just tell it to fix it so it understands how to do it correctly next time. You'll be surprised at what it comes up with. Saving all this to a git repo is key. Then you can re-use your prompt engineering, create other modes, instructions, etc

5. When you are ready to execute, use your custom mode, then just say, 'execute your instructions' since it knows about them as part of its mode. It will follow your instructions and rules.

4. Check over all the stuff it created, if some doesn't make sense to you, tell it to update it accordingly, its much easier to make it write your prompts than for you to write them.

3. Basically, get it to write your prompts, rules, instructions, modes. The instructions.md file can ref other prompt files (I put mine in /.roo/prompts). Rules can include things like: always create a git commit after processing a phase, when processing instructions, never edit files in /.roo/*

2. Tell it to configure the roo rules file structure docs.roocode.com/features/cus.... Then tell it to create an instructions.md file with a bit of information about the instructions you want it to do and update your new custom roomode to read this instructions.md file.

1. My tips for this is if you want to re-use things and/or make a prompting system robust. Use RooCode, use Sonnet 3.7/4, create a new workspace in VS, tell it to create you a new roomode: docs.roocode.com/features/cus... for the overview of what you want to achieve.

I've update the PR description with the full details of tools, prompts, etc...
github.com/Shazwazza/Ar... Using the right tools and models is a must, else it will produce bad results. RooCode is awesome, especially when you use a good model and auto-approve actions with git commits.

Indeed! Was an intriguing thought. Our service handles > 500 billion requests per day globally, thinking of the scale for an umbraco site that could do that, but separating those concerns could go a long way within a cluster for even smaller scale sites.

It happened! www.abc.net.au/news/2025-04...

Twerk driven development 😂

Sorry, don't post politics normality but this is all hitting close (on) home.