@bettercms-ai/mcp 0.18.0 → 0.20.0

package/SKILL.md

@@ -16,13 +16,23 @@ behind them.
 - **Additive where possible.** `add_field`/`add_page_field` append; passing `fields`
   to `update_form` or `blockJson` to `update_component` REPLACES — include everything
   you want to keep.
+- **Drafts are invisible.** A component you create is a DRAFT, and a draft component
+  renders as an empty string on the live site — no error, no placeholder. Call
+  `publish_component` on every component you place, then publish the page.
 
 ## Pages & schema
-Design the project's schema from its code — the connected repo, or, for an uploaded
-project, its source in your working directory. Destructure each page into a tree:
-plain fields, **group** (one nested object), **repeater** (a repeatable array). Then
-`create_page` per page. (See the `propose_schema` prompt.) Pages created here show up
-in the dashboard Content tab.
+Decide the architecture before the first call. A marketing site is **components-first**:
+a library of `create_component` sections, each with a `sectionType` and a library
+category, placed on pages via `create_page`'s `blockJson` as `component` blocks. A blog or
+catalogue is **schema-first**: a `create_content_model` collection whose body field is
+`document` (the article canvas — collections only, one per model, top level).
+
+Within a page's own schema, destructure into a tree: plain fields, **group** (one nested
+object), **repeater** (a repeatable array). Never a 1-item repeater, never a repeater of a
+single text (that is `array`).
+
+The full decision tree, section anatomy, variant rules and build order live in the
+`propose_schema` prompt and in the `bettercms://playbook/schema` resource.
 
 ## Forms
 Tools: `list_forms`, `get_form`, `create_form`, `update_form`.