@easysociable/cli 0.1.0

package/skills/easysociable-content/workflows/DEVICE_TASKS.md

@@ -0,0 +1,5 @@
+# Deferred in V1
+
+Device automation, iPhone publishing, Desktop tasks and Local API workflows are
+not part of the V1 Content Skill. Do not invoke or document them as fallback
+paths. Keep this file as a migration marker only.

package/skills/easysociable-content/workflows/EXPERIMENTS.md

@@ -0,0 +1,6 @@
+# Deferred in V1
+
+Experiments, hypotheses, metrics and proposal activation are retained only as
+historical documentation. The V1 Content Skill does not expose these commands
+or a backend. Write any future notes as ordinary Markdown in the Obsidian
+Vault; do not create hosted experiment records.

package/skills/easysociable-content/workflows/MCP_FIRST.md

@@ -0,0 +1,10 @@
+# Obsidian-first workflow
+
+There is no Content MCP fallback in V1. Use local filesystem tools to set up or
+validate the existing Obsidian Vault, write the Run and platform Pack under
+`Content Engine/runs/<slug>/` or `内容引擎/成稿/<slug>/`, then use the unified EasySociable MCP for hosted
+Template/Slideshow operations. If the MCP is unavailable, use equivalent
+`easysociable` CLI commands.
+
+Never start a Local API, open SQLite or switch to the retired
+`easysociable-content` binary.

package/skills/easysociable-content/workflows/PUBLICATION.md

@@ -0,0 +1,5 @@
+# Deferred in V1
+
+V1 does not provide publication, social posting, metrics, retrospectives or
+UGC/SEO projections. Keep the generated Pack and final PNG export in the local
+Obsidian Run; do not call a retired `easysociable-content` command.

package/skills/easysociable-content/workflows/TOPIC_DRAFT.md

@@ -0,0 +1,5 @@
+# Topic and draft notes
+
+Never invent hosted IDs. V1 has no publication endpoint; call a draft complete
+only when the local Run and platform Pack have been written to the Obsidian
+Vault.

package/skills/easysociable-content/workflows/WORKING_DRAFT.md

@@ -0,0 +1,10 @@
+# Local working draft
+
+V1 has no Working Draft CLI or Content MCP. Store the working draft as
+Markdown/JSON inside the locale run folder (`Content Engine/runs/<slug>/` or
+`内容引擎/成稿/<slug>/`), then
+write the platform Pack before handing off to the Template or Slideshow Skill.
+
+Never treat a local draft as a final render. The final checkpoint is the PNG
+and `manifest.json` written by the unified `easysociable` CLI after the user
+confirms the Studio preview.

package/skills/easysociable-slideshow/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: easysociable-slideshow
+description: >
+  Create and review temporary multi-page Slideshow Runs for EasySociable from a
+  local Obsidian Content Pack. Use the unified `easysociable` CLI or MCP, open
+  Studio for preview, and perform final PNG rendering only after confirmation.
+  There is no Slideshow Template product, UGC publishing, social posting or
+  separate Slideshow CLI/MCP in V1.
+---
+
+# EasySociable Slideshow Skill
+
+A Slideshow Run is a temporary composition of explicit single-page Templates.
+It is not a reusable Carousel/Deck Template and it is not a public post.
+
+## Rules
+
+1. Read a local `content-pack.v1` from the Obsidian Content Engine.
+2. Use the unified `easysociable` CLI or the unified MCP server. All hosted
+   calls go through Gateway; never call Directus, R2, Stripe or private services.
+3. The Agent must choose a Profile, one Theme and an explicit Page Template for
+   every page. The server never silently chooses or replaces a Page Template.
+4. A Run has 1–20 pages, one supported platform (`tiktok`, `instagram`,
+   `linkedin` or `threads`) and one Profile/Theme across all pages.
+5. Topology is fixed after creation: no add, copy, delete, reorder or template
+   switch. Page-instance slot/layout/type/style/decoration edits remain allowed
+   in Studio.
+6. Studio is preview-only. It has no final download, publish, unpublish, UGC,
+   SEO/GEO or social-posting action.
+7. Agent revisions update the same unexpired Run. Studio activity extends the
+   seven-day TTL. Expired Runs are not recoverable through the public API.
+8. Preview is free but rate/concurrency limited. Final rendering is PNG-only,
+   uses one atomic reservation for all pages and charges only when every page
+   succeeds.
+
+## Workflow
+
+1. Validate the Pack and platform/page count.
+2. Resolve or create the user's Profile/Theme through the unified CLI/MCP.
+3. Select a compatible published Page Template for every page.
+4. Call:
+
+   ```bash
+   easysociable slideshows create --file ./pack.json --json
+   ```
+
+5. Open the returned `studioUrl` and inspect every page.
+6. Save Studio edits and wait for the saved revision.
+7. After explicit confirmation, call:
+
+   ```bash
+   easysociable slideshows render --id run_xxx --idempotency-key run_xxx-final-1 --json
+   easysociable slideshows export --id run_xxx --output ./exports/run_xxx/tiktok --json
+   ```
+
+   Hosted finals use one Run capture session + one Imagine deck screenshot
+   (single browser load, N page PNGs). Require Studio Save (`layout.studioJson`
+   + `themeSnapshot`) before render. Single-page Template jobs still use
+   `renders create|wait|export`.
+
+8. Verify checksums and the reconstruction `manifest.json` in the Obsidian
+   Run export. The export is the local final deliverable; cloud artifacts expire
+   after 24 hours.
+
+## Failure handling
+
+- If a page template, slot or image is invalid, return the structured Gateway
+  error to the Agent; do not substitute another template.
+- If any final page fails, there is no partial final set and no page charge.
+- Retry the same final request with the same idempotency key to reuse the Job.
+- If the Run is expired, create a new Run from the Pack.
+
+## Handoff boundary
+
+The Content Skill owns semantic copy and Pack creation. The Template Skill owns
+single-page authoring and fill-slots. This Skill only composes explicit page
+instances and coordinates preview/final render.

package/skills/easysociable-slideshow/references/CONTENT_PACK.md

@@ -0,0 +1,25 @@
+# ContentPack v1
+
+```json
+{
+  "schemaVersion": "content-pack.v1",
+  "platform": "tiktok",
+  "title": "A repeatable story",
+  "pages": [
+    { "role": "hook", "pageTemplateId": "tpl_hook_001", "slots": { "text_0": "The hook", "text_1": "The point" } },
+    { "role": "value", "pageTemplateId": "tpl_value_001", "slots": { "text_0": "One idea" } },
+    { "role": "cta", "pageTemplateId": "tpl_cta_001", "slots": { "text_0": "Follow for more" } }
+  ]
+}
+```
+
+Page `role` is semantic and `pageTemplateId` is the explicit published
+single-page template chosen by the Agent. `slots` are public values only. Do not
+add a `deck_template_id`, `bindingMap`, AST or ContentDocument.
+
+The Gateway validates that each selected template supports the page role and
+belongs to the account-visible catalog. It never silently replaces a selection.
+
+The renderer accepts any supported page count within the platform cap. A newly
+published Page Template can be selected in a new Run without creating a
+carousel asset.

package/skills/easysociable-slideshow/references/GATEWAY.md

@@ -0,0 +1,16 @@
+# Slideshow Gateway reference
+
+Slideshow uses the unified EasySociable Gateway client and public routes:
+
+```text
+POST /v1/slideshow/runs
+GET  /v1/slideshow/runs/{runId}
+PATCH /v1/slideshow/runs/{runId}
+POST /v1/slideshow/runs/{runId}/render
+GET  /v1/slideshow/runs/{runId}/studio
+GET  /v1/render-jobs/{jobId}
+GET  /v1/render-jobs/{jobId}/manifest
+```
+
+There are no V1 publish, unpublish, public-piece or Slideshow-template routes.
+All requests use the account's unified credential and owner isolation.

package/skills/easysociable-slideshow/references/PLATFORM_CAPS.md

@@ -0,0 +1,17 @@
+# Platform page caps (ADR-0026)
+
+The Run validates only the actual `content-pack.v1.pages.length`. There is no
+`designMax`, full-page deck skeleton, or deck catalog to clone.
+
+| platform | hardMin | hardMax | default canvas |
+|---|---:|---:|---|
+| tiktok | 4 | 35 | 9:16 · 1080×1920 |
+| instagram | 2 | 20 | 4:5 · 1080×1350 |
+| linkedin | 2 | 300 | 1:1 · 1080×1080 |
+| x | 2 | 4 | platform-specific X organic image size |
+| xiaohongshu | 2 | 18 | platform-specific vertical image size |
+| threads | 2 | 20 | platform-specific image size |
+
+If a pack is outside the cap, stop before creating a Run and ask the agent to
+revise the page count or split the piece. Never silently drop a CTA or pad a
+pack to a product skeleton.

package/skills/easysociable-slideshow/references/VAULT.md

@@ -0,0 +1,18 @@
+# Obsidian export
+
+The local Obsidian Run folder is the final delivery mirror:
+
+```text
+Content Engine/            or  内容引擎/
+└── runs/<slug>/           or  成稿/<slug>/
+    └── exports/<slug>/<platform>/   or  导出/<slug>/<platform>/
+        ├── 01.png
+        ├── 02.png
+        └── manifest.json
+```
+
+Read `locale.json` in the engine root (`en` or `zh`) and use that tree. Pack JSON keys stay English.
+
+The CLI verifies checksums and atomically replaces this directory only after a
+complete atomic Hosted Render succeeds. No ZIP is created. The cloud artifact
+may expire after 24 hours; the local PNGs remain the user's files.

package/skills/easysociable-slideshow/workflows/CREATE_RUN.md

@@ -0,0 +1,7 @@
+# Create Run
+
+1. Build `content-pack.v1` from the agent's semantic outline.
+2. Check platform hardMin/hardMax.
+3. Call `create_run` or `run create` through Gateway.
+4. Save `runId`, `studioUrl`, and `status=draft`.
+5. Do not call a Deck API or create a carousel template.

package/skills/easysociable-slideshow/workflows/MCP_FIRST.md

@@ -0,0 +1,14 @@
+# MCP-first
+
+Use the single unified EasySociable MCP server for Slideshow Run operations.
+Fallback commands use the same Gateway client:
+
+```bash
+easysociable slideshows create --file ./pack.json --json
+easysociable slideshows render --id run_xxx --idempotency-key run_xxx-final-1 --json
+easysociable renders wait --id job_xxx --json
+easysociable renders export --id job_xxx --output ./exports/run_xxx/tiktok --json
+```
+
+Neither path may call a private service, Local API, Directus, R2 or a separate
+Slideshow MCP process.

package/skills/easysociable-slideshow/workflows/OUT_OF_SCOPE.md

@@ -0,0 +1,8 @@
+# Out of scope
+
+- DeckTemplate creation, `list_decks`, `CREATE_DECK`, or `BIND_P0_DECKS`.
+- ContentDocument as a render input (ADR-0021).
+- Client-side RenderPlan or AST compilation.
+- Full cross-platform Page Template coverage and ad-placement variants.
+- Copy generation, account memory, or publication analytics.
+- UGC/publication, public slugs, SEO/GEO and social posting.

package/skills/easysociable-slideshow/workflows/PUBLISH_RUN.md

@@ -0,0 +1,4 @@
+# Deferred in V1
+
+Slideshow Runs are not published as UGC and have no publish/unpublish action in
+V1. The final deliverable is a locally exported PNG set and `manifest.json`.

package/skills/easysociable-slideshow/workflows/RENDER_RUN.md

@@ -0,0 +1,6 @@
+# Render Run
+
+Call `render_slideshow_run` / `slideshows render`. The Agent has already chosen a published Page Template
+for each page role, fills public slot values, and delegates to Hosted Template
+Render. A missing role match is a structured error; the agent must not silently
+replace a page template locally.

package/skills/easysociable-template/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: easysociable-template
+description: >
+  Create single-page social image templates for EasySociable via the unified
+  Template MCP or `easysociable` CLI, and fill published template slots to Hosted Render
+  (get_template → slots → create_render_job). Use when the user wants to author a
+  page template from a reference image or text brief, write a shared visual design
+  philosophy, explore 2–3 professional layout concepts as spatial expressions of that
+  philosophy, plan or generate visual assets, co-create/reuse a Theme with brand-hex
+  palette generation, choose a Surface (flat / Gateway gradient catalog / host
+  Unsplash·Pexels·Pinterest photo), pull icons via Template Gateway
+  search_icons/get_icon (internal Icon Catalog), run
+  screenshot-based visual QA, attach catalog metadata (platforms including
+  x/linkedin/threads, pageRoles, archetypes, density, slotSummary), open Authoring
+  Studio, publish a single-page template, or render a published template by filling
+  public slots. Do not use for multi-slide slideshow composition, ContentDocument as
+  render input, local content library, or carousel packs.
+---
+
+# EasySociable Template Skill
+
+The public entry points are the unified `easysociable` CLI and one unified MCP
+server. Do not install or invoke `easysociable-template`, `easysociable-slideshow`,
+`easysociable-content`, or a separate Content/Slideshow MCP in V1.
+
+**This skill owns two single-page paths:**
+
+1. **Author** templates (Studio + Publish).
+2. **Fill slots → Hosted Render** for a published PageTemplate (`workflows/FILL_AND_RENDER.md`).
+
+It is a template factory **and** the Agent surface for single-page fill-slots out图 (ADR-0021). It is **not** a multi-slide slideshow compositor.
+
+Every published page must carry **P0 catalog metadata** so Agents can filter and fill templates (`references/CATALOG_METADATA.md`).
+
+Out of scope (hand off):
+
+- Generating爆款 copy / Working Draft as a **Content** product (Content Skill)
+- Multi-slide slideshow composition / Slideshow Run → **easysociable-slideshow**
+- Local Runtime, SQLite, Content Version library
+- Using `ContentDocument` / `contentDocumentHash` as Template render input
+
+## Rules
+
+1. Prefer the unified EasySociable MCP. Fall back only to the unified `easysociable` CLI.
+2. Submit only public Gateway DTOs. Never invent or request private Safe AST / Binding Map / RenderPlan.
+3. Do not start Local Runtime, read content library SQLite, or call Content MCP/CLI for Template work.
+4. Catalog and create targets are **single-page** only. Never treat site Carousel packs as Agent templates.
+5. After `create` / `createDraft`, the primary authoring path is `authoringStudioUrl` (`/authoring/{draftId}`). Always send the handoff message in `AUTHORING_STUDIO.md` (edit → **Save** → tell Agent to publish). Do not require a Hosted Preview Job for interactive authoring.
+6. Studio has **Save only** — no Publish button. Publish only after the user saves and **explicitly** asks to publish; then run `workflows/PUBLISH_FROM_DRAFT.md`.
+7. **Do not Publish without complete P0 selection metadata** (`CATALOG_METADATA.md`). Gateway enforces this.
+8. Theme: reuse `themeId` **or** co-create full `ThemeTokens`. Colors/fonts belong in Theme; page nodes use semantic `--es-*` tokens where possible.
+9. Layout model is **absolute positioning** on a **flat canvas tree** (see prior authoring rules / `AUTHORING_SOURCE.md`).
+10. **Runtime layout CSS:** put exact geometry in JSX inline `style={{...}}`. Never depend on Tailwind arbitrary-value classes for geometry.
+11. Run `scripts/validate-authoring-source.mjs` before every create/update.
+12. `supportedRoles` uses closed **pageRoles**; `platforms` is a multi-select array.
+13. Canvas sizes must follow `references/PLATFORM_SPECS.md`.
+14. **Text-only V2.1 authoring:** `DESIGN_BRIEF` → Philosophy → Concepts → assets/surface → author → Visual QA.
+15. **Visual QA** before Studio handoff when authoring.
+16. Prefer **reusable/brand assets**, Gateway gradient recipes, and catalog icons for deterministic visuals. Geometric chrome (hairlines, rails, discs) may use plain CSS shapes — **not** as a substitute for named icons.
+17. Preserve `draftId`, `templateId`, `themeId`, `jobId`, `authoringStudioUrl`, and `previewUrl` across steps.
+18. **Theme / Surface confirmation gates** unchanged for authoring (see `PALETTE_REVIEW`, `SURFACE_REVIEW`).
+19. **Fill-slots render (primary consumption path):** `get_template` → fill `slots[]` → `create_render_job({ templateId, slots, output })` → poll Job/Manifest. Image slots always use an account-owned `imageId` from the existing Gateway → R2 + Directus `Image` flow. Never pass a third-party URL, local path, transient `renderAssetId`, ContentDocument or `contentDocumentHash`. See `workflows/FILL_AND_RENDER.md`.
+20. **Hosted Capture first:** default delivery is Hosted Artifact. Local capture only when the error includes `fallback.capture` — follow `workflows/FILL_AND_RENDER.md` §5 (CLI `capture` or same-URL Playwright). Do not use page html-to-image buttons as the Agent primary path.
+21. **Icons (hard rule — no shortcuts):**
+    - Any **recognizable icon** (arrows, chevrons, checkmarks, social glyphs, UI symbols, “next page” cues, etc.) **MUST** use Gateway Icon Catalog:
+      `search_icons` / CLI `icons search` → show ≤8 candidates → **user confirm** (or explicit “你定 / 用第 N 个”) → `get_icon` / CLI `icons get --idempotency-key …` → embed returned **`canonicalSvg`** and record **`iconAssetId`** / `iconId` on the decoration node.
+    - **Forbidden by default:** hand-authored SVG `<path>` icons, emoji-as-icon, Iconify/Better Icons MCP, inventing icon markup “because it’s faster”.
+    - **Not icons (CSS chrome OK without catalog):** pure geometry with no symbol meaning — e.g. solid rectangle rail, hairline rule, plain circle blob used only as wash.
+    - **Degrade only if** search/get fails or catalog unavailable: say so, then offer omit **or** temporary CSS/SVG shape **after user agrees**. Never silently hand-draw when catalog works.
+    - Color with `currentColor` / `--es-*`; never bake brand hex into the SVG. Full procedure: `workflows/SURFACE_REVIEW.md` § Icons.
+
+## Bootstrap
+
+```bash
+easysociable auth status --json
+```
+
+## Intent routing
+
+| User intent | Workflow |
+|---|---|
+| Text description → template | `DESIGN_BRIEF.md` → … → `AUTHORING_STUDIO.md` |
+| Reference image → template | `AUTHORING_FROM_IMAGE.md` → … → `AUTHORING_STUDIO.md` |
+| Need gradient / photo surface / icons only | `SURFACE_REVIEW.md` |
+| **Add / change an icon** (arrow, chevron, check, …) | **MUST** `SURFACE_REVIEW.md` § Icons — search → confirm → get_icon. **Do not** hand-draw SVG paths. |
+| Already have authoring payload / continue Studio | `workflows/AUTHORING_STUDIO.md` |
+| User says publish / 发布该模板 (after Save) | `workflows/PUBLISH_FROM_DRAFT.md` |
+| Browse published single-page templates | `list` / `get_template` + public metadata |
+| **Fill a published template → PNG/JPEG** | `workflows/FILL_AND_RENDER.md` |
+| 「做一套多页 slideshow / deck / carousel 出图」 | **Stop multi-slide composition** → **easysociable-slideshow**. Per-page fill-slots render still uses this skill’s `FILL_AND_RENDER` when orchestrated by slideshow. |
+
+## Core model
+
+- `references/PLATFORM_SPECS.md`
+- `references/CATALOG_METADATA.md`
+- `references/SLOTS.md` — public slot contract for fill-slots render
+- `references/AUTHORING_SOURCE.md`
+- `references/THEME_TOKENS.md`
+- `references/EXTERNAL_RESOURCES.md`
+- `references/GATEWAY.md` — CLI / MCP including `render` / `create_render_job`
+- `workflows/FILL_AND_RENDER.md` — get_template → slots → Hosted Render
+- Authoring V2.1 workflows + validators as before
+
+## MCP
+
+See `workflows/MCP_FIRST.md`.

package/skills/easysociable-template/references/AUTHORING_SOURCE.md

@@ -0,0 +1,129 @@
+# Authoring source (Agent → Gateway)
+
+The Agent produces a public **single-page** `authoringSource`. The server compiles it into private Safe AST / bindings. Clients never receive Binding Map or private AST.
+
+## Required payload shape
+
+```ts
+type AuthoringSource = {
+  canvas: { width: number, height: number }  // e.g. 1080×1350, 1080×1440
+  json: unknown  // Studio projection (nodes / snapshot-like structure)
+  // optional: data, style, font — only if Gateway/Studio expect them
+}
+```
+
+Provenance on create:
+
+```ts
+source: {
+  kind: 'image_reference' | 'text_brief' | 'manual' | 'import'
+  brief?: string
+}
+```
+
+## What the Agent must decide before `create`
+
+1. **Canvas** — width / height + `canvasPreset` from `PLATFORM_SPECS.md` Recommended row + `CATALOG_METADATA.md`.
+2. **Selection metadata (P0)** — platforms, supportedRoles (pageRoles), contentFamily, contentArchetypes, density, media/slotSummary, shortDescription — see `CATALOG_METADATA.md`. Write `selection-metadata.json` alongside the authoring source.
+3. **Slot table** — see `SLOTS.md` (`text` / `number` / `image` only; no `list`). Derive `slotSummary` (+ `fixedItemCount` for checklist/steps).
+4. **Node layout** — flat absolute positions on the canvas; each fillable node has `bindingKey` = slot key.
+5. **Decoration** — nodes without `bindingKey` (including visual card backgrounds as **siblings**, not parents).
+6. **Theme** — reuse `themeId` or full `ThemeTokens` create (`THEME_TOKENS.md`).
+7. **Placeholders** — sample strings/images for Studio preview only.
+
+## Layout model
+
+- Nodes are **absolutely positioned** (independent frames) under the canvas frame (`data-type="post"` / Graphic).
+- **Flat tree rule:** every layout node is a **direct child of the canvas frame**, with coordinates relative to the **canvas**, not to another box.
+- **Forbidden:** nesting `position: 'absolute'` inside another `position: 'absolute'` (e.g. `profile-card` wrapping avatar + name + handle). Studio select/drag writes canvas coordinates; nested frames cause elements to jump or move as a group unintentionally.
+- **Allowed text nesting:** a text host (`h1`–`h6`, `p`, `span`, or one absolute text unit) may contain **non-positioned** inline children (emphasis marks, split currency + number spans). Those children must **not** set `position: 'absolute'`.
+- **Visual “card” pattern:** draw the card panel as its own absolute **decoration** sibling; place `img` / name / handle as separate absolute siblings using canvas coordinates (convert any local offsets: `canvasLeft = cardLeft + localLeft`).
+- Do not assume flex/flow reflow when a node is omitted.
+- Empty optional slots → omit node at render (see `SLOTS.md`).
+
+Bad — layout group wrapper (absolute inside absolute):
+
+```jsx
+<div
+  style={{ position: 'absolute', right: 56, top: 62, width: 270, height: 214 /* card */ }}
+  data-type="profile-card"
+>
+  <img style={{ position: 'absolute', left: 24, top: 24, width: 76, height: 76 }} /* nested */ />
+  <div style={{ position: 'absolute', left: 24, top: 122 }}>Alex Chen</div>
+</div>
+```
+
+Good — flat siblings (card chrome + content share the canvas):
+
+```jsx
+<div
+  style={{ position: 'absolute', left: 874, top: 62, width: 270, height: 214 /* panel only */ }}
+  data-type="decoration"
+/>
+<img
+  style={{ position: 'absolute', left: 898, top: 86, width: 76, height: 76 }}
+  data-type="image"
+/>
+<div style={{ position: 'absolute', left: 898, top: 184, width: 220 }} data-type="title">
+  Alex Chen
+</div>
+```
+
+## Studio runtime CSS contract
+
+Authoring Studio loads `authoringSource.json` **at runtime**. Tailwind only emits CSS for classes found during the Studio build, so remote arbitrary-value utilities have no guaranteed CSS.
+
+For every value that controls composition, use JSX inline styles:
+
+- Geometry: `position`, `left`, `right`, `top`, `bottom`, `width`, `height`
+- Critical type: `fontSize`, `lineHeight`, `letterSpacing`, `fontWeight`
+- Runtime Theme values: `var(--es-color-*)`, `var(--es-font-*)`, `var(--es-surface-*)`
+
+Bad — class names exist in the DOM but their CSS may not:
+
+```jsx
+<h1 className="absolute left-[56px] top-[120px] w-[720px] text-[42px]">
+  Revenue
+</h1>
+```
+
+Good — deterministic after runtime loading:
+
+```jsx
+<h1
+  style={{
+    position: 'absolute',
+    left: 56,
+    top: 120,
+    width: 720,
+    fontSize: 42,
+    color: 'var(--es-color-text,#F7F9F9)',
+    fontFamily: 'var(--es-font-heading,Inter)',
+  }}
+>
+  Revenue
+</h1>
+```
+
+Use `className` only for non-critical static utilities known to exist in the Studio bundle. Never use Tailwind arbitrary-value tokens (`...-[...]`) for authoring geometry, typography, or Theme colors.
+
+Before create/update, run the bundled validator relative to this Skill directory:
+
+```bash
+node scripts/validate-authoring-source.mjs ./authoring-source.json
+```
+
+Treat any validator error as blocking.
+
+## Forbidden in Agent output
+
+- Private Safe AST as if it were the public contract
+- `bindingMap` / full bindings objects in Gateway requests
+- Multi-page / carousel pack structures
+- Claiming pixel-perfect recreation of a competitor poster without Studio review
+- Critical runtime layout expressed with Tailwind arbitrary-value classes
+
+## Hand-off
+
+After create, open `authoringStudioUrl` and send the handoff message in `AUTHORING_STUDIO.md`.  
+User edits and **Saves** in Studio (no Publish button). Agent publishes only after the user asks — see `PUBLISH_FROM_DRAFT.md`.