@se-studio/skills 1.0.11 → 1.0.13

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @se-studio/skills
 
+## 1.0.13
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
+## 1.0.12
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
 ## 1.0.11
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/skills",
-  "version": "1.0.11",
+  "version": "1.0.13",
   "description": "SE Studio agent skills for marketing site development with Contentful CMS",
   "repository": {
     "type": "git",

package/skills/contentful-cms-core/SKILL.md

@@ -130,7 +130,7 @@ cms-edit set @root items <id1>,<id2>,<id3> --links
 
 **Rich text fields** (body, additionalCopy):
 ```bash
-printf '## Why it matters\n\nOur platform helps teams **move faster** with [confidence](https://example.com).\n\n- Instant setup\n- No code required\n- 99.9%% uptime\n' | cms-edit rtf @c1 body -
+printf '## Why it matters\n\nOur platform helps teams **move faster** with [confidence](https://example.com).\n\n- Instant setup\n- No code required\n- 99.9%% uptime\n' | cms-edit rtf @c1 body --markdown -
 ```
 
 Markdown support:
@@ -146,17 +146,17 @@ For any content with multiple paragraphs or newlines, use `printf` piped to stdi
 
 ```bash
 # Correct — printf interprets \n properly
-printf '## Why it matters\n\nOur platform helps teams **move faster**.\n\n- Instant setup\n- No code required\n' | cms-edit rtf @c1 body -
+printf '## Why it matters\n\nOur platform helps teams **move faster**.\n\n- Instant setup\n- No code required\n' | cms-edit rtf @c1 body --markdown -
 
 # Also correct — file input
-cms-edit rtf @c1 body --file path/to/file.md
-cms-edit rtf @c1 body - < path/to/file.md
+cms-edit rtf @c1 body --markdown --file path/to/file.md
+cms-edit rtf @c1 body --markdown - < path/to/file.md
 ```
 
 Single-line content (no newlines) can be passed as a quoted argument directly:
 
 ```bash
-cms-edit rtf @c1 body "Simple single-paragraph body text with **bold**."
+cms-edit rtf @c1 body --markdown "Simple single-paragraph body text with **bold**."
 ```
 
 **Surgical rich text replace** (compliance / quidget tokens — does not re-import the whole field):
@@ -237,7 +237,7 @@ Same as Component plus:
 When adding body content and a CTA (e.g. PDF download) to an article:
 
 1. `cms-edit open <article-slug>` (or `open <id> --id`)
-2. Set body: `cms-edit rtf @<ref> body "..."` or `--file path/to.md`. If you need to add a body component first, use `add` then `rtf`.
+2. Set body: `cms-edit rtf @<ref> body --markdown "..."` or `--markdown --file path/to.md`. If you need to add a body component first, use `add` then `rtf`.
 3. `cms-edit add CTA --target bottomContent`
 4. Set CTA links: use `--type external --label "Download PDF" --href <url>` for an external PDF URL, or `--type download --label "Download PDF" --asset-id <asset-id>` for a Contentful asset (get the ID from `cms-edit asset search "..."` or `asset info <id>`).
 5. `cms-edit save`
@@ -442,7 +442,7 @@ cms-edit read @c0
 cms-edit set @c0 heading "We build for the future"
 
 # 5. Update the body copy (use printf for multiline content)
-printf '## Our mission\n\nWe help companies **ship faster** and _smarter_.\n\n- Founded in 2018\n- 500+ clients\n- [Join us](/careers)\n' | cms-edit rtf @c0 body -
+printf '## Our mission\n\nWe help companies **ship faster** and _smarter_.\n\n- Founded in 2018\n- 500+ clients\n- [Join us](/careers)\n' | cms-edit rtf @c0 body --markdown -
 
 # 6. Review
 cms-edit diff
@@ -469,7 +469,7 @@ cms-edit open /products
 cms-edit types component  # discover what's available
 cms-edit add CTA --after @c3
 cms-edit set @c4 heading "Ready to get started?"
-cms-edit rtf @c4 body "Join thousands of teams who trust us."
+cms-edit rtf @c4 body --markdown "Join thousands of teams who trust us."
 cms-edit links add @c4 --type external --label "Start free trial" --href https://app.example.com
 cms-edit save
 ```
@@ -763,7 +763,7 @@ cat page.json | cms-edit create from-json             # Pipe from stdin
 - Any component entry in `components` or `items` may use `{ existingId }` to link an existing entry instead of creating a new one.
 - The same applies to `links` entries — use `{ existingId }` to attach an existing link entry.
 - `cmsLabel` sets the human-readable label shown in Contentful's entry list. Defaults to `type` or `contentType` if omitted. **Always set `cmsLabel` on components when a page has multiple instances of the same type** (e.g. three CTAs) — editors need to distinguish them.
-- String `fields` values are converted to Contentful rich text when they match the Markdown heuristic: contains `\n\n` or `**` or `_`, starts with `#`, starts with `- `, or starts with `> ` (blockquote with a space). **Plain single-line text with none of those patterns is not converted** — for RichText fields, add `\n\n` or a heading line, or use `cms-edit rtf` afterwards.
+- String `fields` values become Rich Text when they auto-detect as Markdown (same heuristic), HTML (tag-like), or Rich Text JSON (`nodeType: document`). Otherwise strings stay as-is — use `{ "value": "…", "format": "text"|"markdown"|"html"|"json" }` or `cms-edit rtf` with `--text|--markdown|--html|--json`.
 - `target` sets which content array to use: `topContent`, `content` (default), or `bottomContent`.
 - Slugs must not have a trailing slash — `from-json` strips it with a warning, but avoid it in source JSON.
 - All entries are created as **drafts**. A human must publish in Contentful.

package/skills/contentful-cms-rich-text/SKILL.md

@@ -9,10 +9,10 @@ Use this skill when editing **rich text** fields (body, additionalCopy) and inse
 
 ## Rich text (rtf)
 
-- **Replace** body with Markdown (single paragraph, no newlines): `cms-edit rtf @c1 body "Simple body with **bold** and [link](https://example.com)."`
+- **Replace** body with Markdown (single paragraph, no newlines): `cms-edit rtf @c1 body --markdown "Simple body with **bold** and [link](https://example.com)."`
 - **Multiline content** — use `printf` piped to stdin; `\n` in a double-quoted shell string is **not** a newline in bash:
   ```bash
-  printf '## Heading\n\nParagraph with **bold** and [link](https://example.com).\n' | cms-edit rtf @c1 body -
+  printf '## Heading\n\nParagraph with **bold** and [link](https://example.com).\n' | cms-edit rtf @c1 body --markdown -
   ```
 - Use `--file path/to/file.md` or stdin (`-`) for long content.
 - Markdown supported: headings, bold/italic, links, lists, blockquote, inline code, `---`.
@@ -86,7 +86,7 @@ Add `--dry-run` to count matches without writing.
 Replace an entire rich text field by piping Markdown from stdin. Avoids shell quoting issues for long content.
 
 ```bash
-echo "## New heading\n\nNew body text." | cms-edit rtf edit @c1 body
+echo "## New heading\n\nNew body text." | cms-edit rtf edit @c1 body --markdown
 ```
 
 In human (interactive) mode, the command prints the current Markdown to stdout first, then reads the replacement from stdin.

package/skills/site-workflows-project-cleanup/SKILL.md

@@ -57,9 +57,17 @@ After this change the font table will reference `system-ui` but retain all the r
 
 ---
 
-## Step 2 — Update `src/project/font.ts`
+## Step 2 — Remove fonts (file + binaries)
 
-Delete the entire file. It exports `noiVariableFlex` (local font) and `ibmPlexMono` (Google font) — both unused after cleanup.
+Delete the entire `src/project/font.ts` file. It exports `noiVariableFlex` (local font) and `ibmPlexMono` (Google font) — both unused after cleanup.
+
+Also remove any local font binaries that the template may ship alongside the loader. These are referenced by the now-deleted `font.ts` and otherwise linger as dead assets:
+
+```bash
+rm -rf src/fonts/
+```
+
+(If `src/fonts/` does not exist on this template, the command is a no-op — safe to run unconditionally.)
 
 ---
 
@@ -266,55 +274,68 @@ Delete `src/project/components/Footer/MobileFooter.tsx` if it exists.
 
 Create `scripts/clean-schema.js` (or update it if it already exists):
 
+> The `scripts/` directory in the SE Studio template ships with `{ "type": "module" }` in its own `package.json`, so the script below is **ESM** (`import` syntax, not `require`). Do not add `'use strict'` — it is a no-op in ES modules.
+
 ```js
 #!/usr/bin/env node
-'use strict';
-const fs = require('node:fs');
+import fs from 'node:fs';
 
 const inputPath = 'scripts/master-schema.json';
 const outputPath = 'scripts/clean-schema.json';
 
 if (!fs.existsSync(inputPath)) {
   console.error(`Input file not found: ${inputPath}`);
-  console.error('Export the schema first: contentful space export --skip-content --content-file scripts/master-schema.json');
+  console.error(
+    'Export the schema first: contentful space export --skip-content --skip-webhooks --content-file scripts/master-schema.json',
+  );
   process.exit(1);
 }
 
 const schema = JSON.parse(fs.readFileSync(inputPath, 'utf8'));
 
 // Trim componentType to bare-bones set
-const component = schema.contentTypes.find(ct => ct.sys.id === 'component');
+const component = schema.contentTypes?.find((ct) => ct.sys.id === 'component');
 if (component) {
-  const field = component.fields.find(f => f.id === 'componentType');
-  if (field) {
-    field.validations = field.validations.map(v => v.in ? { in: ['Generic'] } : v);
+  const field = component.fields.find((f) => f.id === 'componentType');
+  if (field?.validations) {
+    field.validations = field.validations.map((v) => (v.in ? { in: ['Generic'] } : v));
   }
 }
 
 // Trim collectionType to bare-bones set
-const collection = schema.contentTypes.find(ct => ct.sys.id === 'collection');
+const collection = schema.contentTypes?.find((ct) => ct.sys.id === 'collection');
 if (collection) {
-  const field = collection.fields.find(f => f.id === 'collectionType');
-  if (field) {
-    field.validations = field.validations.map(v =>
-      v.in ? { in: ['Generic', 'Related articles'] } : v
+  const field = collection.fields.find((f) => f.id === 'collectionType');
+  if (field?.validations) {
+    field.validations = field.validations.map((v) =>
+      v.in ? { in: ['Generic', 'Related articles'] } : v,
     );
   }
 }
 
-// Clear externalComponentType (no external components in bare-bones setup)
-const ext = schema.contentTypes.find(ct => ct.sys.id === 'externalComponent');
+// Drop the `in` validation on externalComponentType entirely.
+// Replacing it with `{ in: [] }` is rejected by Contentful's Management API
+// ("Expected at least one choice"), so we filter the validation out instead
+// and leave any non-`in` validations untouched.
+const ext = schema.contentTypes?.find((ct) => ct.sys.id === 'externalComponent');
 if (ext) {
-  const field = ext.fields.find(f => f.id === 'externalComponentType');
-  if (field) {
-    field.validations = field.validations.map(v => v.in ? { in: [] } : v);
+  const field = ext.fields.find((f) => f.id === 'externalComponentType');
+  if (field?.validations) {
+    field.validations = field.validations.filter((v) => !v.in);
   }
 }
 
+// Strip webhooks from the export. `contentful space import` will otherwise
+// try to CREATE every webhook in the target space and 409 on conflicts when
+// they already exist (e.g. revalidation webhook auto-provisioned by Vercel),
+// causing the import to exit non-zero even though content types succeeded.
+delete schema.webhooks;
+
 fs.writeFileSync(outputPath, JSON.stringify(schema, null, 2));
 console.log(`Clean schema written to ${outputPath}`);
 console.log('Component types kept:', ['Generic']);
 console.log('Collection types kept:', ['Generic', 'Related articles']);
+console.log('Webhooks: stripped from output');
 ```
 
 Run it:
@@ -353,10 +374,101 @@ Fix any TypeScript errors that surface from the removed imports. Common issues:
 
 ---
 
+## Step 13 — Clean up `docs/cms-guidelines/`
+
+Templates that have already had CMS guidelines generated will ship `docs/cms-guidelines/` files for components and collections that no longer exist after this cleanup. Trim it down to only the three kept types (Generic component, Generic collection, Related articles), then regenerate the merged docs.
+
+### 1. Delete obsolete component / collection / external markdown
+
+Remove every file under `docs/cms-guidelines/components/`, `docs/cms-guidelines/collections/`, and `docs/cms-guidelines/externals/` **except**:
+
+- `docs/cms-guidelines/components/generic.md`
+- `docs/cms-guidelines/collections/generic.md`
+- `docs/cms-guidelines/collections/related-articles.md`
+
+```bash
+# Components: keep only generic.md
+find docs/cms-guidelines/components -type f -name '*.md' ! -name 'generic.md' -delete 2>/dev/null || true
+
+# Collections: keep only generic.md and related-articles.md
+find docs/cms-guidelines/collections -type f -name '*.md' \
+  ! -name 'generic.md' ! -name 'related-articles.md' -delete 2>/dev/null || true
+
+# Externals: nothing kept
+rm -rf docs/cms-guidelines/externals 2>/dev/null || true
+```
+
+### 2. Trim `docs/cms-guidelines/screenshots/`
+
+Delete every PNG under `docs/cms-guidelines/screenshots/` that is not for `generic` (component or collection) or `related-articles` (collection):
+
+```bash
+# Component screenshots: keep generic-*.png only
+find docs/cms-guidelines/screenshots/components -type f \
+  ! -name 'generic-*.png' -delete 2>/dev/null || true
+
+# Collection screenshots: keep generic-*.png and related-articles-*.png
+find docs/cms-guidelines/screenshots/collections -type f \
+  ! -name 'generic-*.png' ! -name 'related-articles-*.png' -delete 2>/dev/null || true
+
+# Externals screenshots: drop entirely
+rm -rf docs/cms-guidelines/screenshots/externals 2>/dev/null || true
+```
+
+### 3. Trim `docs/cms-guidelines/screenshots/index.json`
+
+If it exists, edit `docs/cms-guidelines/screenshots/index.json` so it contains only entries for the three kept types — `Generic` (component), `Generic` (collection), and `Related articles` (collection). All other entries must be removed; otherwise the merged guidelines will reference deleted screenshots.
+
+### 4. Regenerate the merged guidelines
+
+```bash
+pnpm cms-guidelines:merge
+pnpm cms-generate-html-style-guide
+```
+
+This rewrites `docs/cms-guidelines/COMPONENT_GUIDELINES_FOR_LLM.md` and `docs/cms-guidelines/html-component-style-guide.md` against the trimmed inputs.
+
+---
+
+## Step 14 — Clean up `src/generated/cms-discovery/accepted-variants/`
+
+The same component/collection types are referenced by JSON discovery files under `src/generated/cms-discovery/accepted-variants/`. Stale entries for removed types must be deleted, otherwise `generate-showcase-mocks` and the CMS guideline skills will repopulate guidelines for components that no longer exist in code.
+
+Delete everything in `accepted-variants/` **except**:
+
+- `accepted-variants/generic.json` (if present at the top level)
+- `accepted-variants/related-articles.json` (if present at the top level)
+- `accepted-variants/components/generic.json`
+- `accepted-variants/collections/generic.json`
+- `accepted-variants/collections/related-articles.json`
+
+```bash
+DISCOVERY=src/generated/cms-discovery/accepted-variants
+
+# Top-level legacy files (older templates): keep generic.json + related-articles.json only
+find "$DISCOVERY" -maxdepth 1 -type f -name '*.json' \
+  ! -name 'generic.json' ! -name 'related-articles.json' -delete 2>/dev/null || true
+
+# Components: keep generic.json only
+find "$DISCOVERY/components" -type f -name '*.json' \
+  ! -name 'generic.json' -delete 2>/dev/null || true
+
+# Collections: keep generic.json + related-articles.json
+find "$DISCOVERY/collections" -type f -name '*.json' \
+  ! -name 'generic.json' ! -name 'related-articles.json' -delete 2>/dev/null || true
+
+# Externals: drop entirely
+rm -rf "$DISCOVERY/externals" 2>/dev/null || true
+```
+
+If the project also ships top-level showcase outputs (`src/generated/showcase-examples.json`, `src/generated/showcase-mocks-draft.json`), delete those too — they are regenerated by `pnpm generate-showcase-mocks`. Leave `src/generated/showcase-mocks.json` (it is committed and will be re-curated via the **curate-showcase-mocks** skill on demand).
+
+---
+
 ## What is deliberately left untouched
 
 - `src/app/(cms-routes)/` — all routing is left as-is; the CMS routes work with whatever is registered
 - `src/lib/constants.ts` — site title/description stays as-is for cleanup; update manually for new projects
 - `src/project/STYLING.md` and `src/project/ANIMATION.md` — left for human review; update to reflect the new bare-bones system
-- `src/project/font.ts` — deleted (step 2 above)
+- `src/project/font.ts` and `src/fonts/` — deleted (step 2 above)
 - `scripts/master-schema.json` — never modified, always kept as the original export