@se-studio/project-build 1.0.122 → 1.0.123

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @se-studio/project-build
 
+## 1.0.123
+
+### Patch Changes
+
+- Bulk version bump: patch for all packages
+
 ## 1.0.122
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/project-build",
-  "version": "1.0.122",
+  "version": "1.0.123",
   "description": "Build tools and management scripts for SE Studio projects",
   "repository": {
     "type": "git",

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

@@ -0,0 +1,60 @@
+---
+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/manifest.json

@@ -3,5 +3,8 @@
   "templates": "Create and edit templates (preContent, postContent, menu, footer, colours)",
   "navigation": "Create navigation, nav open/add, set nav item fields, remove",
   "rich-text": "Rich text (rtf) and embeds (append/insert); Markdown support",
-  "screenshots": "Screenshot command, agent-browser requirement, mock vs live, --url-only"
+  "screenshots": "Screenshot command, agent-browser requirement, mock vs live, --url-only",
+  "alt-text-audit": "Audit and improve image alt text across site pages",
+  "seo-descriptions": "Generate or improve SEO meta descriptions for pages",
+  "schema-org": "Generate Schema.org structured data as Mustache templates"
 }

package/skills/contentful-cms/schema-org/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: "Schema.org Generation"
+description: "Generate Schema.org structured data as Mustache templates for site pages and upload via cms-edit."
+---
+
+# Skill: contentful-cms — Schema.org Generation
+
+Use this skill when generating **Schema.org structured data** (JSON-LD) as Mustache templates for pages and uploading via `cms-edit`. Works with any brand context skill for customer name and site URL.
+
+## Brand Context
+
+Before starting, check if a brand context skill is available. You'll need the customer name and site URL for Organisation and publisher fields in the schema templates.
+
+If no brand context is available, ask the user for these details.
+
+## Phase 1: Analyse Site Structure
+
+1. `cms-edit sitemap` to get all pages and articles
+2. For each page, use `fetch_page_markdown` (from site-workflows MCP server) to read content
+3. Categorise each page by Schema.org type:
+
+| Page Type | Likely Schema.org Type |
+|-----------|----------------------|
+| Homepage | Organization + WebSite |
+| About | AboutPage + Organization |
+| Service/Product | Service or Product |
+| Pricing | Product with Offer |
+| Blog listing | CollectionPage |
+| Article | Article or BlogPosting |
+| FAQ | FAQPage with Question/Answer |
+| Contact | ContactPage |
+| Team/People | ProfilePage or Person |
+| Case study | Article |
+| Landing page | WebPage |
+
+## Phase 2: Generate Mustache Templates
+
+Create JSON-LD templates using these standard Mustache variables:
+
+- `{{title}}` — page/article title
+- `{{seoDescription}}` — SEO meta description
+- `{{slug}}` — page slug
+- `{{publishDate}}` — article publish date
+- `{{updatedAt}}` — last modification date
+- `{{authorName}}` — article author name
+- `{{heroImageUrl}}` — primary image URL
+- `{{customerName}}` — from brand context
+- `{{siteUrl}}` — from brand context
+
+## Phase 3: Upload via cms-edit
+
+1. Check available fields:
+   - `cms-edit schema page` — page content type fields
+   - `cms-edit schema template` — template content type fields
+   - Look for `schemaOrg`, `jsonLd`, `structuredData`, or similar
+2. For **template-level** schemas (Organization, WebSite — shared): `cms-edit list --type template` → open → set
+3. For **page-level** schemas: open each page → set its schema field
+4. `cms-edit diff` then `cms-edit save`
+
+## Best Practices
+
+- Don't duplicate — template-level Organization schema covers all pages
+- Use specific types — `MedicalBusiness` over `LocalBusiness` if applicable
+- Validate all required properties are present
+- Schema must reflect actual page content
+
+## Output
+
+| Page/Template | Schema.org Type(s) | Variables Used | Applied To |
+|--------------|-------------------|---------------|-----------|
+
+## Related skills
+
+See the **core** skill for the full cms-edit workflow. See the **seo-descriptions** skill for meta description generation.

package/skills/contentful-cms/seo-descriptions/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: "SEO Descriptions"
+description: "Generate or improve SEO meta descriptions for pages using cms-edit, targeting keywords with the brand voice."
+---
+
+# Skill: contentful-cms — SEO Descriptions
+
+Use this skill when generating or improving **SEO meta descriptions** for pages using `cms-edit`. Works with any brand context skill for customer-specific voice and audience.
+
+## Brand Context
+
+Before starting, check if a brand context skill is available (e.g., "OM1 Brand Context"). If so, use its brand voice, target audience, SEO focus areas, and tone when writing descriptions.
+
+If no brand context is available, ask the user about their brand voice and target audience before proceeding.
+
+## Workflow
+
+1. **Get all pages**: `cms-edit sitemap`
+2. **For each page** (or a specific page):
+   a. **Read page content** using `fetch_page_markdown` (from the site-workflows MCP server) to understand what the page covers
+   b. **Check current SEO**:
+      - `cms-edit open /<slug>`
+      - `cms-edit read @page seoDescription` (or `read @page` for all fields)
+   c. **Analyse** the page — primary purpose, problem it solves, desired user action
+   d. **Generate** a meta description following the guidelines below
+   e. `cms-edit set @page seoDescription "new description"`
+   f. `cms-edit diff` then `cms-edit save`
+
+## Meta Description Guidelines
+
+1. **Length:** 150–160 characters (Google truncates at ~160)
+2. **Include the target keyword** naturally — don't stuff it
+3. **Use the brand voice** from the brand context
+4. **Include a call to action** — "Learn more", "Get started", "Discover", etc.
+5. **Be specific** — mention concrete benefits, not vague claims
+6. **Match search intent** — what would someone search to land on this page?
+7. **Avoid:**
+   - Starting with the brand name (it's in the title tag)
+   - "Welcome to..." or "This page is about..."
+   - Duplicating descriptions across pages
+   - Quotes (truncated in SERPs)
+
+## Output
+
+For each page, present:
+
+| Page | Current Description | New Description | Chars | Target Keyword |
+|------|-------------------|-----------------|-------|----------------|
+
+Then apply changes via cms-edit.
+
+## Related skills
+
+See the **core** skill for the full cms-edit workflow. See the **alt-text-audit** skill for image accessibility.