EN FR

Why Kirby CMS and Claude Code are the perfect duo for creative developers

Kirby stores everything in flat files. Claude Code reads those files directly. The result: an AI assistant that truly understands your site — no database, no mapping, no friction.

  • Kirby CMS
  • Claude Code
  • AI
  • workflow
Kirby CMS development interface with Claude Code

There is something elegant about the way Kirby CMS works. No database. No ORM layer. No schema to maintain. Content lives in text files, organised in folders, readable by any editor and by any tool that knows how to read files.

That is where everything changes when you pair Kirby with Claude Code.

An assistant that reads your site the way you do

With a traditional database-driven CMS, an AI assistant is blind to the actual content of the site. It can read the PHP code, the templates, the migrations — but not the data. You have to describe the structure, export dumps, explain relationships.

With Kirby, Claude Code accesses the entire content directly: texts, SEO metadata, page relationships, uploaded files, slugs, publication statuses. Everything is there, in .txt files using a simple key-value format, inside the project tree. Claude sees exactly what Kirby sees.

Claude can read 53 portfolio pages, detect which ones are missing a page_cover field, and suggest fixes in a matter of seconds.

Emmanuel Lechat

Creative freedom as a foundation

Kirby imposes nothing. No predefined page structure, no mandatory theme, no plugin required to do something simple. YAML blueprints define exactly the fields each page type needs, and PHP templates do exactly what you write. The CMS steps back and lets the project speak.

This philosophy resonates directly with how Claude Code works: it does not presuppose an architecture — it observes what exists and adapts to it. It reads the project's conventions before suggesting anything. It can create a blueprint, a template, block snippets, CSS, all while staying consistent with the style already in place.

A concrete workflow

Here is what it looks like in practice. In a single session, Claude Code can: audit all content pages to check for missing SEO fields, create a new page type with its blueprint and template, generate the associated CSS in line with the existing design system, write the initial content in the correct Kirby format, and even retrieve a field from a previous version of the project that you wanted to bring back.

All without leaving the terminal. Without ever opening an admin interface. Without ever writing a SQL query.

What this changes for designer-developers

For profiles that handle both design and code — a common reality in freelance work — the Kirby + Claude Code combination considerably reduces the cognitive overhead of administrative tasks. You stay in the creative flow longer. You delegate repetitive tasks (checking fields, normalising meta descriptions, creating blueprint variations) without losing control.

Kirby stays simple because it is designed to be simple. Claude Code stays relevant because everything is readable. It is a coherence of philosophy as much as of tooling.