@se-studio/skills 1.9.11 → 1.9.16

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # @se-studio/skills
 
+## 1.9.16
+
+### Patch Changes
+
+- 049abbb: Document how to place a designed HTML page: site chrome stays in the template, editor-owned or repeated sections become registered components, and HtmlComponent is only for a developer-owned island. Specimens drop embedded fonts, a second colour palette, raw forms, and hand-rolled analytics.
+
+## 1.9.15
+
+### Patch Changes
+
+- f03f1f1: Document the weekly production Screaming Frog fleet audit.
+
+## 1.9.14
+
+### Patch Changes
+
+- 3d4f180: State the marketing-route and layout rules in the customer architecture block, the session skill, and the page and styling skills. A new URL is a Contentful slug. Frame width is not a max-width, and a missing text style stops the plan instead of becoming `leading-[…]`.
+
+## 1.9.13
+
+### Patch Changes
+
+- b47c1c2: Implement se-core #252 anti-Webflow-port BLOCKERs plus Nick simplicity rules (no RTF flatten, links as-is, no hardcoded visitor copy, Tailwind over CSS islands, fail closed). Add skill `se-marketing-sites-customer-simplicity`, wire from agent-session, and soften globals.css / customCss escape hatches.
+
+## 1.9.12
+
+### Patch Changes
+
+- fbb6952: Document Option C editor-pack publish via customer CI (reusable GitHub Actions workflow). Agents regenerate and commit packs only; they do not run `gh release create` unless Nick asks.
+
 ## 1.9.11
 
 ### Patch Changes

package/package.json

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

package/references/agent-session/customer-agents-block.md

@@ -28,7 +28,7 @@ Before non-trivial code, run the placement checklist (in the skill). Summary:
 
 | Belongs in… | Examples |
 |-------------|----------|
-| **This repo** (`src/project/*`, `cms-edit/**`) | Brand components, styling, site routing, editor-pack |
+| **This repo** (`src/project/*`, `cms-edit/**`) | Brand components, styling, editor-pack, and `src/lib/marketing-routes.json` (which article-type and person-type folders exist). A new URL is a Contentful slug, not a new `page.tsx`. |
 | **Customer shared package** (if monorepo) | Consent/analytics shared across sites in this customer |
 | **`se-core-product`** (`@se-studio/*`) | Fixes/features needed by 2+ sites, CMS infrastructure |
 

package/references/agent-session/customer-architecture.mdc

@@ -24,8 +24,18 @@ Source of truth: `se-core-product` `docs/PHILOSOPHY.md`. Code review: `CODE_REVI
 
 - Keep T0/T1 skeleton files thin; document deviations in the site README.
 - Use core route handlers (`generatePage`, robots, sitemaps, etc.). Do not reimplement.
+- A new marketing URL is a Contentful page slug (use `indexed: false` for an experiment). Do not add `src/app/**/page.tsx` for it. App Router pages are the CMS catch-all, a folder named in `src/lib/marketing-routes.json` for an article type or a person type, and the fixed misc files (page-test, preview, sitemap, robots, markdown, download, og, api, cms-dev).
+- Every marketing block is `<Section>` with `content-cols-grid`. Width is `col-span-*`, `max-w-cols-N`, or `max-w-cols-gap-N`. Type is a `fontTable` class (`h1`, `p2`, `sizingInformation.*`). Vertical space is `section-spacing` on `Section`.
+- Figma stays the source for layout, copy, colour, and type when a text style is set. Implement with the grid and the font table. Do not paste MCP arbitrary classes.
+- Plan-time stops: the frame width (1440, 1920, whatever the artboard is) is not `max-w-[…]`. Type with no text style (`leading-[1.2]`, raw `text-[32px]`) means the designer did not specify the font — name the node and wait. Do not pick a class and continue.
 - Mobile-first Tailwind. Preserve heading hierarchy. Size visuals with core helpers. Avoid duplicate mobile/desktop markup for the same content.
 - UI changes: early Vercel preview (mobile + laptop) → Nick visual → full breakpoints including oversize (~1920+) before deep polish/code review.
+- **Remakes are not Webflow reconstruction** (PHILOSOPHY §5a / `se-marketing-sites-customer-simplicity`):
+  - CMS entry → registered component/collection only; **fail closed** when a field is empty (omit UI / fix CMS — never invent from the live site).
+  - Body/`additionalCopy` via `RtfOrString` — no RTF→plain flatten for layout.
+  - CMS `links` as-is with standard link helpers — no invented roles unless Nick asks.
+  - No hardcoded visitor copy, live URLs, or brand media fallbacks in TS.
+  - Tailwind + design tokens over CSS islands; do not grow Webflow-ported page CSS. `globals.css` / HtmlComponent `customCss` for true one-offs or shared primitives only.
 
 ## Caching / performance / images
 

package/references/agent-session/customer-code-review.md

@@ -52,14 +52,28 @@ Run all five lenses. Skip a lens only when the diff clearly cannot touch it (say
 - Consent granted by default where a CMP decides, or bypassing site consent gating.
 - Forms: preview posting to production CRM/forms destinations or GTM, or bypassing server-side submit.
 - Hard-coded heading skips, `Visual` without size helpers, or needless duplicate mobile/desktop content.
+- A new `src/app/**/page.tsx` for a marketing URL. That URL is a Contentful slug (often `indexed: false` for an experiment). Allowed app pages: the CMS catch-all, an article type or person type named in `src/lib/marketing-routes.json`, and the fixed misc set (page-test, preview, sitemap, robots, markdown, download, og, api, cms-dev).
+- Arbitrary layout standing in for the grid or an unspecified text style: `max-w-[1440px]` or `max-w-[1920px]` (that number is the Figma frame, not a max-width), `leading-[…]` / `text-[32px]` with no `fontTable` class, section padding via `py-[…]` instead of `<Section>`, `content-cols-grid`, and `max-w-cols-N`. Name the Figma node in the plan and wait. Do not guess a style and do not paste MCP classes.
 - Failing typecheck, lint, or tests; new behaviour with no test where the site already tests that layer.
 - Smoke/discovery/`server-config` hacks to unblock deploy smoke (belongs in `@se-studio/site-check`).
+- **Remake / port simplicity** (PHILOSOPHY §5a / skill `se-marketing-sites-customer-simplicity`):
+  - Stub or heading-match fallback as the live renderer; unfinished types must stay unregistered or preview-only.
+  - Catalogue fetch (`getAllArticleLinks` / `getAllPersonLinks` / walking another page) inside a component or layout.
+  - Layout/behaviour multiplex on `cmsLabel` / heading / `anchor` (type ≠ label).
+  - Flattening body/`additionalCopy` RTF → plain strings or paragraph heuristics to drive layout (use `RtfOrString`).
+  - Inventing or filtering CMS `links` into roles / special chrome unless Nick explicitly asked.
+  - Hardcoded visitor copy, live URLs, CDN paths, or brand media fallbacks in TS — fix CMS instead.
+  - New Webflow/FlowKit CSS dumps or growing page CSS islands (`etf.css`-style, `fk-*`, minified sheets) for layout; prefer Tailwind + tokens. `globals.css` / `customCss` only for true one-offs or shared primitives.
+  - Filling missing CMS by inventing from the live site (must **fail closed**: omit UI or fix CMS).
+  - Second public URL system or custom App Router page for a type `generatePage` already covers.
+  - Mixed `@se-studio/*` majors on one site without an aligned bump plan.
 
 **NIT**
 
 - Prefer existing core components over one-offs.
 - Don’t rename existing tracking events only to match other sites.
 - Clearer names, smaller functions, docs polish.
+- Pixel-perfect vs Figma before the early visual gate (not a merge blocker early). Webflow remakes follow CMS→component + tokens, not pixel CSS dumps.
 
 ---
 
@@ -70,7 +84,7 @@ If the PR changes UI, confirm the session followed agent-session visual phases:
 1. **Early:** Vercel preview, mobile (~390) + laptop (~1280), stopped for Nick’s visual review.
 2. **Full (after Nick is happy):** tablet (~768), laptop (~1280), **oversize (~1920+)**, plus mobile — flag overflow, stretched heroes, broken grids.
 
-Do not treat “pixel-perfect vs Figma” as a merge blocker before the early visual gate completes.
+Do not treat “pixel-perfect vs Figma” as a merge blocker before the early visual gate completes. Remakes from live Webflow/HTML are **not** a fidelity chase against the old site — implement CMS fields with tokens; flag invented structure as **BLOCKER** above.
 
 ---
 

package/references/contentful-cms-cms-guidelines/html-component-authoring.md

@@ -9,7 +9,32 @@ metadata:
 
 # HtmlComponent Authoring Guide
 
-`HtmlComponent` is a CMS content type that renders developer-authored HTML directly into the page. It bypasses the standard component registration system and is intended for one-off or highly custom layouts that the structured component library cannot produce.
+`HtmlComponent` is a CMS content type that renders developer-authored HTML directly into the page. It bypasses the standard component registration system.
+
+Author it only after the recorded call is **keep**. That call is in `packages/contentful-cms/docs/editor-tasks/create-html-component.md`. A layout the library cannot produce does not keep the section. A registered type that could render it does not promote the section. Do not use HtmlComponent + `customCss` to reconstruct a Webflow page. See `se-marketing-sites-customer-simplicity` and PHILOSOPHY §5a.
+
+---
+
+## From a designed page file
+
+A self-contained HTML file (nav, page, footer, embedded font) is a specimen. Do not paste it into `rawHtml`. The shelf decision is in `packages/contentful-cms/docs/editor-tasks/create-html-component.md` (`cms-edit://customer/task-create-html-component`):
+
+| Shelf | When |
+|-----|------|
+| Site layout | Nav, footer, menu, contact panel. Leave them in the file. |
+| Registered component | An editor will change the words, media, or links, or the section repeats (on this page or another). Build or reuse a component. Do not author it here. |
+| `HtmlComponent` | The recorded call is **keep**: a developer will own it, editors will not change the words, media, or links, and it does not repeat. A layout match does not decide this. A first version gets the same keep-or-promote call. Continue below only after **keep**. |
+
+When the shelf is `HtmlComponent`:
+
+- Drop `@font-face` and embedded font files. The site already loads the brand font.
+- Drop a second `:root` palette. Use the named colour and type classes in the project style guide. Motion that those classes cannot express goes in `customCss`, using the site’s existing tokens.
+- Do not paste a `<form>`. Forms use the site’s registered form.
+- Do not push to `dataLayer` from `customJs`. `HtmlComponent` does not emit analytics. Clicks that must be measured are registered links.
+- One page has one `h1`. Set `isHero` only when this block is that heading.
+- Fill `markdownContent` with the visible sentences.
+
+Regenerate `html-component-style-guide.md` only when that site’s tokens have changed.
 
 ---
 

package/skills/coding-discipline/SKILL.md

@@ -299,7 +299,7 @@ export const HeroRenderer: ComponentRenderer<ProjectConfig> = ({ information })
 
 ## Code Style Requirements
 
-- **Styling**: Tailwind only. Do not use CSS modules (`*.module.css`). Use Tailwind classes or `src/app/globals.css` for shared styles.
+- **Styling**: Tailwind utilities + design tokens first. Do not use CSS modules (`*.module.css`). Prefer classes in TSX over new CSS. `src/app/globals.css` is for **shared primitives only** (keyframes, RTF element maps, true design-system utilities) — not per-page Webflow/layout reconstruction. Growing page CSS islands is review debt (see `se-marketing-sites-customer-simplicity`).
 - **Biome** for linting/formatting (not ESLint/Prettier)
 - Single quotes, semicolons, trailing commas
 - `import type` for type-only imports

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

@@ -91,10 +91,14 @@ git add cms-edit/editor-pack   # or cms-edit/<site>/editor-pack
 git commit -m "chore(cms-edit): regenerate editor pack"
 ```
 
-## Step 6 — Publish (commit + push only)
+## Step 6 — Publish (commit + push; CI owns GitHub Releases)
 
 **Absolute rule for agents:** hosted MCP is **never** published via `vercel deploy`, `pnpm cms-edit:deploy*`, or `deploy-cms-edit-host.sh`. Commit and push is the only deploy path for customer repos with `cms-edit/host/`.
 
+**Option C (shared multi-tenant host):** Customer CI publishes the committed pack as a GitHub Release (`editor-pack.tar.gz`) via the reusable workflow `Something-Else-Studio/se-core-product/.github/workflows/cms-edit-pack-publish.yml`. Agents do **not** run `gh release create` (or treat the printed command from `cms-edit host pack-publish` as something to execute) unless Nick explicitly asks. Do **not** regenerate the pack in CI — publish the committed `editor-pack/` only. Tags are immutable (`cms-edit-pack-<projectKey>-v<version>`); bump version for a new Release, then update the host registry `packTag` when intentional.
+
+See `packages/contentful-cms/HOSTED.md` (Option C section) for the caller workflow sketch.
+
 ### Customer repo with `cms-edit/host/` (SE Studio, Pedestal, Headwater, Brightline, …)
 
 Commit `editor-pack/` (and any other `cms-edit/**` changes) and push **`develop`**. Hosted MCP Production is the marketing production branch (`main`, HSD `production`). Merge there only after ask + confirm (`production-merge.md`). `ignoreCommand` skips `develop` and feature refs.
@@ -108,7 +112,7 @@ Do **not** run `pnpm cms-edit:deploy` or `vercel deploy` after this step.
 
 ### Customers without `cms-edit/host/` in their repo
 
-Rare layout — coordinate with the repo owner. Agents still must not run deploy scripts unless explicitly asked.
+Rare layout — coordinate with the repo owner. Agents still must not run deploy scripts unless explicitly asked. For Option C tenants, pack publish still goes through customer CI → GitHub Release (same reusable workflow), not a local `gh release create`.
 
 ## Homepage slug reminder
 

package/skills/screaming-frog-audit/SKILL.md

@@ -59,6 +59,20 @@ Prioritized P0–P3 report from a single crawl export.
 
 ---
 
+## Fleet production audit
+
+From se-core-product, crawl every marketing production site and write P0–P3 reports. One site at a time. Quit the Screaming Frog GUI first.
+
+```bash
+pnpm seo:screaming-frog:fleet          # crawl + audit
+pnpm seo:screaming-frog:fleet -- --list
+node scripts/screaming-frog-fleet.mjs --install-agent
+```
+
+Reports land in `~/spider/fleet-audits/<YYYY-MM-DD>/`. The command does not pass `--tag`, so it does not replace a deployment `content` baseline. `--install-agent` loads a user LaunchAgent (`studio.se.screaming-frog-fleet`) for Sunday 22:00 local time.
+
+Start URL: the manifest `production` profile. When that profile is a `*.vercel.app` alias and cms-edit `productionSiteUrl` is a public host, the public host is crawled. Eagle stays on its configured Vercel production URL. Preview-only issue downgrades (noindex, preview robots) are not applied.
+
 ## Other commands
 
 ```bash

package/skills/se-marketing-sites-cms-routes-and-appshared/SKILL.md

@@ -7,6 +7,8 @@ description: "Guide for the (cms-routes) route group and appShared pattern. Use
 
 Reference app: **example-empty** (this monorepo). Customer sites with fuller route sets: see `docs/RELATED_PROJECTS.md` (e.g. OM1 uses `resources/`, `team/`, `topics/` instead of `articles/`, `people/`, `tags/`).
 
+Do not add a `page.tsx` for a marketing URL. That URL is a Contentful slug on the catch-all. Extra folders are only article types and person types listed in `src/lib/marketing-routes.json`.
+
 ## Route Group: (cms-routes)
 
 All CMS-driven pages live under `src/app/(cms-routes)/`. The layout enables dynamic params:
@@ -29,9 +31,9 @@ export default function CmsRoutesLayout({ children }: { children: React.ReactNod
 | `/{slug1}/{slug2}/...` | `[level1]/[...slugs]/page.ts` | Multi-level pages |
 | `/articles/` | `articles/page.ts` | Articles index (uses ARTICLES_BASE) |
 | `/articles/{type}/` | `articles/[articleType]/page.ts` | Article type index |
-| `/articles/{type}/{tag}/` | `articles/[articleType]/[tag]/page.ts` | Article type + tag index |
-| `/articles/{type}/{tag}/{article}/` | `articles/[articleType]/[tag]/[...slugs]/page.ts` | Individual article |
-| `/tags/`, `/tags/{tag}/` | `tags/` | Tag index (if enabled) |
+| `/articles/{type}/{tag}/` | `articles/[articleType]/[tag]/page.ts` | Article type + tag index. Only when that base sets `tagInPath: true`. Hand-written `generateArticleTypeTag*` page. |
+| `/articles/{type}/{tag}/{article}/` | `articles/[articleType]/[tag]/[...slugs]/page.ts` | Individual article with a tag segment. Same `tagInPath` rule. |
+| `/tags/`, `/tags/{tag}/` | `tags/` | Tag index when `tags: true` |
 | `/people/`, `/people/{person}/` | `people/` | People (if enabled) |
 
 Base paths come from `@/lib/constants` (e.g. ARTICLES_BASE = `/learning-hub` or `/articles`).
@@ -97,7 +99,7 @@ export default async function (props: PageProps<'/[level1]'>) {
 }
 ```
 
-For article routes, use `converterContext.urlCalculators.article`, `articleType`, `articleTypeTag` to compute the path. Import `converterContext` from `@/lib/converter-context` when that module exists (so route files don't pull in cms-server); otherwise from `@/lib/cms-server`.
+A dynamic `articles` route uses `converterContext.urlCalculators` (`article`, `articleType`, `articleTypeTag`). Import `converterContext` from `@/lib/converter-context` when that module exists (so route files don't pull in cms-server); otherwise from `@/lib/cms-server`. A fixed article folder, and a dynamic base whose path is not `articles`, passes the path of that file (`/work/`, `/work/${articleSlug}/`). `article()` prefixes `ARTICLES_BASE` and, when primary tags are on, inserts `other`. That is a different URL from the file that was written. The generator does this. Hand-written `[tag]` pages still use `articleTypeTag`.
 
 ## See Also
 

package/skills/se-marketing-sites-create-collection/SKILL.md

@@ -293,3 +293,8 @@ export const MyCollectionRegistration = defineCollection({
     *   New UI or behaviour → new Contentful `collectionType` enum value + registration. Never `if (cmsLabel)` / parse labels for layout or renderer choice.
     *   `cmsLabel` is for authors (and may pass to `trackingLocation`); it is not a runtime discriminator.
     *   Position/variant-only differences may share one Core under multiple `defineCollection` registrations; drive layout from `collectionType`.
+9.  **Simplicity (remakes / ports)**:
+    *   Do **not** flatten item body fields for layout; use `<RtfOrString>`.
+    *   Do **not** invent link roles from CMS `links` unless Nick asks.
+    *   Prefer Tailwind tokens over CSS islands; empty fields → omit (**fail closed**).
+    *   Load `se-marketing-sites-customer-simplicity` on remake tasks.

package/skills/se-marketing-sites-create-component/SKILL.md

@@ -1,12 +1,20 @@
 ---
 name: se-marketing-sites-create-component
-description: "Guide for creating new CMS-driven components in the SE Core Product monorepo. Use this skill when asked to create a new component, ensuring adherence to the 4-layer architecture."
+description: "Guide for creating new CMS-driven components in the SE Core Product monorepo. Use this skill when asked to create a new component, or when a designed HTML page needs a registered section. Ensures adherence to the 4-layer architecture."
 ---
 
 # Creating CMS Components
 
 This guide explains how to build new CMS-driven components following the established architecture patterns in this codebase.
 
+## When the brief is a designed HTML page
+
+Read `packages/contentful-cms/docs/editor-tasks/create-html-component.md` and record **keep** or **promote** for each section before writing code. A first version with no designed file gets the same call. Do not start the four layers until the call is **promote**. Do not open the HTML playbook until the call is **keep**.
+
+**Promote** is required when an editor will change the words, media, or links, or the section repeats (on this page or another). Then follow the four layers below. Do not paste the HTML document in as the component. Leave nav, footer, menu, and the contact panel to the page template.
+
+**Keep** is allowed only when a developer will own it, an editor will not change the words, media, or links, and it does not repeat. Motion, a tool demo, or vendor JS can be that island. A layout match does not promote it, and a new layout does not keep it. The keep path is the playbook above, including the project HTML style guide.
+
 ## Architecture Overview
 
 All components follow a **four-layer architecture** and must remain **Server Components** by default.
@@ -231,9 +239,10 @@ export const MyNewRegistration = defineComponent({
     *   Add `'use client'` to that file only.
     *   Import and use in Core component.
 5.  **Build Wrapper Component**:
-    *   Wrap Core with `<Section>`.
+    *   Wrap Core with `<Section>` (`content-cols-grid`, `section-spacing`). Do not replace Section with `max-w-[1440px]` or `py-16`.
     *   Pass `componentName={componentType}` and `information`.
-    *   Set layout (e.g., `positionClassName="col-span-full"`).
+    *   Set layout with `col-span-*`, `max-w-cols-N`, or `max-w-cols-gap-N`.
+    *   Type is a `fontTable` class or `sizingInformation.*`. A Figma frame width is not a max-width. A node with no text style (`leading-[1.2]`, raw `text-[32px]`) stops the plan — do not guess a class.
 6.  **Build Renderer**:
     *   Default export (short name).
     *   Wrap with `<UnusedChecker>`.
@@ -248,3 +257,9 @@ export const MyNewRegistration = defineComponent({
     *   New UI or behaviour → new Contentful `componentType` enum value + registration. Never `if (cmsLabel)` / parse labels for layout or renderer choice.
     *   `cmsLabel` is for authors (and may pass to `trackingLocation`); it is not a runtime discriminator.
     *   Position/variant-only differences may share one Core under multiple `defineComponent` registrations; drive layout from `componentType`.
+10. **Simplicity (remakes / ports)**:
+    *   Layers are the registration pattern — not an invitation to bespoke parsers.
+    *   Do **not** flatten body/`additionalCopy` for layout; use `<RtfOrString>`.
+    *   Do **not** invent or filter CMS `links` into roles unless Nick asks.
+    *   Prefer Tailwind tokens over new `globals.css` layout rules; CSS islands are debt.
+    *   Empty field → omit UI (**fail closed**). Load `se-marketing-sites-customer-simplicity` on remake tasks. Its HtmlComponent escape hatch does not move a section onto or off HtmlComponent after **keep** or **promote** is recorded.

package/skills/se-marketing-sites-create-page/SKILL.md

@@ -9,6 +9,18 @@ This guide explains how to create new pages and handle routing in the SE Core Pr
 
 Reference app: **example-empty** (this monorepo). Customer implementations: see `docs/RELATED_PROJECTS.md`.
 
+## Do not add a route for a marketing URL
+
+A new URL is a Contentful page slug, served by the catch-all (`[level1]` and `[...slugs]`). An experiment is a CMS page with `indexed: false`, not a new folder under `src/app`.
+
+App Router `page` files are only:
+
+- the CMS catch-all
+- a folder named in `src/lib/marketing-routes.json` for an article type or a person type (`node scripts/generate-marketing-routes.mjs <app> --write` writes the thin article index and detail wrappers; `[tag]` segments are hand-written when that base sets `tagInPath: true`)
+- the fixed misc files (page-test, preview, sitemap, robots, markdown, download, og, api, cms-dev)
+
+`pnpm skeleton:check` fails an extra `page.ts` once `marketing-routes.json` is present. Search and other non-page tools stay misc routes. They are not a second copy of a CMS page.
+
 ## Page Architecture
 
 ### 1. (cms-routes) Route Group
@@ -33,9 +45,9 @@ export default function CmsRoutesLayout({ children }: { children: React.ReactNod
 | `/{slug1}/{slug2}/...` | `[level1]/[...slugs]/page.ts` | Multi-level pages |
 | `/articles/` | `articles/page.ts` | Articles index (uses ARTICLES_BASE from constants) |
 | `/articles/{type}/` | `articles/[articleType]/page.ts` | Article type index |
-| `/articles/{type}/{tag}/` | `articles/[articleType]/[tag]/page.ts` | Article type + tag index |
-| `/articles/{type}/{tag}/{article}/` | `articles/[articleType]/[tag]/[...slugs]/page.ts` | Individual article |
-| `/tags/`, `/tags/{tag}/` | `tags/` | Tag index (if enabled) |
+| `/articles/{type}/{tag}/` | `articles/[articleType]/[tag]/page.ts` | Article type + tag index. Only when that base sets `tagInPath: true`. Hand-written `generateArticleTypeTag*` page. `--write` does not emit it. |
+| `/articles/{type}/{tag}/{article}/` | `articles/[articleType]/[tag]/[...slugs]/page.ts` | Individual article with a tag segment. Same `tagInPath` rule. |
+| `/tags/`, `/tags/{tag}/` | `tags/` | Tag index when `tags: true` |
 | `/people/`, `/people/{person}/` | `people/` | People (if enabled) |
 
 Base paths (e.g. `/articles` vs `/learning-hub`) come from `@/lib/constants`.
@@ -104,19 +116,9 @@ The appShared modules render content with:
 
 For route files that only need `converterContext` or `buildInformation` (e.g. `generateStaticParams`, sitemap, path computation), import from `@/lib/converter-context` when that module exists, so you don't pull in cms-server.
 
-## Creating a Specialized Route
-
-For a route that behaves differently from standard CMS pages (e.g. search, dashboard):
-
-1. Create the route under `(cms-routes)` or a separate route group.
-2. Either create a new appShared module (if the pattern is reusable) or implement inline.
-3. Use `getPageWithErrors`, `getArticleWithErrors`, etc. from `@/lib/cms-server`.
-4. Use `projectRendererConfig` from `@/lib/cms-server`.
-5. Render with `CmsContent` using `contents`, `rendererConfig`, and `pageContext`.
-
 ## Custom Layouts
 
-If a route needs a different layout (e.g. no header/footer), create `layout.tsx` in that route directory.
+A different chrome (for example no header) is a `layout.tsx` on a route that already exists. It is not a new URL. A new marketing URL is still a Contentful slug.
 
 ## Troubleshooting
 

package/skills/se-marketing-sites-customer-simplicity/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: se-marketing-sites-customer-simplicity
+description: "Guardrail for customer marketing remakes and ports. Load on Webflow/HTML remake, match-live-site, or parity tasks: CMS to component only, fail closed, no RTF flatten, link inventing, CSS islands, or hardcoded copy."
+---
+
+# Customer site simplicity (remakes / ports)
+
+CMS field in → registered UI out. Do not reconstruct the live site.
+
+Canonical: `docs/PHILOSOPHY.md` §5a. Review: `customer-code-review.md`. Session: `site-workflows-agent-session` (**Do not port Webflow / HTML pages**). Subtract first: `principle-subtract-before-you-add`. How to build a type: `se-marketing-sites-create-component` / `create-collection`.
+
+## Do
+
+- CMS entry → `componentType` / `collectionType` → Registration → Core on core route handlers
+- Empty field → **omit** that UI (or fix CMS). Never invent from the live site
+- Body / `additionalCopy` via `RtfOrString`
+- CMS `links` as-is with `SectionLinks` / `TrackedLink` (or site equivalents)
+- Tailwind + design tokens; `Visual` + `calculateVisualSizes`; `getSizingInformation`
+
+## Do not (BLOCKER)
+
+| Antipattern | Instead |
+|-------------|---------|
+| Stub / heading-match as live renderer | Full layers, or stay unregistered |
+| Catalogue fetch inside a component | Collection `contents` / related fields |
+| Multiplex on `cmsLabel` / heading / `anchor` | One type = one layout (R4.2a) |
+| RTF → plain / paragraph heuristics for layout | `RtfOrString` only |
+| Invent / filter `links` into roles | Render links as given (unless Nick asks) |
+| Hardcoded visitor copy, live URLs, CDN/media fallbacks | Fix CMS / import |
+| Webflow/FlowKit CSS dumps / page CSS islands | Tokens + Tailwind utilities |
+| Second public URL system / custom page for `generatePage` types | One IA; type owns the prefix |
+| Mixed `@se-studio/*` majors | Aligned bump |
+
+## Escape hatches (narrow)
+
+- `globals.css`: shared primitives only (keyframes, RTF element maps, true design-system utilities) — **not** per-page layout ports
+- HtmlComponent + `customCss`: only when the recorded call is **keep** (`create-html-component.md`). A layout a registered type cannot express does not make that call. Do not move a section onto or off HtmlComponent after **keep** or **promote** is recorded. **Not** the default Webflow remake path.
+
+## Related
+
+- `site-workflows-agent-session`, `se-marketing-sites-styling-system`, `coding-discipline`
+- Do not load Cursor Webflow DevLink / FlowKit skills on `@se-studio` customer sites

package/skills/se-marketing-sites-styling-system/SKILL.md

@@ -93,6 +93,16 @@ While configurable, most projects use:
 *   `laptop`: ~1024px+
 *   `desktop`: ~1440px+
 
+Desktop at 1440 is the artboard the grid is built from. It is not a `max-w-[1440px]`. The grid (`container-cols-grid` outside, `content-cols-grid` inside) is what changes at other widths.
+
+### Sections
+
+A marketing block is `<Section>` from `@/framework/Section`. That sets `container-cols-grid` and `section-spacing`. Do not replace it with `mx-auto max-w-[…] px-… py-16`.
+
+Width inside the section is a column span, `max-w-cols-N`, or `max-w-cols-gap-N` (spacing tokens from `--spacing-cols-*`). Type is a `fontTable` class (`h1`, `p1`) or `sizingInformation.h1` from `getSizingInformation`. Do not write `text-[32px]`, `leading-[1.2]`, or `tracking-[…]`.
+
+If Figma has no text style on a node, stop and name that node. Do not guess a class. If the only width in the file is the frame, use the grid.
+
 ### Layout Helpers
 
 Common layout patterns using Tailwind grid utilities:
@@ -124,9 +134,13 @@ Wrap the `RtfOrString` component with the appropriate class:
 
 ## Global Styles
 
-Project-specific global styles, animations, and custom utility classes are located in `src/app/globals.css`. This file imports the generated Tailwind CSS and defines:
+Project-specific global styles live in `src/app/globals.css`. Prefer **Tailwind utilities and design tokens in TSX** for layout. Treat new layout selectors in `globals.css` or extra `*.css` files as **review debt** unless they are shared design-system primitives.
+
+`globals.css` is appropriate for:
 
 *   Root variables (if any)
-*   Animation keyframes
-*   Custom component classes (e.g., `.btn-primary`)
-*   Rich Text Formatting classes
+*   Animation keyframes / `--animate-*` tokens
+*   Rich Text Formatting element maps (`.rtf-*`)
+*   True shared design-system utilities (rare; prefer tokens)
+
+Do **not** grow per-page Webflow ports or CSS islands for layout (see `se-marketing-sites-customer-simplicity`). HtmlComponent `customCss` is a last-resort escape hatch for one-offs, not the default remake path.

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

@@ -231,9 +231,26 @@ When editing Contentful in parallel on the same space, use distinct cms-edit ses
 - **Do not** edit `se-core-product` unless placement is `core` and user approves mode switch
 - Consume `@se-studio/*` from npm — not monorepo workspace links
 
+### Do not port Webflow / HTML pages
+
+Rebuild remakes as **CMS components and collections** on core handlers (`generatePage`, registrations, `RtfOrString`, Tailwind tokens). Never “match this Webflow section in one file,” dump FlowKit/`fk-*` CSS, multiplex on `cmsLabel`/heading, flatten RTF for layout, invent link roles, or hardcode live copy/URLs. **Fail closed** when CMS is empty — omit UI or fix CMS; do not invent from the live site.
+
+Load skill **`se-marketing-sites-customer-simplicity`** on any Webflow/HTML remake, “match the live site,” or parity task. Also: `principle-subtract-before-you-add`. Canonical rules: `docs/PHILOSOPHY.md` §5a; review BLOCKERs in [`customer-code-review.md`](../../references/agent-session/customer-code-review.md).
+
+Do **not** use Cursor Webflow DevLink / FlowKit skills on `@se-studio` customer sites (wrong stack: CSS modules / `_webflow-style.css`).
+
 ### Figma direction (new designs) + phased visual gates
 
-**Until the user explicitly says otherwise**, when implementing UI from a Figma file or node, treat Figma as the **direction / source of truth** for structure, spacing, type, colour, radii, alignment, and control patterns. Do not “improve” or normalize away from the comps to match older site patterns. Prefer Figma MCP design context over CMS drafts or live-site memory.
+**Until the user explicitly says otherwise**, when implementing UI from a **new** Figma file or node, treat Figma as the **direction / source of truth** for structure, spacing, type, colour, radii, alignment, and control patterns. Do not “improve” or normalize away from the comps to match older site patterns. Prefer Figma MCP design context over CMS drafts or live-site memory.
+
+Two things in that file are not decisions. Raise them in the plan and do not write the code until there is a concrete answer:
+
+- The frame width (1440, 1920, whatever the artboard is) is one canvas size. The grid is how that frame adapts at other widths. It is not `max-w-[1440px]`. If the comp really seems to need a hard cap at the frame width, say so and wait.
+- Type with no text style (`leading-[1.2]`, raw `text-[32px]`) means the designer did not specify the font. Name the node. Do not copy the leading and do not guess a `fontTable` class (`h1`, `p1`, `sizingInformation.*`).
+
+Implement what Figma did specify with `<Section>`, `content-cols-grid`, column spans or `max-w-cols-N` / `max-w-cols-gap-N`, and a font-table class. Do not paste arbitrary classes from Figma MCP.
+
+**Remakes from live Webflow/HTML are different:** Figma SoT does **not** apply. Use CMS structure + design tokens; do not chase pixel CSS dumps from the old site. See **Do not port Webflow / HTML pages** above.
 
 **Do not** chase pixel-perfect polish before the **early visual gate**. Iterate with Nick on a Vercel preview first.
 
@@ -259,7 +276,7 @@ Flag layout blowouts, overflow, sparse/stretched heroes, broken grids, and type
 
 Non-UI changes skip visual phases and go to code review.
 
-**Related skills:** `site-workflows-figma-design-snapshot` / `site-workflows-apply-design-snapshot`; Figma MCP `get_design_context`.
+**Related skills:** `se-marketing-sites-customer-simplicity` (remakes / ports); `principle-subtract-before-you-add`; `site-workflows-figma-design-snapshot` / `site-workflows-apply-design-snapshot`; Figma MCP `get_design_context`.
 
 ### Cross-project handoffs
 

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

@@ -247,13 +247,15 @@ Use `getSizingInformation(index)` from `@/lib/SizingInformation` for dynamic sem
 | laptop    | 1024px    | 12      |
 | desktop   | 1440px    | 12      |
 
-Gap: 16px at all breakpoints. Margin: 16px at all breakpoints.
+1440 is the desktop artboard. It is not `max-w-[1440px]`. The grid is what adapts at other widths.
 
-Use `content-cols-grid` for standard content layout.
+Gap and margin come from `tailwind.config.json`.
+
+A marketing block is `<Section>` (`container-cols-grid` + `section-spacing`) with an inner `content-cols-grid`. Width is `col-span-*`, `max-w-cols-N`, or `max-w-cols-gap-N`. Type is a `fontTable` class. Do not use `py-16` as section padding, or `leading-[…]` / `text-[32px]` when the file has no text style — stop and ask which style.
 
 ## Section Spacing
 
-Standard vertical padding: `py-16 laptop:py-24`
+Vertical rhythm is `section-spacing` on `<Section>`, not a hand-written `py-*`.
 
 ## RTF Classes