Open-source starter kit for building solid web apps with your AI agent.

Drubricks is a free starter kit on Drupal 12. Tell your AI agent what the system is for, and it builds one from proper Drupal parts: data, access rules, screens, demo data and tests.

  • Drupal 12
  • PHP 8.5
  • HTMX 4, no React or Vue
  • 75 UI components
  • GPL
Paste into Claude Code, Codex, OpenCode or any coding agent, in an empty folder

Based on Drubricks (https://github.com/drubricks/drubricks) build me a system to manage the teachers and clients of a language school.

Video

See Drubricks in action.

A walk through the starter: the apps, the screens and how an agent builds on it.

What you start from

A real app on day one, not a blank page.

This is the starter with its three example apps installed. Your system gets the same shell, the same components and the same screens, in its own records.

your-project.ddev.site/apps
Drubricks: Dashboard (Dark)

How it works

One prompt. Four steps. Your own system.

The agent follows AGENTS.md in the repository. You answer a few questions and review the result.

  1. 01

    You describe the system

    The agent asks 3 to 7 questions before it writes any code: roles and who sees what, the records and their fields, the main views, the rules to enforce, language, currency, name, logo, colours and demo data.

    • Who works in it, and what can each role see?
    • Lists, a board, a calendar, a dashboard?
    • Which rules must never break?
  2. 02

    It starts your own project

    It clones the starter and runs the launcher in your-own-project mode: a new git repository, the base installed, the example apps kept in the code as references.

    ./launch-drubricks.sh --own-project --apps=
  3. 03

    It builds your modules

    Your system is written as modules of its own, modelled on the bundled examples: one for a small system, several cooperating ones (sales, inventory, HR) for an ERP-sized one. Each comes with recipes, demo data and tests, and the agent installs it and checks it.

    web/modules/custom/<prefix>_<name>
  4. 04

    You open the site

    Log in and it works. Later prompts change it the same way: “add invoices”, “teachers see only their lessons”. The owner can add fields in the admin UI without code, and the screens show them.

    ddev launch

Why a starter

Agents are great builders. They need a frame to build in.

On a blank framework an agent invents the structure from scratch every time. Drubricks gives it Drupal’s slots to fill, so the same kind of request produces the same kind of code.

Isometric plate with recessed slots: two blocks sit in their slots, a third hovers above an empty one.

Blank framework + agent

  • A new architecture with every prompt
  • Login, roles and record access written by hand, again
  • Front end, back end and an API between them to keep in sync
  • No admin UI: every field change is a code change
  • Works in the demo, gets harder to change every month

Drubricks + agent

  • Entities, fields, access handlers, plugins, recipes: defined slots
  • Access checks, CSRF, escaping and SQL safety come from core
  • One app: PHP renders the screens, HTMX swaps them in place
  • Roles, Field UI, Views and menus without code
  • AGENTS.md and a review skill keep each change the Drupal way

What is inside

The bricks

Everything a business app needs before the first feature is written. Once you start your project, it is all your code: no upgrade path and nothing to keep in sync.

  • drubricks_core

    The app engine

    Base entity with owner, dates, status, colour and revisions. Own/any permissions and record-level access. The list + details + inspector screen with modal forms, boards, calendars and tables. HTMX helpers, dashboard blocks, per-record logs.

  • theme

    75 components

    The UI kit’s app shell as single-directory components. Drupal forms in the kit look. Logo, name and palette in the theme settings. Light, dark and auto.

  • example

    CRM

    Companies, contacts, deals. A validation rule, a dependent field, delete blockers.

  • example

    Projects

    Projects with members, tasks, a drag-and-drop board. Users see only their own projects.

  • example

    Booking

    Rooms, cars, equipment and people in a week calendar. No double bookings, opening hours.

  • AGENTS.md

    The agent’s manual

    How to start a new system from a prompt, the conventions, and a drupal-way-review skill that checks every change.

  • installer

    Recipes

    Base recipe, then pick apps, each with its demo data. The profile removes itself.

  • admin

    Admin tools

    Navigation, Gin Login, Masquerade, Config Log, Project Browser.

  • CI

    Checks

    phpcs, PHPStan, PHPUnit and Playwright, plus an install with every app.

Stack

Current versions, all the way down.

No legacy to drag along. A new project starts on the newest releases of everything it stands on.

  • Drupal12.0The framework: entities, access, admin UI, recipes
  • PHP8.5The language, with property hooks and the pipe operator
  • Symfony8.1Routing, HTTP kernel and services under Drupal core
  • HTMX4.0In Drupal core: swaps screens without page reloads
  • MariaDB10.11The database; MySQL and PostgreSQL work too
  • Guzzle8.0The HTTP client for integrations and APIs
  • PHPUnit12.5Unit, kernel and functional tests

Why Drupal

Boring where it matters.

Business systems live for years, hold data that matters and get changed by many hands, more and more of them AI agents. Drupal was built for that.

  1. 01

    Secure

    A dedicated security team, coordinated advisories and long-supported releases. Banks, governments and universities run on it.

  2. 02

    A simple stack

    PHP renders, HTMX swaps. No headless split, no second build and deploy, no client state to keep in sync.

  3. 03

    Runs anywhere

    PHP with MySQL, MariaDB or PostgreSQL, from a cheap shared plan to Kubernetes. No Node.js server in production.

  4. 04

    A harness for agents

    The framework limits what an agent can get wrong. Every entity gets the same admin UI, and the same tests run.

  5. 05

    Admin UI included

    Roles and permissions, Field UI, Views, menus, revisions, translations. The owner changes things without a developer.

  6. 06

    Proven for 20+ years

    Developed since 2001 by one of the largest open source communities, with thousands of modules for SSO, workflows and search.

  7. 07

    Multilingual, accessible

    The interface is translated into 100+ languages, and WCAG accessibility is a requirement for core changes.

  8. 08

    No lock-in

    GPL, no licence fees, no platform to rent. The code and the data are yours.

Quickstart

Start in an empty folder.

Let the agent do it, or run it by hand to look around the examples first.

A

By prompt

Open Claude Code, or another agent that reads AGENTS.md, in an empty folder and describe your system, naming the repository.

Based on Drubricks (https://github.com/drubricks/drubricks) build me a system to manage the teachers and clients of a language school.

The agent asks its questions, clones, builds, installs and gives you a login.

B

By hand

Clone into a folder named after your project and run the launcher. It sets up DDEV, installs Composer packages and asks how you want to install.

git clone https://github.com/drubricks/drubricks.git my-project
cd my-project
./launch-drubricks.sh
ddev launch

You need

  • DDEV 1.25 or newer
  • Docker Desktop, OrbStack or Colima
  • Git
  • Nothing else on the host: PHP 8.5, Composer and the database run in DDEV

Launcher without questions

./launch-drubricks.sh --own-project --apps=
Your own project, base only. The start of a system built by prompt.
./launch-drubricks.sh --own-project
Your own project with every example app installed.
./launch-drubricks.sh -y
The starter itself, for contributing. Starter files kept.

FAQ

Questions

Do I need to know Drupal?

Not to get started. The agent follows AGENTS.md and models its modules on the bundled examples. The code it writes is standard Drupal, so any Drupal developer can review it or take it over later.

Is it really free?

Yes. Drubricks is open source under the GPL, like Drupal. There is no paid tier and no licence fee. The code and the data are yours.

Which AI agents does it work with?

It is made and tested with Claude Code. The instructions live in AGENTS.md, a plain file that other coding agents read too.

How do I update my project when Drubricks changes?

You don’t, by design. Once you start, the starter’s code becomes your project’s code, and there is nothing to keep in sync. Drupal core and contributed modules update with Composer as usual.

Which Drupal version does it use, and how do I update it?

Drubricks is built on Drupal 12. Drupal core and contributed modules update with Composer, like in any Drupal project, and your project keeps receiving Drupal's security releases.

Where can I host it?

Anywhere that runs PHP with MySQL, MariaDB or PostgreSQL. Production needs no Node.js: Node only builds the theme CSS, and the built CSS is committed. Locally everything runs in DDEV.

Is there a React or Vue front end?

No. Drupal renders the screens and HTMX swaps them without full page reloads. For the odd interactive widget there are JSON API helpers for small JavaScript islands.

Can I add fields without code?

Yes. Application → Entity structure → Manage fields. The app’s forms and record details show new fields on their own.

Your next system is one prompt away.

Copy the prompt, change the last sentence to describe your business, and paste it into your agent.

GitHub
Isometric wall of blue bricks with one brick being placed on top.