From e5f170b9b004ecb573eda9831165bfa9cb175f6f Mon Sep 17 00:00:00 2001
From: MrTango <md@derico.de>
Date: Fri, 22 May 2026 04:06:26 -0700
Subject: [PATCH 1/3] Add template-question catalogue to plonecli skill

Add reference/templates.md cataloguing every copier-template question
(keys, defaults, choices, conditional and computed answers, required
keys) so the skill builds non-interactive --defaults -d invocations
without guessing or hitting prompts.

Strengthen SKILL.md description and add a scaffold-don't-hand-write rule
so the skill triggers when a plan decides to create a behavior or other
feature. Wire the new reference into add.md and create.md.
---
 plonecli/skills/plonecli/SKILL.md             |   5 +-
 plonecli/skills/plonecli/reference/add.md     |   4 +-
 plonecli/skills/plonecli/reference/create.md  |   2 +-
 .../skills/plonecli/reference/templates.md    | 293 ++++++++++++++++++
 4 files changed, 300 insertions(+), 4 deletions(-)
 create mode 100644 plonecli/skills/plonecli/reference/templates.md

diff --git a/plonecli/skills/plonecli/SKILL.md b/plonecli/skills/plonecli/SKILL.md
index 0ae5e84..6a31bb8 100644
--- a/plonecli/skills/plonecli/SKILL.md
+++ b/plonecli/skills/plonecli/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: plonecli
-description: Scaffold and develop Plone packages with plonecli (copier-template based). Use for any plonecli command (create, add, setup, serve, test, debug, update, config) and whenever working on Plone add-on features: creating a backend add-on or Zope project; adding a content type, behavior, view, viewlet, portlet, vocabulary, indexer, subscriber, control panel, form, theme, or any other subtemplate; scaffolding an upgrade step / GenericSetup migration after changing profile XML (catalog, types, workflows, registry, rolemap) so it reaches already-installed sites; adapting an old/legacy package (mr.bob/bobtemplates, buildout, setup.py) to the structure plonecli's templates need; running/testing/reconfiguring a generated project. Triggers on "plonecli ...", "create a Plone addon", "add a content type / behavior / restapi service", "add upgrade_step", "migrate already-installed Plone sites", "use plonecli on an old/legacy package", "convert setup.py / buildout addon to plonecli", "zope-setup".
+description: Scaffold and develop Plone packages with plonecli (copier-template based). Use this BEFORE hand-writing any Plone add-on code — including when a plan or task step decides to create/implement a Plone feature such as a behavior, content type, view, viewlet, portlet, vocabulary, indexer, subscriber, control panel, form, REST API service, theme, or upgrade step. Scaffold these with plonecli subtemplates instead of writing files by hand. Also for any plonecli command (create, add, setup, serve, test, debug, update, config); creating a backend add-on or Zope project; scaffolding a GenericSetup upgrade step after profile XML changes so they reach installed sites; adapting an old/legacy package (mr.bob, buildout, setup.py) to plonecli's structure. Triggers on "plonecli ...", "create a Plone addon", "add/create/implement a behavior (or content type / restapi service / ...)", "add upgrade_step", "migrate installed Plone sites", "zope-setup". The -d KEY=VALUE answers each template accepts are in reference/templates.md.
 ---
 
 # plonecli
@@ -43,7 +43,8 @@ On first run, plonecli clones the copier-templates to `~/.copier-templates/plone
 
 ## Critical rules
 
-- **`create`/`add` are interactive by default — always run them non-interactively here.** copier opens prompts you cannot answer in Claude Code / CI (they hang or fail). Pass `--defaults` (use template defaults for unasked questions) plus `-d/--data KEY=VALUE` (repeatable) for each answer the user specified — or `--data-file PATH` for a YAML/JSON file of answers (`-d` overrides matching keys). Required answers without a default (`content_type_name`, `behavior_name`, `service_name`, `upgrade_step_title`) **must** be given via `-d`. Example: `plonecli add upgrade_step --defaults -d upgrade_step_title="Reimport viewlets"`. **Never give up on a prompt and hand-write the files the subtemplate would generate** — drive plonecli non-interactively instead. Don't invoke `copier` directly. See [reference/add.md](reference/add.md).
+- **Scaffold Plone features with plonecli — don't hand-write them.** The moment a task or plan calls for a behavior, content type, view, viewlet, portlet, vocabulary, indexer, subscriber, control panel, form, REST API service, theme, upgrade step, or any other Plone artifact, the first step is `plonecli add <subtemplate>` (inside the addon), not creating `.py`/`.zcml`/`.xml` files by hand. The templates wire up registration, profiles, and tests correctly; hand-rolled files miss those. Only fall back to manual edits for the legacy-package case below, and even then only the minimal hooks plonecli needs.
+- **`create`/`add` are interactive by default — always run them non-interactively here.** copier opens prompts you cannot answer in Claude Code / CI (they hang or fail). Pass `--defaults` (use template defaults for unasked questions) plus `-d/--data KEY=VALUE` (repeatable) for each answer the user specified — or `--data-file PATH` for a YAML/JSON file of answers (`-d` overrides matching keys). Required answers without a default (`content_type_name`, `behavior_name`, `service_name`, `upgrade_step_title`) **must** be given via `-d`. **The full catalogue of every template's `-d` keys, defaults, choices, conditional/computed answers and which are required is [reference/templates.md](reference/templates.md)** — consult it to build the invocation instead of guessing or triggering a prompt. Example: `plonecli add upgrade_step --defaults -d upgrade_step_title="Reimport viewlets"`. **Never give up on a prompt and hand-write the files the subtemplate would generate** — drive plonecli non-interactively instead. Don't invoke `copier` directly. See [reference/add.md](reference/add.md).
 - **Never start the dev server yourself.** Do not run `plonecli serve` / `plonecli debug` / `invoke start`. Assume the instance is already running; if it is not, ask the user to start it. (`plonecli test` is fine to run.)
 - **Use native `uv`.** Run things as `uv run <command>`; never `uv pip` or `pip` unless explicitly told.
 - **Tests must pass — never skip them.** After scaffolding or adding a feature, run `plonecli test` and report real results.
diff --git a/plonecli/skills/plonecli/reference/add.md b/plonecli/skills/plonecli/reference/add.md
index c25c6f7..fb7be5a 100644
--- a/plonecli/skills/plonecli/reference/add.md
+++ b/plonecli/skills/plonecli/reference/add.md
@@ -26,7 +26,9 @@ plonecli add behavior --defaults -d behavior_name="IFeatured"
 plonecli add restapi_service --defaults -d service_name="@todos"
 ```
 
-Pass `-d` for every answer the user has specified; `--defaults` covers the rest. Required answers that have no default (e.g. `content_type_name`, `behavior_name`, `service_name`, `upgrade_step_title`) **must** be supplied with `-d` or copier still has to prompt. Don't invent values the user hasn't given — ask first, then pass them via `-d`. The per-template question/answer keys are listed below and shown by the prompts themselves.
+Pass `-d` for every answer the user has specified; `--defaults` covers the rest. Required answers that have no default (e.g. `content_type_name`, `behavior_name`, `service_name`, `upgrade_step_title`) **must** be supplied with `-d` or copier still has to prompt. Don't invent values the user hasn't given — ask first, then pass them via `-d`.
+
+**The complete `-d KEY=VALUE` reference for every template — keys, defaults, choices, conditional `when` questions, computed/hidden keys you must not pass, and which answers are required — is [templates.md](templates.md).** Use it to assemble the command up front; the prompts also echo the same keys.
 
 ## Subtemplates are gated by project type
 
diff --git a/plonecli/skills/plonecli/reference/create.md b/plonecli/skills/plonecli/reference/create.md
index 385c534..2dd378f 100644
--- a/plonecli/skills/plonecli/reference/create.md
+++ b/plonecli/skills/plonecli/reference/create.md
@@ -6,7 +6,7 @@ plonecli create addon collective.todo            # backend add-on + zope-setup (
 plonecli create zope-setup my-project            # Zope project setup
 ```
 
-Like `add`, `create` is interactive by default. In Claude Code / CI run it non-interactively with `--defaults` (use template defaults) plus `-d/--data KEY=VALUE` for any answer you want to set, e.g. `plonecli create backend_addon collective.todo --defaults -d package_description="Todo manager"`. Do not call `copier` directly.
+Like `add`, `create` is interactive by default. In Claude Code / CI run it non-interactively with `--defaults` (use template defaults) plus `-d/--data KEY=VALUE` for any answer you want to set, e.g. `plonecli create backend_addon collective.todo --defaults -d package_description="Todo manager"`. Do not call `copier` directly. The `-d` keys each project template accepts (`backend_addon`, `zope-setup`, the `addon` composite) — defaults, choices, and conditional questions like `db_storage`/`distribution` — are catalogued in [templates.md](templates.md).
 
 ## Project templates
 
diff --git a/plonecli/skills/plonecli/reference/templates.md b/plonecli/skills/plonecli/reference/templates.md
new file mode 100644
index 0000000..97136ec
--- /dev/null
+++ b/plonecli/skills/plonecli/reference/templates.md
@@ -0,0 +1,293 @@
+# Template questions — what `-d KEY=VALUE` answers each template accepts
+
+This is the authoritative catalogue of every copier-template question, so you can build the
+non-interactive `--defaults -d KEY=VALUE …` invocation **without** triggering a prompt and
+**without** guessing. It is derived from the templates' `copier.yml`. The live source of truth is
+still the templates clone (`~/.copier-templates/plone-copier-templates/<template>/copier.yml`); run
+`plonecli -l` to see which templates/subtemplates apply where.
+
+## How to read these tables
+
+- **Required** (shown as `**required**` in the Default column) = the question has a validator and
+  **no usable default** → you **must** pass it with `-d`, or copier still prompts (and hangs in
+  Claude Code / CI). Only four keys are truly required: `behavior_name`, `content_type_name`,
+  `service_name`, `upgrade_step_title`.
+- **name†** = the subtemplate's primary identifier. It *has* the default shown (so `--defaults`
+  won't prompt), but that default is a generic placeholder (`my-view`, `Weather`, …) — you'll almost
+  always set it via `-d` to a real name. Its validator only rejects an empty value.
+- **Default** = used when you omit the key under `--defaults`. Pass `-d KEY=VALUE` only to change it.
+- **Choices** = the only accepted values (copier rejects others).
+- **Conditional (`when`)** = the question only appears when another answer has a given value. To set
+  it you must also set the controlling answer (e.g. `parent_content_type` needs `global_allow=false`).
+- **Computed / hidden** keys (PascalCase→snake_case module names, interfaces, etc.) are derived
+  automatically — **do not pass them**; they are listed only so you understand what gets generated.
+- Booleans: pass `-d key=true` / `-d key=false`.
+
+Golden rule: pass `--defaults` plus a `-d` for **every** answer the user actually specified, **plus**
+every Required key. Don't invent values the user hasn't given — ask, then pass them via `-d`.
+
+---
+
+## Create templates (project-level — `plonecli create <template> <name>`)
+
+### `backend_addon` — Plone backend add-on package
+
+The `<name>` positional becomes the default `package_name`, so `package_name` is effectively
+satisfied; everything else has a default.
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `package_name` | the project dir name (or legacy package name) | Python package, e.g. `collective.todo`. |
+| `package_title` | derived from `package_name` | Human-readable title. |
+| `package_description` | "A Plone addon package" | |
+| `plone_version` | newest supported minor | choices: the supported Plone minor versions (`PloneVersionsHook`). |
+| `is_headless` | `false` | bool — headless/API-only addon. |
+| `author_name` | "Plone Developer" | |
+| `author_email` | "dev@plone.org" | |
+
+Hidden/computed: `package_folder`, `namespace_parts`, `package_module`, `browser_layer_name`,
+`current_year`, `current_date`.
+
+### `zope-setup` (alias `project`) — runnable Plone/Zope project
+
+When applied standalone, asks project identity; when applied **on top of an addon** (`addon`
+composite or `plonecli setup`), identity + `base_path`/`db_storage` are read from the addon context
+and those questions are skipped (`when: not addon_context`).
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `project_name` | from addon context, else **required** | only asked when not run on an addon. |
+| `project_title` | derived | only when not on an addon. |
+| `project_description` | "A Plone project" | only when not on an addon. |
+| `plone_version` | newest full version | choices: supported full Plone versions. |
+| `distribution` | `plone.volto` | choices: `plone.volto`, `plone.classicui`. |
+| `base_path` | `var` | runtime dir; only when not on an addon. |
+| `db_storage` | `instance` | choices: `instance`, `relstorage`, `zeo`; only when not on an addon. |
+| `zeo_address` | `localhost:8100` | only when `db_storage=zeo`. |
+| `pg_host` | `localhost` | only when `db_storage=relstorage`. |
+| `pg_port` | `5432` | only when `db_storage=relstorage`. |
+| `pg_dbname` | `plone_<project_name>` | only when `db_storage=relstorage`. |
+| `pg_user` | `plone` | only when `db_storage=relstorage`. |
+| `pg_password` | "" (secret) | only when `db_storage=relstorage`. |
+| `author_name` | "Plone Developer" | |
+| `author_email` | "dev@plone.org" | |
+| `initial_zope_username` | `admin` | |
+| `initial_user_password` | `admin` (secret) | |
+
+### `addon` (alias `add-on`) — composite
+
+No own questions: it applies `backend_addon` then `zope-setup` in sequence. Pass the `-d` keys for
+both layers in one `create addon` call. Do **not** also run `plonecli setup` afterward.
+
+---
+
+## `backend_addon` subtemplates (`plonecli add <sub>` inside an addon)
+
+Every subtemplate also reads `package_name` / `package_folder` from the parent addon — you normally
+don't pass those.
+
+### `behavior` — Dexterity behavior
+
+| Key | Default | Notes |
+|---|---|---|
+| `behavior_name` | **required** | interface name, e.g. `IFeatured`, `ITaggable`. A leading `I` is added if missing. |
+| `behavior_description` | "A custom Dexterity behavior" | |
+
+Hidden/computed: `behavior_interface`, `behavior_module`, `behavior_class`. `behavior_marker` /
+`behavior_factory` exist but are `when: false` (both default `true`); override only via
+`-d behavior_marker=false` etc. if you really need to.
+
+Example: `plonecli add behavior --defaults -d behavior_name="IFeatured"`
+
+### `content_type` — Dexterity content type
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `content_type_name` | **required** | e.g. `Talk`, `News Item`. |
+| `content_type_description` | "A custom content type" | |
+| `content_type_base` | `Container` | choices: `Container`, `Item`. |
+| `content_type_icon` | `puzzle` | Bootstrap icon name (e.g. `file-earmark`, `folder`, `newspaper`). |
+| `global_allow` | `true` | bool — globally addable? |
+| `parent_content_type` | `Folder` | choices come from the addon's known portal types plus `<enter manually>`; only when `global_allow=false`. |
+| `parent_content_type_manual` | "" | only when `global_allow=false` **and** `parent_content_type=<enter manually>`. |
+| `filter_content_types` | `true` | only when `content_type_base=Container`. |
+| `activate_default_behaviors` | `true` | standard Plone behaviors bundle. |
+| `enable_dublin_core` | `true` | only when `activate_default_behaviors=false`. |
+| `enable_navigation` | `true` | only when `activate_default_behaviors=false`. |
+
+Hidden/computed: `content_type_class`, `content_type_module`, `content_type_interface`,
+`content_type_portal_type`, `parent_content_type_resolved`.
+
+Example (containment): `plonecli add content_type --defaults -d content_type_name="Talk" -d global_allow=false -d parent_content_type="Folder"`
+
+### `restapi_service` — `plone.restapi` endpoint
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `service_name` | **required** | endpoint name, e.g. `stats`, `my-endpoint`. |
+| `service_description` | "A custom REST API endpoint" | |
+| `expandable` | `false` | add `IExpandableElement` adapter (extends `@search` etc.). |
+| `http_get` | `true` | |
+| `http_post` | `false` | |
+| `http_patch` | `false` | |
+| `http_delete` | `false` | |
+| `service_for` | `plone.dexterity.interfaces.IDexterityContainer` | choices: `…IDexterityContainer`, `…IDexterityContent`, `Products.CMFPlone.interfaces.IPloneSiteRoot`, `zope.interface.Interface`. |
+
+Hidden/computed: `service_module`, `service_class`, `service_endpoint`.
+
+### `view` — BrowserView (optional page template)
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `view_name` | `my-view` (name†) | URL id, used as `@@my-view`. |
+| `view_class_name` | `MyView` | PascalCase Python class. |
+| `view_base_class` | `BrowserView` | choices: `BrowserView`, `DefaultView`, `CollectionView`. |
+| `view_template` | `true` | also generate a `.pt`? |
+| `view_for` | `*` | choices: addon content-type interfaces + `*` + `<enter manually>`. |
+| `view_for_manual` | `*` | only asked when `view_for=<enter manually>`; must be non-empty. |
+| `view_marker` | `false` | generate a marker interface? |
+| `view_description` | "A custom browser view" | |
+
+Hidden/computed: `view_for_interface`, `view_module`.
+
+### `viewlet` — `browser:viewlet`
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `viewlet_name` | `myviewlet` (name†) | lowercase identifier. |
+| `viewlet_class_name` | `MyViewlet` | PascalCase. |
+| `viewlet_manager` | `plone.portalheader` | choices: the standard Plone viewlet managers (`plone.htmlhead`, `plone.portaltop`, `plone.portalheader`, `plone.portalfooter`, `plone.abovecontent`, `plone.belowcontent`, `plone.portalleftcolumn`, `plone.portalrightcolumn`, … — see `copier.yml` for the full list). |
+| `viewlet_for` | `*` | interface or `*`. |
+| `viewlet_template` | `true` | also generate a `.pt`? |
+| `viewlet_description` | "A custom viewlet" | |
+
+Hidden/computed: `viewlet_module`.
+
+### `portlet` — classic Plone portlet
+
+| Key | Default | Notes |
+|---|---|---|
+| `portlet_name` | `Weather` (name†) | PascalCase display name. |
+| `portlet_description` | "A custom portlet" | |
+
+Hidden/computed: `portlet_module`.
+
+### `vocabulary` — named vocabulary (`IVocabularyFactory`)
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `vocabulary_name` | `AvailableThings` (name†) | PascalCase class name. |
+| `vocabulary_description` | "A custom named vocabulary" | |
+| `vocabulary_type` | `simple` | choices: `simple` (SimpleTerm list), `catalog` (StaticCatalogVocabulary). |
+
+Hidden/computed: `vocabulary_class`, `vocabulary_module`.
+
+### `indexer` — catalog indexer (`@indexer`)
+
+| Key | Default | Notes |
+|---|---|---|
+| `indexer_name` | `my_custom_index` (name†) | snake_case Python identifier. |
+| `indexer_description` | "A custom catalog indexer" | |
+
+### `subscriber` — zope event subscriber
+
+| Key | Default | Notes |
+|---|---|---|
+| `subscriber_handler_name` | `obj_modified_do_something` (name†) | snake_case handler/module name. |
+| `subscriber_event` | `zope.lifecycleevent.interfaces.IObjectModifiedEvent` | dotted event interface. |
+| `subscriber_for` | `plone.dexterity.interfaces.IDexterityContent` | dotted context interface. |
+| `subscriber_description` | "A custom event subscriber" | |
+
+### `controlpanel` — registry-backed settings form
+
+| Key | Default | Notes |
+|---|---|---|
+| `controlpanel_name` | `MyFeatured` (name†) | PascalCase base name. |
+| `controlpanel_title` | = `controlpanel_name` | shown in Plone's control-panel list. |
+| `controlpanel_description` | "A custom control panel" | |
+
+Hidden/computed: `controlpanel_module`, `controlpanel_url_id`.
+
+### `form` — `z3c.form`-based form
+
+| Key | Default | Notes |
+|---|---|---|
+| `form_name` | `my-form` (name†) | URL id, invoked as `@@my-form`. |
+| `form_class_name` | `MyForm` | PascalCase. |
+| `form_for` | `*` | interface or `*`. |
+| `form_description` | "A custom form" | |
+
+Hidden/computed: `form_module`.
+
+### `upgrade_step` — GenericSetup upgrade step
+
+| Key | Default | Notes |
+|---|---|---|
+| `upgrade_step_title` | **required** | e.g. "Add catalog index". |
+| `upgrade_step_description` | "A custom upgrade step" | |
+| `source_version` | current `metadata.xml` version (injected) | upgrade **from**. |
+| `destination_version` | `source + 1` | upgrade **to**. |
+
+See [add.md](add.md) for the full upgrade-step workflow (fill the handler, add a test).
+
+### `site_initialization` — site init registry records
+
+| Key | Default | Notes |
+|---|---|---|
+| `site_name` | `New Plone Site` (name†) | site title in header/tab. |
+| `language` | `en` | ISO 639-1 two-letter code. |
+
+### `mockup_pattern` — Mockup JS pattern scaffold
+
+| Key | Default | Notes |
+|---|---|---|
+| `pattern_name` | `my-pattern` (name†) | without the `pat-` prefix. |
+| `pattern_description` | "A custom Mockup JS pattern" | |
+
+### `theme` — full Diazo theme (scss partials + webpack)
+
+| Key | Default | Notes |
+|---|---|---|
+| `theme_name` | `My Theme` (name†) | shown in the theming control panel. |
+| `theme_description` | "A custom Plone theme" | |
+
+Hidden/computed: `theme_id`.
+
+### `theme_barceloneta` — Barceloneta-based theme variant
+
+Same keys as `theme` (`theme_name` is the name† key, `theme_description` defaults to "A Barceloneta-based
+Plone theme"); hidden `theme_id`.
+
+### `theme_basic` — minimal basic theme
+
+Same keys as `theme` (`theme_name` is the name† key, `theme_description` defaults to "A basic Plone theme");
+hidden `theme_id`.
+
+### `svelte_app` — Svelte app scaffold (vite + Python mount view)
+
+| Key | Default | Notes |
+|---|---|---|
+| `svelte_app_name` | `my-svelte-app` (name†) | kebab-case. |
+| `svelte_app_description` | "A custom Svelte application" | |
+| `svelte_app_custom_element` | `false` | compile as a Web Component? |
+
+Hidden/computed: `svelte_app_module`, `svelte_app_class`.
+
+---
+
+## `zope-setup` subtemplates (`plonecli add <sub>` inside a project)
+
+### `zope_instance` — additional named Zope instance
+
+| Key | Default | Choices / notes |
+|---|---|---|
+| `instance_name` | `instance` (name†) | dir name, e.g. `instance1`, `zeo-client1`. |
+| `port` | `8080` | HTTP port. |
+| `base_path` | from project context, else `var` | runtime dir. |
+| `db_storage` | from project context, else `instance` | choices: `instance`, `relstorage`, `zeo`. |
+| `zeo_address` | `localhost:8100` | only when `db_storage=zeo`. |
+| `pg_host` / `pg_port` / `pg_dbname` / `pg_user` / `pg_password` | as in zope-setup | only when `db_storage=relstorage`. |
+| `initial_zope_username` | `admin` | |
+| `initial_user_password` | `admin` (secret) | |
+
+Hidden/computed: `project_name`, `instance_home`.

From c6eec51f76f304e39f5e9078a0d68c50d899d880 Mon Sep 17 00:00:00 2001
From: MrTango <md@derico.de>
Date: Fri, 22 May 2026 17:15:30 +0300
Subject: [PATCH 2/3] Add changelog entry for template-question catalogue

---
 CHANGES.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/CHANGES.md b/CHANGES.md
index dec5ff9..08632f0 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -3,7 +3,12 @@
 ## 7.0.0b8 (unreleased)
 
 
-- Nothing changed yet.
+- Add `reference/templates.md` to the bundled plonecli skill, cataloguing every
+  copier-template question (keys, defaults, choices, conditional and computed
+  answers, required keys) so the skill builds non-interactive `--defaults -d`
+  invocations without guessing or hitting prompts. Strengthen the skill
+  description and add a scaffold-don't-hand-write rule.
+  [MrTango]
 
 
 ## 7.0.0b7 (2026-05-22)

From e11c8eb2e99ef329c98e891bcc769d7b3313efc4 Mon Sep 17 00:00:00 2001
From: MrTango <md@derico.de>
Date: Fri, 22 May 2026 17:17:00 +0300
Subject: [PATCH 3/3] update claude instructions

---
 CLAUDE.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/CLAUDE.md b/CLAUDE.md
index 44d7ca8..69325a0 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -5,3 +5,4 @@
 - if changes on the devcontainer setup are needed, do it in the copier template "/home/maik/develop/src/copier-claude-code-devcontainer/" and apply the template again.
 - keep commit and changelog messages lean, focus on facts
 - don't create a manual test plan in PR description, create real test which are run in the CI!
+- keep commit message and PR description lean