Claude and Kirby

The CMS Questions
1

Hello.

Been briefing Claude to scaffold out sites, it’s surprisingly effective but found a couple of things interesting.

  • It seems to consistently prefer using Kirby 4 documentation even when it’s stated that Kirby 5 is in use. I wander if the legacy doc’s pages could do with a big notice at that top that has ‘legacy documentation, to view the latest please refer to version 5’ ( or similar )
  • Whilst I’ve found the Kirby video on importing content via the API / CLI really useful, Claude didn’t seem to have any reference to that, and started to built out an importer outside of the framework, just raw creation of files in the content folder via PHP directly. I then gave it a previously coded importer for reference and it picked up the intention. Wander if it’s worth having a transcript or documentation page that accompanies any future videos so AI agents can consume that content too.

Anyone else come across other issues or tips to help agents be more effective?

Thanks.

Ian

2
1 Like
3

Three simple things for me, explicitly state what Kirby version and CSS framework you want to use and ask for advice on security and hardening deployments for your specific project. The Claude code looks clean and is well commented but you have to watch out for typos particularly missing hyphens in query strings. It’s one possible way to accelerate your learning.

4

Interesting @bnomei will give it a try.

@oppfield For the version, it’s just odd as its’ reviewing composer and installing plugins as part of the brief, so it definately should know its’ a kirby 5 install, then it seems to revert back to referencing kirby 4 documentation at later points.

I’m always reviewing what it’s generating. It’s still surprising that it fails seemingly basic things and then completes something quite complex!

I treat it like a junior dev, that is surprisingly well read :slight_smile: