@se-studio/project-build 1.0.131 → 1.0.133

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @se-studio/project-build
 
+## 1.0.133
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
+## 1.0.132
+
+### Patch Changes
+
+- Version bump: patch for changed packages
+
 ## 1.0.131
 
 ### Patch Changes

package/README.md

@@ -56,23 +56,28 @@ pnpm setailwind
 pnpm setup-colours
 ```
 
-### Skills sync (seskills)
+### Agent skills
 
-Skills are sourced from `packages/project-build/skills/` and can be synced into an app’s `.agents/skills/` directory so the app has the same marketing-site skills as the package. Add a `.cursor/skills` → `.agents/skills` symlink if the editor only discovers `.cursor/skills`.
+SE Studio skills are now published as a separate package: **`@se-studio/skills`**. Skill source files live in `packages/skills/skills/`.
 
-**From an app directory** (e.g. `apps/example-brightline`):
+**In the monorepo**, run from the repo root to sync skills into `.agents/skills/`:
 
 ```bash
-pnpm exec seskills sync
+pnpm skills:sync
 ```
 
-**From the repo root** (sync into a specific app):
+**In external projects**, install skills via the `skills` CLI:
 
 ```bash
-pnpm exec seskills sync apps/example-brightline
+npx skills add @se-studio/skills
 ```
 
-This copies the contents of `project-build/skills/` into the target’s `.agents/skills/`. Run after pulling changes to project-build skills or when setting up a new app.
+Add to your project’s `package.json` to auto-install on `pnpm install`:
+
+```json
+"devDependencies": { "@se-studio/skills": "^1.0.0" },
+"scripts": { "postinstall": "npx skills update -y" }
+```
 
 ## API Reference
 
@@ -111,13 +116,7 @@ setup-colours
 ```
 
 #### `seskills sync [target-dir]`
-Syncs skills from `packages/project-build/skills/` into a project’s `.agents/skills/`. Default target is current working directory.
-
-**Usage:**
-```bash
-seskills sync                 # sync into current directory
-seskills sync apps/example-om1   # sync into given path
-```
+Deprecated. Use `npx skills add @se-studio/skills` instead. See `packages/skills/` for the canonical skill sources.
 
 For detailed JSDoc documentation on all exports, see the TypeScript declaration files (`.d.ts`) in the package.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/project-build",
-  "version": "1.0.131",
+  "version": "1.0.133",
   "description": "Build tools and management scripts for SE Studio projects",
   "repository": {
     "type": "git",
@@ -28,7 +28,6 @@
   "bin": {
     "setailwind": "./dist/setailwind.js",
     "setup-colours": "./dist/management/setupColours.js",
-    "seskills": "./dist/seskills.js",
     "generate-showcase-data": "./dist/generate-showcase-data.js",
     "generate-showcase-mocks": "./dist/generate-showcase-mocks.js",
     "cms-generate-field-list": "./dist/cms-generate-field-list.js",
@@ -40,7 +39,6 @@
   },
   "files": [
     "dist",
-    "skills",
     "*.md"
   ],
   "keywords": [
@@ -76,7 +74,7 @@
     "vitest": "^4.1.4"
   },
   "scripts": {
-    "build": "node scripts/merge-contentful-skills.mjs && tsc --project tsconfig.build.json",
+    "build": "tsc --project tsconfig.build.json",
     "dev": "tsc --project tsconfig.build.json --watch",
     "type-check": "tsc --noEmit",
     "lint": "biome lint .",

package/dist/management/sync-skills.d.ts

@@ -1,4 +0,0 @@
-export declare function syncSkills(targetDir?: string, 
-/** When true, exits silently (code 0) if not running as an installed package. Safe for postinstall. */
-ifInstalled?: boolean): Promise<void>;
-//# sourceMappingURL=sync-skills.d.ts.map

package/dist/management/sync-skills.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sync-skills.d.ts","sourceRoot":"","sources":["../../src/management/sync-skills.ts"],"names":[],"mappings":"AA+CA,wBAAsB,UAAU,CAC9B,SAAS,GAAE,MAAsB;AACjC,uGAAuG;AACvG,WAAW,UAAQ,iBAsEpB"}

package/dist/management/sync-skills.js

@@ -1,97 +0,0 @@
-import * as fs from 'node:fs';
-import * as path from 'node:path';
-import { fileURLToPath } from 'node:url';
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-async function copyDir(src, dest) {
-    await fs.promises.mkdir(dest, { recursive: true });
-    const entries = await fs.promises.readdir(src, { withFileTypes: true });
-    for (const entry of entries) {
-        const srcPath = path.join(src, entry.name);
-        const destPath = path.join(dest, entry.name);
-        if (entry.isDirectory()) {
-            await copyDir(srcPath, destPath);
-        }
-        else {
-            await fs.promises.copyFile(srcPath, destPath);
-        }
-    }
-}
-async function flattenGroup(srcGroupDir, prefix, targetDir) {
-    if (!fs.existsSync(srcGroupDir))
-        return;
-    const entries = await fs.promises.readdir(srcGroupDir, { withFileTypes: true });
-    for (const entry of entries) {
-        if (!entry.isDirectory())
-            continue;
-        await copyDir(path.join(srcGroupDir, entry.name), path.join(targetDir, `${prefix}-${entry.name}`));
-    }
-}
-/**
- * Returns true when this script is running from inside a pnpm/npm workspace
- * (i.e. as a local package, not as an installed dependency from the registry).
- *
- * Detection: if the path to this file does NOT contain "node_modules" then we
- * are running from the workspace source — syncing would overwrite the canonical
- * skill files with the distributed copies, which is the wrong direction.
- */
-function isWorkspacePackage() {
-    return !__dirname.includes('node_modules');
-}
-export async function syncSkills(targetDir = process.cwd(), 
-/** When true, exits silently (code 0) if not running as an installed package. Safe for postinstall. */
-ifInstalled = false) {
-    if (isWorkspacePackage()) {
-        if (ifInstalled) {
-            // Running inside the monorepo during a workspace install — skip silently.
-            return;
-        }
-        console.warn('Warning: seskills sync is running from a workspace package (not from node_modules).\n' +
-            'Skipping to avoid overwriting canonical skill files in the monorepo.\n' +
-            'Run `seskills sync` from an external project that has @se-studio/project-build installed.');
-        return;
-    }
-    // Locate the skills directory relative to this file (dist/management/sync-skills.js)
-    // dist/management/ -> dist/ -> package root -> skills/
-    const packageRoot = path.resolve(__dirname, '..', '..');
-    const skillsSourceDir = path.join(packageRoot, 'skills');
-    const skillsTargetDir = path.join(targetDir, '.agents', 'skills');
-    console.log(`Syncing skills from ${skillsSourceDir} to ${skillsTargetDir}...`);
-    try {
-        try {
-            await fs.promises.access(skillsSourceDir);
-        }
-        catch {
-            console.error(`Error: Skills directory not found at ${skillsSourceDir}`);
-            console.error('This may be because the package was not built or installed correctly.');
-            return;
-        }
-        // Remove stale nested group dirs and flat aliases before rebuilding
-        const groups = ['contentful-cms', 'se-marketing-sites', 'site-workflows'];
-        try {
-            const existing = await fs.promises.readdir(skillsTargetDir, { withFileTypes: true });
-            for (const entry of existing) {
-                if (!entry.isDirectory())
-                    continue;
-                const isNestedGroup = groups.includes(entry.name);
-                const isFlatAlias = groups.some((g) => entry.name.startsWith(`${g}-`));
-                if (isNestedGroup || isFlatAlias) {
-                    await fs.promises.rm(path.join(skillsTargetDir, entry.name), { recursive: true });
-                }
-            }
-        }
-        catch {
-            // target dir may not exist yet — fine
-        }
-        // Flatten group dirs into <group>-<skill>/ at the top level
-        await flattenGroup(path.join(skillsSourceDir, 'contentful-cms'), 'contentful-cms', skillsTargetDir);
-        await flattenGroup(path.join(skillsSourceDir, 'se-marketing-sites'), 'se-marketing-sites', skillsTargetDir);
-        await flattenGroup(path.join(skillsSourceDir, 'site-workflows'), 'site-workflows', skillsTargetDir);
-        console.log('Skills synced successfully.');
-    }
-    catch (error) {
-        console.error('Error syncing skills:', error);
-        process.exit(1);
-    }
-}
-//# sourceMappingURL=sync-skills.js.map

package/dist/management/sync-skills.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sync-skills.js","sourceRoot":"","sources":["../../src/management/sync-skills.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAClC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC;AAE3C,KAAK,UAAU,OAAO,CAAC,GAAW,EAAE,IAAY;IAC9C,MAAM,EAAE,CAAC,QAAQ,CAAC,KAAK,CAAC,IAAI,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IACnD,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IAExE,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,MAAM,OAAO,GAAG,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,CAAC,CAAC;QAC3C,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC,CAAC;QAE7C,IAAI,KAAK,CAAC,WAAW,EAAE,EAAE,CAAC;YACxB,MAAM,OAAO,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QACnC,CAAC;aAAM,CAAC;YACN,MAAM,EAAE,CAAC,QAAQ,CAAC,QAAQ,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QAChD,CAAC;IACH,CAAC;AACH,CAAC;AAED,KAAK,UAAU,YAAY,CAAC,WAAmB,EAAE,MAAc,EAAE,SAAiB;IAChF,IAAI,CAAC,EAAE,CAAC,UAAU,CAAC,WAAW,CAAC;QAAE,OAAO;IACxC,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,WAAW,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IAChF,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,IAAI,CAAC,KAAK,CAAC,WAAW,EAAE;YAAE,SAAS;QACnC,MAAM,OAAO,CACX,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,KAAK,CAAC,IAAI,CAAC,EAClC,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,GAAG,MAAM,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,CAChD,CAAC;IACJ,CAAC;AACH,CAAC;AAED;;;;;;;GAOG;AACH,SAAS,kBAAkB;IACzB,OAAO,CAAC,SAAS,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC;AAC7C,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,UAAU,CAC9B,YAAoB,OAAO,CAAC,GAAG,EAAE;AACjC,uGAAuG;AACvG,WAAW,GAAG,KAAK;IAEnB,IAAI,kBAAkB,EAAE,EAAE,CAAC;QACzB,IAAI,WAAW,EAAE,CAAC;YAChB,0EAA0E;YAC1E,OAAO;QACT,CAAC;QACD,OAAO,CAAC,IAAI,CACV,uFAAuF;YACrF,wEAAwE;YACxE,2FAA2F,CAC9F,CAAC;QACF,OAAO;IACT,CAAC;IAED,qFAAqF;IACrF,uDAAuD;IACvD,MAAM,WAAW,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;IACxD,MAAM,eAAe,GAAG,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,QAAQ,CAAC,CAAC;IACzD,MAAM,eAAe,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,SAAS,EAAE,QAAQ,CAAC,CAAC;IAElE,OAAO,CAAC,GAAG,CAAC,uBAAuB,eAAe,OAAO,eAAe,KAAK,CAAC,CAAC;IAE/E,IAAI,CAAC;QACH,IAAI,CAAC;YACH,MAAM,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,eAAe,CAAC,CAAC;QAC5C,CAAC;QAAC,MAAM,CAAC;YACP,OAAO,CAAC,KAAK,CAAC,wCAAwC,eAAe,EAAE,CAAC,CAAC;YACzE,OAAO,CAAC,KAAK,CAAC,uEAAuE,CAAC,CAAC;YACvF,OAAO;QACT,CAAC;QAED,oEAAoE;QACpE,MAAM,MAAM,GAAG,CAAC,gBAAgB,EAAE,oBAAoB,EAAE,gBAAgB,CAAC,CAAC;QAC1E,IAAI,CAAC;YACH,MAAM,QAAQ,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,eAAe,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;YACrF,KAAK,MAAM,KAAK,IAAI,QAAQ,EAAE,CAAC;gBAC7B,IAAI,CAAC,KAAK,CAAC,WAAW,EAAE;oBAAE,SAAS;gBACnC,MAAM,aAAa,GAAG,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;gBAClD,MAAM,WAAW,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC;gBACvE,IAAI,aAAa,IAAI,WAAW,EAAE,CAAC;oBACjC,MAAM,EAAE,CAAC,QAAQ,CAAC,EAAE,CAAC,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,KAAK,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;gBACpF,CAAC;YACH,CAAC;QACH,CAAC;QAAC,MAAM,CAAC;YACP,sCAAsC;QACxC,CAAC;QAED,4DAA4D;QAC5D,MAAM,YAAY,CAChB,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,gBAAgB,CAAC,EAC5C,gBAAgB,EAChB,eAAe,CAChB,CAAC;QACF,MAAM,YAAY,CAChB,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,oBAAoB,CAAC,EAChD,oBAAoB,EACpB,eAAe,CAChB,CAAC;QACF,MAAM,YAAY,CAChB,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,gBAAgB,CAAC,EAC5C,gBAAgB,EAChB,eAAe,CAChB,CAAC;QAEF,OAAO,CAAC,GAAG,CAAC,6BAA6B,CAAC,CAAC;IAC7C,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,OAAO,CAAC,KAAK,CAAC,uBAAuB,EAAE,KAAK,CAAC,CAAC;QAC9C,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;AACH,CAAC"}

package/dist/seskills.d.ts

@@ -1,9 +0,0 @@
-#!/usr/bin/env node
-/**
- * seskills - Skill management CLI for SE Studio projects
- *
- * Usage:
- *   seskills sync [target-dir]
- */
-export {};
-//# sourceMappingURL=seskills.d.ts.map

package/dist/seskills.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"seskills.d.ts","sourceRoot":"","sources":["../src/seskills.ts"],"names":[],"mappings":";AACA;;;;;GAKG"}

package/dist/seskills.js

@@ -1,32 +0,0 @@
-#!/usr/bin/env node
-/**
- * seskills - Skill management CLI for SE Studio projects
- *
- * Usage:
- *   seskills sync [target-dir]
- */
-import { syncSkills } from './management/sync-skills.js';
-async function main() {
-    const args = process.argv.slice(2);
-    const command = args[0];
-    if (command === 'sync') {
-        // Filter out flags from positional args
-        const positional = args.slice(1).filter((a) => !a.startsWith('--'));
-        const ifInstalled = args.includes('--if-installed');
-        const targetDir = positional[0] || process.cwd();
-        await syncSkills(targetDir, ifInstalled);
-    }
-    else {
-        console.log('Usage: seskills sync [target-dir] [--if-installed]');
-        console.log('');
-        console.log('  --if-installed  Exit silently when running as a workspace package.');
-        console.log('                  Use this in a postinstall script so it only runs in');
-        console.log('                  external projects, not inside the monorepo.');
-        process.exit(1);
-    }
-}
-main().catch((err) => {
-    console.error(err);
-    process.exit(1);
-});
-//# sourceMappingURL=seskills.js.map

package/dist/seskills.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"seskills.js","sourceRoot":"","sources":["../src/seskills.ts"],"names":[],"mappings":";AACA;;;;;GAKG;AAEH,OAAO,EAAE,UAAU,EAAE,MAAM,6BAA6B,CAAC;AAEzD,KAAK,UAAU,IAAI;IACjB,MAAM,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;IACnC,MAAM,OAAO,GAAG,IAAI,CAAC,CAAC,CAAC,CAAC;IAExB,IAAI,OAAO,KAAK,MAAM,EAAE,CAAC;QACvB,wCAAwC;QACxC,MAAM,UAAU,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,IAAI,CAAC,CAAC,CAAC;QACpE,MAAM,WAAW,GAAG,IAAI,CAAC,QAAQ,CAAC,gBAAgB,CAAC,CAAC;QACpD,MAAM,SAAS,GAAG,UAAU,CAAC,CAAC,CAAC,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC;QACjD,MAAM,UAAU,CAAC,SAAS,EAAE,WAAW,CAAC,CAAC;IAC3C,CAAC;SAAM,CAAC;QACN,OAAO,CAAC,GAAG,CAAC,oDAAoD,CAAC,CAAC;QAClE,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChB,OAAO,CAAC,GAAG,CAAC,sEAAsE,CAAC,CAAC;QACpF,OAAO,CAAC,GAAG,CAAC,uEAAuE,CAAC,CAAC;QACrF,OAAO,CAAC,GAAG,CAAC,+DAA+D,CAAC,CAAC;QAC7E,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;AACH,CAAC;AAED,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,GAAG,EAAE,EAAE;IACnB,OAAO,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;IACnB,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}

package/skills/contentful-cms/alt-text-audit/SKILL.md

@@ -1,60 +0,0 @@
----
-name: "Alt Text Audit"
-description: "Audit and improve image alt text across site pages using cms-edit, with brand-aware terminology and accessibility best practices."
----
-
-# Skill: contentful-cms — Alt Text Audit
-
-Use this skill when auditing or improving **image alt text** across a site's pages using `cms-edit`. Works with any brand context skill for customer-specific terminology.
-
-## Brand Context
-
-Before starting, check if a brand context skill is available (e.g., "OM1 Brand Context", "Something Else Brand Context"). If so, use its terminology, image interpretation guidelines, and brand voice when writing alt text.
-
-If no brand context is available, ask the user about any brand-specific terms before proceeding.
-
-## Workflow
-
-1. **Get all pages**: `cms-edit sitemap`
-2. **For each page** (or a specific page if the user specified one):
-   a. `cms-edit open /<slug>`
-   b. `cms-edit snapshot` — identify components with visual/image/media fields
-   c. For each image-bearing component:
-      - `cms-edit read @ref` to inspect fields
-      - Check `altText` on any image/visual references
-      - `cms-edit read @ref visual` to see asset details if needed
-   d. **Flag** images with:
-      - Missing alt text (empty or null)
-      - Generic alt text ("image", "photo", "banner", "screenshot", "img", "picture")
-      - Alt text that doesn't use brand terminology (if brand context available)
-      - Alt text over 125 characters
-   e. **Generate** improved alt text following the guidelines below
-   f. `cms-edit set @ref altText "new alt text"`
-   g. `cms-edit diff` to review, then `cms-edit save`
-
-## Alt Text Guidelines
-
-1. **Be specific and descriptive** — describe what is actually in the image
-2. **Use brand terminology** — refer to the brand context for correct terms
-3. **Keep under 125 characters** — screen readers truncate longer text
-4. **Don't start with** "Image of", "Photo of", "Picture of"
-5. **Decorative images** — set alt to "" (empty string) for dividers, background patterns
-6. **Context matters** — describe the image's purpose on the page, not just its visual content
-7. **Include relevant actions** — if people are doing something meaningful, describe it
-
-## Reading Page Content
-
-To understand a page before auditing its images, use `fetch_page_markdown` (from the site-workflows MCP server) with the page slug.
-
-## Output
-
-Present a summary table when complete:
-
-| Page | Component | Old Alt Text | New Alt Text | Status |
-|------|-----------|-------------|-------------|--------|
-
-Where Status is: Updated, Skipped (decorative), Already Good, or Needs Review.
-
-## Related skills
-
-See the **core** skill for the full cms-edit workflow (open, snapshot, read, set, save).

package/skills/contentful-cms/cms-guidelines/README.md

@@ -1,166 +0,0 @@
-# CMS Guidelines Generation
-
-This directory contains the pipeline prompts and documentation for generating CMS component guideline fragments for any app in the monorepo.
-
----
-
-## What are CMS guidelines?
-
-Guidelines are short markdown fragments — one per CMS type — that describe how each component or collection looks, what fields it uses, how colours are applied, and how it behaves. They are merged into `docs/cms-guidelines/COMPONENT_GUIDELINES_FOR_LLM.md`, a single document used to give LLMs accurate context about the app's component library.
-
----
-
-## Lifecycle: From content to guidelines
-
-1. **Build the site** — implement all components and collections; ensure all content is correct and published in Contentful.
-2. **Generate showcase data** — pull real Contentful data into the app's showcase:
-   ```bash
-   pnpm --filter <appName> generate-showcase
-   ```
-   This writes `src/generated/showcase-examples.json`.
-3. **Curate showcase mocks** — run the [curate-showcase-mocks skill](.agents/skills/se-marketing-sites-curate-showcase-mocks/SKILL.md) to select the best examples into `showcase-mocks.json`. This makes the showcase (and screenshots) show realistic content.
-4. **Generate field list** — parse TypeScript types to produce structured field metadata:
-   ```bash
-   # From the app directory:
-   pnpm run cms-discovery:field-list
-
-   # Or from repo root:
-   pnpm --filter <appName> exec cms-generate-field-list --app-dir .
-   ```
-5. **Generate guidelines** — run the [Generate CMS guidelines skill](.agents/skills/contentful-cms-generate-cms-guidelines/SKILL.md).
-
-Steps 1–3 only need to be repeated when content or component code changes significantly. Step 4 only needs to be repeated when TypeScript types change. Step 5 can be re-run at any time.
-
----
-
-## How to run guideline generation
-
-Use the Cursor skill at [`.agents/skills/contentful-cms-generate-cms-guidelines/SKILL.md`](.agents/skills/contentful-cms-generate-cms-guidelines/SKILL.md). It supports three modes:
-
-| Mode | When to use |
-|---|---|
-| `full` | First-time generation, or regenerate everything |
-| `single` | Regenerate one component after code changes |
-| `merge-only` | Rebuild `COMPONENT_GUIDELINES_FOR_LLM.md` after manual fragment edits |
-
-**Example: full from scratch for `example-om1`**
-
-Start the app:
-```bash
-pnpm --filter example-om1 dev
-```
-
-Then invoke the skill with:
-- App directory: `apps/example-om1`
-- Mode: `full`
-- Discovery URL: `http://localhost:3013/api/cms/discovery/`
-
-**Example: single component**
-
-Invoke the skill with:
-- App directory: `apps/example-se2026`
-- Mode: `single`
-- Type name: `Hero`
-- Discovery URL: `http://localhost:3012/api/cms/discovery/`
-
-**Example: merge only**
-
-```bash
-cms-merge-guidelines --app-dir apps/example-om1
-```
-
----
-
-## CLIs used by this pipeline
-
-| CLI | Purpose |
-|---|---|
-| `cms-generate-html-style-guide` | Generate `html-component-style-guide.md` from `tailwind.config.json` + `globals.css` |
-| `cms-generate-field-list` | Parse TypeScript types → `field-list.json` |
-| `cms-capture-screenshots` | Capture component screenshots for variant evaluation |
-| `cms-update-colour-hints` | Upsert a colour hint in `colour-hints.json` |
-| `cms-generate-collection-guidelines` | Generate all collection/external `.md` files from a discovery URL |
-| `cms-merge-guidelines` | Merge all fragments → `COMPONENT_GUIDELINES_FOR_LLM.md` |
-
-All CLIs are provided by `@se-studio/project-build`. Run `pnpm build` from the repo root to ensure they are built and linked.
-
----
-
-## `cms-generate-html-style-guide`
-
-Generates `docs/cms-guidelines/html-component-style-guide.md` — a design system reference for any LLM or developer authoring HTML in `HtmlComponent` CMS entries.
-
-Does not require a running dev server. Reads only local files:
-- `tailwind.config.json` → colour palette, typography classes, grid configuration
-- `src/app/globals.css` → custom utilities, RTF class names, CSS custom properties
-
-```bash
-# From the app directory:
-pnpm cms-generate-html-style-guide
-```
-
-The output file is a **static fragment** — not generated by the LLM component pipeline. It is automatically included as a preamble in `COMPONENT_GUIDELINES_FOR_LLM.md` when `cms-merge-guidelines` runs. Regenerate it whenever the design system changes.
-
----
-
-## `cms-generate-collection-guidelines`
-
-New project-independent CLI. Reads the discovery API and writes collection and external guideline fragments without any app-specific hardcoding.
-
-```bash
-cms-generate-collection-guidelines \
-  --discovery-url http://localhost:3010/api/cms/discovery/ \
-  --app-dir apps/example-brightline
-```
-
-Options:
-
-| Flag | Description |
-|---|---|
-| `--discovery-url <url>` | Discovery API URL (required). App must be running. |
-| `--app-dir <path>` | App directory (default: cwd). |
-
-Outputs:
-- `docs/cms-guidelines/collections/<slug>.md` for every collection
-- `docs/cms-guidelines/externals/<slug>.md` for every external
-- Updates `generated/cms-discovery/colour-hints.json`
-
----
-
-## Pipeline document index
-
-| File | Purpose |
-|---|---|
-| `generate-component-guidelines.md` | Full pipeline overview: Phases A–F |
-| `variant-loop.md` | Phase A: propose variants → screenshot → evaluate |
-| `variant-proposal-prompt.md` | LLM prompt: propose showcase variants |
-| `evaluation-prompt.md` | LLM prompt: evaluate screenshot diversity |
-| `generation-prompt.md` | Phase B: three-step guideline generation |
-| `colour-hint-prompt.md` | Phase C: derive colour application hint |
-| `validation-prompt.md` | Phase D: 9-check guideline validation |
-
----
-
-## Output files (per app)
-
-```
-<appDir>/
-  docs/cms-guidelines/
-    html-component-style-guide.md     # design system reference (auto-generated; static fragment)
-    components/          # one .md per componentType
-    collections/         # one .md per collectionType
-    externals/           # one .md per externalComponentType
-    COMPONENT_GUIDELINES_FOR_LLM.md   # merged document (includes style guide as preamble)
-  generated/cms-discovery/
-    field-list.json
-    colour-hints.json
-    accepted-variants/
-      components/        # one .json per component type
-      collections/       # one .json per collection type
-      externals/         # one .json per external component type
-    screenshots/
-      components/        # PNG screenshots for components
-      collections/       # PNG screenshots for collections
-      externals/         # PNG screenshots for externals
-      index.json         # file field uses subpath e.g. "components/hero-default.png"
-```

package/skills/contentful-cms/cms-guidelines/colour-hint-prompt.md

@@ -1,77 +0,0 @@
-# Colour Hint Prompt
-
-**Step 5.2 — Produce a structured colour hint per CMS type.**
-
-The colour hint is a short machine-readable label describing how `backgroundColour` and
-`textColour` are applied in this component. It is stored in
-`generated/cms-discovery/colour-hints.json` and served by the discovery API.
-
----
-
-## Purpose
-
-The colour hint helps tools and LLMs quickly understand how colours work without reading
-the full guideline. For example:
-
-- `"section"` → the colour applies to the full-width section (both copy and visual columns).
-- `"card"` → the colour is applied per-card inside a collection.
-- `"none"` → this type does not use backgroundColour/textColour.
-
----
-
-## Valid hint values
-
-| Value | Meaning |
-|---|---|
-| `"section"` | backgroundColour/textColour apply to the full-width section wrapper (most components) |
-| `"card"` | Colours apply per-card (collection items); section has no colour |
-| `"section+card"` | Both section-level and card-level colours exist |
-| `"none"` | The type does not use backgroundColour or textColour |
-
----
-
-## Prompt (to run as part of generation)
-
-```
-You are writing a colour hint for a CMS component documentation system.
-
-Component: <COMPONENT_TYPE>
-Component source:
-<COMPONENT_SOURCE>
-
-Section.tsx source (shows how backgroundColour/textColour are applied at section level):
-<SECTION_SOURCE>
-
-Look at how backgroundColour and textColour are used in the source.
-
-Rules:
-- If backgroundColour/textColour are in USED_FIELDS AND passed to a Section wrapper (or
-  similar full-width wrapper): hint = "section"
-- If backgroundColour/textColour are applied per-card in a collection: hint = "card"
-- If both are true: hint = "section+card"
-- If neither backgroundColour nor textColour is in USED_FIELDS: hint = "none"
-
-Output JSON only:
-{
-  "typeName": "<COMPONENT_TYPE>",
-  "colourApplication": "section",
-  "notes": "backgroundColour and textColour applied to the full Section wrapper."
-}
-```
-
----
-
-## Script to update colour-hints.json
-
-Run the script after generating each component:
-
-```bash
-cms-update-colour-hints --type "Hero" --hint "section" \
-  --notes "backgroundColour and textColour applied to the full Section wrapper."
-```
-
-Or provide an LLM-generated JSON file:
-
-```bash
-cms-update-colour-hints --from /tmp/hero-colour-hint.json
-```

package/skills/contentful-cms/cms-guidelines/evaluation-prompt.md

@@ -1,84 +0,0 @@
-# Evaluation Prompt — Screenshot Differences
-
-**Step 4.3 — Prompt for evaluating whether captured screenshots are suitably different.**
-
-The evaluation step is used by the orchestrator (Step 4.4) to decide whether to accept the
-current set of screenshots, or to request additional variants (up to the 2×N cap).
-
----
-
-## When to run
-
-After `cms-capture-screenshots` has captured a batch of screenshots, feed them to an LLM with
-this prompt. The LLM inspects the images and returns a verdict.
-
----
-
-## Prompt
-
-```
-You are reviewing a set of component screenshots for CMS documentation purposes.
-
-Your task: decide whether this set of screenshots is "suitably different" — meaning
-each screenshot looks visually distinct enough that a reader could tell them apart,
-and together they cover the important visual states of the component.
-
-Component: <COMPONENT_TYPE>
-Screenshots (attached as images):
-<LIST OF {label, path, description} PAIRS>
-
-Rules:
-1. Two screenshots are "not different enough" if they look nearly identical — same layout,
-   same colours, same content, just minor text length differences.
-2. The set is "suitably different" if:
-   - At least two screenshots have clearly different layouts (e.g. one has a visual, one does not), OR
-   - At least two screenshots have clearly different colour schemes (e.g. one light, one dark), OR
-   - At least two screenshots show clearly different content (e.g. one full, one minimal).
-3. A set with only one screenshot is NEVER "suitably different" — we need at least two variants.
-
-Output JSON only:
-{
-  "suitablyDifferent": true,
-  "reason": "Short explanation of why the set is or is not diverse enough.",
-  "acceptedVariants": ["default", "navy", "no-visual"],
-  "rejectedVariants": ["minimal"],
-  "suggestions": [
-    "The 'minimal' variant looks too similar to 'no-visual'. Try a variant with a tinted background
-     instead, e.g. Pine background."
-  ]
-}
-
-- acceptedVariants: labels of screenshots that are good to keep.
-- rejectedVariants: labels that are too similar to others or not useful.
-- suggestions: optional list of new variant ideas to try if suitablyDifferent is false
-  (or if any variant was rejected).
-- If suitablyDifferent is true, suggestions can be empty.
-```
-
----
-
-## Output contract
-
-```json
-{
-  "suitablyDifferent": true,
-  "reason": "The default and navy variants have clearly different colour schemes. The no-visual variant shows a different layout. Together they document the main visual states.",
-  "acceptedVariants": ["default", "navy", "no-visual"],
-  "rejectedVariants": ["minimal"],
-  "suggestions": [
-    "Consider replacing 'minimal' with a Pine background variant to show a green colour scheme."
-  ]
-}
-```
-
----
-
-## How the orchestrator uses this
-
-1. If `suitablyDifferent === true` AND all variants are accepted → stop; use the accepted set.
-2. If `suitablyDifferent === false` OR any variants were rejected:
-   - If `attempts < 2 × N` → use `suggestions` to generate additional variant params; capture
-     the new screenshots; re-evaluate.
-   - If `attempts >= 2 × N` → stop; use `acceptedVariants` from the best evaluation so far.
-3. The final accepted set is written to `generated/cms-discovery/accepted-variants/{components|collections|externals}/<type-slug>.json`
-   and the screenshots are committed to `docs/cms-guidelines/screenshots/{components|collections|externals}/`.