@se-studio/skills 1.6.6 → 1.6.8

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @se-studio/skills
 
+## 1.6.8
+
+### Patch Changes
+
+- d74ec5c: Document Figma-as-absolute-gospel for new UI work in site-workflows-agent-session (until the user overrides).
+
+## 1.6.7
+
+### Patch Changes
+
+- 325ef89: cms-edit hosted MCP Production is the marketing production branch (`main` / HSD `production`), not `develop`.
+
 ## 1.6.6
 
 ### Patch Changes

package/package.json

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

package/references/deployment-smoke-feature-branch-skip/README.md

@@ -30,10 +30,10 @@ See [`workflow-snippet.yml`](workflow-snippet.yml). One skip job per Vercel proj
 Feature-branch PRs also trigger cms-edit Vercel projects. Skip builds outside integration branches via `ignoreCommand` in `cms-edit/host/vercel.json`:
 
 ```json
-"ignoreCommand": "if [ \"$VERCEL_GIT_COMMIT_REF\" != \"develop\" ] && [ \"$VERCEL_GIT_COMMIT_REF\" != \"main\" ]; then exit 0; fi; git diff HEAD^ HEAD --quiet -- . ../ ../../pnpm-lock.yaml ../../pnpm-workspace.yaml ../../package.json || exit 1; exit 0"
+"ignoreCommand": "if [ \"$VERCEL_GIT_COMMIT_REF\" != \"main\" ]; then exit 0; fi; git diff HEAD^ HEAD --quiet -- . ../ ../../pnpm-lock.yaml ../../pnpm-workspace.yaml ../../package.json || exit 1; exit 0"
 ```
 
-Replace `develop` with your integration branch if the registry uses a different name.
+HSD: use `production` instead of `main`. Skip `develop` and feature refs so cms-edit Production is not a Preview of `develop`.
 
 ## Rollout status
 
@@ -44,7 +44,7 @@ Replace `develop` with your integration branch if the registry uses a different
 | om1-website | audit | audit |
 | pedestal-sites | audit | audit |
 | pointme | audit | audit |
-| hsd | audit | audit (align ignoreCommand with `develop`) |
+| hsd | audit | audit (align ignoreCommand with `production`) |
 
 Update this table when applying the pattern.
 

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

@@ -62,8 +62,13 @@ cms-edit open --id 4xKj2abcDef
 
 # Home page (slug is 'index')
 cms-edit open --page-slug /
+
+# Include template menu/footer/nav (default open skips site chrome)
+cms-edit open --include-chrome --page-slug /pricing
 ```
 
+`open` / `peek` fetch the page (or article) tree and the template entry, but **not** template `menu` / `footer` / navigation. Edit nav with `nav open`. Pass `--include-chrome` only when you need those trees.
+
 **Flat lookup flags:** provide **exactly one** primary flag per `open` / `resolve` / `nav open`. See `cms-edit help lookup`. Run `cms-edit index sync` so catalog types resolve from the local index.
 
 ### Step 2: Read the snapshot

package/skills/contentful-cms-regenerate-editor-pack/SKILL.md

@@ -89,10 +89,11 @@ git commit -m "chore(cms-edit): regenerate editor pack"
 
 ### Customer repo with `cms-edit/host/` (SE Studio, Pedestal, Headwater, Brightline, …)
 
-Commit `editor-pack/` (and any other `cms-edit/**` changes), then push to the branch Vercel watches (usually `develop`). Changes under `cms-edit/**` trigger a host rebuild (`stage-site.mjs` copies committed artifacts on the Vercel build).
+Commit `editor-pack/` (and any other `cms-edit/**` changes) and push **`develop`**. Hosted MCP Production is the marketing production branch (`main`, HSD `production`) — a **human** merge publishes. `ignoreCommand` skips `develop` and feature refs.
 
 ```bash
-git push origin develop   # or the site's configured deploy branch
+git push origin develop
+# then hand off: human merges to main (HSD: production)
 ```
 
 Do **not** run `pnpm cms-edit:deploy` or `vercel deploy` after this step.

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

@@ -87,6 +87,7 @@ Standard order when diff shows these gaps:
 | 5 | `15-add-slug-regexp-validation.js` | Slug format validation |
 | 6 | `17-add-article-authors.js` | `article.authors` array + backfill from `author` |
 | 7 | `21-add-article-bottom-content.js` | `article.bottomContent` array (idempotent; clones `content` link types) |
+| 8 | `25-add-meta-field.js` | Optional Long text `meta` JSON bag on template/page/article/tag/person and related types. Idempotent. Unused until filled. |
 
 Site-specific (run only when diff shows missing field **and** app uses it):
 

package/skills/site-workflows-agent-session/SKILL.md

@@ -212,6 +212,22 @@ Record `cms_session: <feature-slug>` in manifest when doing CMS work.
 - **Do not** edit `se-core-product` unless placement is `core` and user approves mode switch
 - Consume `@se-studio/*` from npm — not monorepo workspace links
 
+### Figma is absolute gospel (new designs)
+
+**Until the user explicitly says otherwise**, when implementing or polishing UI from a Figma file or node:
+
+| Do | Do not |
+|----|--------|
+| Treat the named Figma node as the **source of truth** for structure, spacing, type, colour, radii, alignment, and control patterns | “Improve”, normalize, or restyle away from the comps to match older site patterns |
+| Pull design context / screenshots from the owned Figma file before coding or “fixing” visuals | Prefer CMS draft copy, prior app screenshots, or memory of the live site over the comps |
+| Match **pixel-faithfully** (including pills vs checkboxes/radios, hug vs full-width CTAs, card fills) | Ship “close enough” and wait for the user to notice |
+| If Figma conflicts with an existing component or token, **follow Figma** and note the deviation | Silently keep the old pattern because it is already in the codebase |
+| Verify in the browser against the Figma node (desktop + mobile when both exist) | Declare done from a single screenshot that does not match the node |
+
+**Override:** Only diverge when the user clearly says so in the current conversation (e.g. “ignore Figma for the button”, “use site chrome instead”). Until that override, Figma wins.
+
+**Related skills:** `site-workflows-figma-design-snapshot` / `site-workflows-apply-design-snapshot` for token sync; Figma MCP `get_design_context` for node-level implementation.
+
 ### Blocked work
 
 If manifest has `blocked_on: "@se-studio/foo@1.2.3"`, do not push customer `develop` until npm publish is confirmed. Update manifest when unblocked.