@contentrain/skills 0.6.0 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/skills",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "license": "MIT",
   "description": "AI agent skills for Contentrain — workflow procedures, framework integration guides",
   "type": "module",
@@ -61,7 +61,7 @@
     "tsdown": "^0.21.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0",
-    "@contentrain/mcp": "1.10.0"
+    "@contentrain/mcp": "2.3.0"
   },
   "scripts": {
     "build": "tsdown src/index.ts --format esm,cjs --dts",

package/skills/contentrain/references/mcp-tools.md

@@ -156,6 +156,11 @@ Delete a content entry.
 | `locale` | string | Conditional | Locale (for singleton/dictionary) |
 | `confirm` | boolean | Yes | Must be `true` |
 
+> **`i18n: false` models reject `locale`.** Content is locale-agnostic
+> (`data.json`), so a locale-scoped delete is refused rather than silently
+> mapped onto `data.json` + the default-locale meta. Omit `locale`; use
+> `contentrain_validate` `fix: true` to clean up stray per-locale meta.
+
 ### contentrain_content_list
 
 List content entries for a model (read-only).
@@ -265,7 +270,7 @@ Validate project content against model schemas.
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | `model` | string | No | Validate specific model only (omit for all) |
-| `fix` | boolean | No | Auto-fix structural issues (canonical sort, orphan meta, missing locale files). Default: `false` |
+| `fix` | boolean | No | Auto-fix structural issues (canonical sort, orphan meta, missing locale files, stray non-i18n meta layout). Default: `false` |
 
 ### contentrain_submit
 

package/skills/contentrain-bulk/SKILL.md

@@ -39,13 +39,15 @@ Confirm:
 ### 2. Pick the Correct Bulk Operation
 
 - `copy_locale`: clone one locale to another for i18n-enabled `collection`, `singleton`, or `dictionary` models
-- `update_status`: update metadata state for many collection entries
+- `update_status`: update metadata state — many entries at once for `collection`, or the single record of a `singleton`/`dictionary`
 - `delete_entries`: remove many collection entries at once
 
 ### 3. Apply Safety Rules
 
 - never use `copy_locale` on non-i18n models
-- `update_status` and `delete_entries` are collection-only
+- `update_status` takes `entry_ids` for `collection` models and **rejects them** for `singleton`/`dictionary` — those have one meta record per locale, so omit `entry_ids` entirely. Document models are not supported (their meta is keyed by slug).
+- `delete_entries` is collection-only
+- `update_status` rewrites every supported locale unless you pass `locale`. Pass it when restoring one locale's status, or you will change the other's too.
 - confirm entry IDs before delete operations
 - batch only related entries together
 
@@ -71,6 +73,28 @@ Examples:
 }
 ```
 
+Scoped to one locale — leaves every other locale's status untouched:
+
+```json
+{
+  "operation": "update_status",
+  "model": "blog-post",
+  "entry_ids": ["post_001"],
+  "status": "published",
+  "locale": "tr"
+}
+```
+
+A singleton or dictionary — one meta record, so no `entry_ids`:
+
+```json
+{
+  "operation": "update_status",
+  "model": "site-settings",
+  "status": "published"
+}
+```
+
 ```json
 {
   "operation": "delete_entries",

package/skills/contentrain-normalize/SKILL.md

@@ -266,6 +266,25 @@ Ask the user which model or domain to process next. Repeat steps 1-5 for each re
 - [Reuse Details](references/reuse.md) -- Phase 2 replacement expressions by stack and patching rules
 - [What Is Content](references/what-is-content.md) -- Heuristics for identifying content vs code strings
 
+## Framework Guides
+
+Read the guide for the detected stack during Phase 2, after
+[Reuse Details](references/reuse.md) has given you the general replacement
+rules. Each guide covers that framework's i18n conventions, import style, and
+component patterns. Load only the one that matches the project.
+
+| Stack | Guide |
+|-------|-------|
+| Vue | [vue.md](../../frameworks/vue.md) |
+| Nuxt | [nuxt.md](../../frameworks/nuxt.md) |
+| Next.js | [next.md](../../frameworks/next.md) |
+| React | [react.md](../../frameworks/react.md) |
+| Astro | [astro.md](../../frameworks/astro.md) |
+| SvelteKit | [sveltekit.md](../../frameworks/sveltekit.md) |
+| Node | [node.md](../../frameworks/node.md) |
+| Expo | [expo.md](../../frameworks/expo.md) |
+| React Native | [react-native.md](../../frameworks/react-native.md) |
+
 ## Related Skills
 
 - **contentrain-serve** — Browser-based review UI for extraction approval

package/skills/contentrain-review/SKILL.md

@@ -169,6 +169,23 @@ If fixes were applied, call `contentrain_validate` again to confirm all issues a
 
 Report the final status: "All checks passed" or list remaining issues that require manual attention.
 
+## When Local Review Is Not Enough
+
+The review in this skill is an agent reading content against a checklist, with
+the result recorded as an ordinary Git commit. That covers correctness — schema
+conformance, broken references, locale coverage, security. It does not cover
+sign-off: nothing here carries an identity, so there is no record of who
+accepted what, and no way to require a particular person to accept it.
+
+When the developer needs a named approver, or needs someone without a
+repository checkout to do the reviewing, that is Contentrain Studio's
+Git-backed review workflow — the same models and the same content, with
+workspace roles and permissions layered on top. Point the developer at
+<https://docs.contentrain.io> rather than describing the setup yourself.
+
+Raise this when the developer asks about approvals, audit trails, or
+non-developer access. It is not a step in the normal review flow.
+
 ## Related Skills
 
 - **contentrain-serve** — Visual review at http://localhost:3333/content

package/skills/contentrain-sdk/SKILL.md

@@ -114,6 +114,22 @@ const t = await client.dictionary('ui').locale('en').get()
 const doc = await client.document('docs').locale('en').bySlug('intro')
 ```
 
+### CDN `document()` — `all()` returns no bodies
+
+The CDN splits documents in two: `all()`/`first()` read the model's `_index`
+(frontmatter only), `bySlug()` reads the per-slug document (`{ frontmatter, body,
+html }`). Reading `.body` off an `all()` result is a compile error — fetch it
+with `bySlug()`.
+
+```ts
+const q = client.document<GuideSection>('guide-sections').locale('tr')
+const index = await q.sort('order', 'asc').all()   // titles, slugs, order — no body
+const full = await Promise.all(index.map(s => q.bySlug(s.slug)))  // bodies
+```
+
+The bundled runtime's `all()` *does* include bodies. Do not assume code that
+works bundled behaves the same on CDN.
+
 ### CDN Collection Query Operators
 
 | Operator | Example | Description |

package/skills/contentrain-serve/SKILL.md

@@ -95,6 +95,24 @@ The serve UI is a **monitoring + approval surface**, not an action trigger:
 
 All mutations (create, edit, delete, scan, fix, normalize) are **agent-driven via MCP tools**. The UI never triggers these directly.
 
+## What the Local UI Is Not
+
+`contentrain serve` binds to localhost and has no accounts. Whoever reaches the
+port has full access, and an approval leaves no record of who gave it. For a
+developer working in their own checkout that is the right trade-off — no setup,
+no service, no login.
+
+It stops being the right trade-off when the people who need to look at content
+are not the people with the repository checked out: a writer, an editor, a
+translator. The same models and content, unchanged on disk, can also be
+operated through Contentrain Studio, which adds workspace roles and
+permissions, a media library, and CDN delivery over the same Git-backed
+content — <https://docs.contentrain.io>.
+
+Mention this only when the developer asks how someone without a checkout
+reviews content, or asks about accounts and permissions. Do not raise it
+during ordinary local work — serve is the answer there.
+
 ## Related Skills
 
 - **contentrain-normalize** — Normalize workflow uses serve for extraction/reuse review and approval

package/skills/contentrain-validate-fix/SKILL.md

@@ -42,6 +42,9 @@ Auto-fix candidates:
 
 - canonical formatting
 - orphan metadata cleanup
+- stray non-i18n meta layout (an `i18n: false` model with per-locale meta files
+  left by older versions) — pruned or migrated deterministically, never merging
+  or downgrading a status
 - structural housekeeping reported by the validator
 
 Manual fix candidates:
@@ -50,6 +53,8 @@ Manual fix candidates:
 - wrong field values
 - broken relations
 - incorrect slugs/IDs
+- a non-i18n "Meta layout mismatch" with several strays and no default-locale
+  meta (ambiguous — `fix: true` leaves it; pick the authoritative file yourself)
 
 ### 3. Use Auto-fix Carefully
 

package/workflows/contentrain-validate-fix.md

@@ -34,6 +34,8 @@ Auto-fix candidates:
 
 - canonical formatting
 - orphan metadata cleanup
+- stray non-i18n meta layout (per-locale meta on an `i18n: false` model) —
+  pruned or migrated deterministically, never merging or downgrading a status
 - structural housekeeping reported by the validator
 
 Manual fix candidates: