@blockbite/agent-context 0.1.0

package/skills/figma-design-to-code/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: figma-design-to-code
+description: Implement one reusable BlockBite dynamic-template island from an exact Figma file key and node id with strong design matching, package contracts, seed data, registration, and blueprint wiring. Use for section-level Figma-to-BlockBite work inside a planned site build or when converting a single Figma section into a reusable BlockBite template.
+---
+
+# Figma Design To Code
+
+Use this skill to implement one reusable dynamic-template island at a time from Figma.
+
+Start from an exact Figma file key and node id. If the request is for a full site or multiple pages, use `figma-site-builder` first to create the inventory and blueprint map.
+
+## Before Coding
+
+1. Discover and record the active `<prefix>` for WP-CLI commands. Do not hardcode `ddev`.
+2. Read `dev/skills/template-figma/SKILL.md`.
+3. Read `dev/skills/document-blueprint/SKILL.md` when wiring a page section or seed file.
+4. Read `dev/skills/block-style/SKILL.md` when buttons, arrows, or repeated block variants are involved.
+5. Read `dev/skills/references/block-dsl.md` before authoring DSL tags.
+6. Read `dev/skills/references/tailwind-utilities.md` before custom CSS for grid placement, direct-child styling, container behavior, editor-only tweaks, or text masks.
+7. Read `<workspace>/dev/plans/<site>/island-inventory.md` and `<workspace>/dev/plans/<site>/page-blueprint-map.md` when they exist.
+
+## Figma Verification
+
+Verify access before editing files:
+
+- Load metadata/context for the exact node.
+- Capture or inspect a screenshot.
+- Record dimensions, breakpoints or responsive hints, spacing, typography, color, image ratios, overflow, repeated groups, hover states, and visible interaction states.
+- If Figma is inaccessible, document the fallback and ask for the missing artifact before guessing design details.
+
+## Reuse Check
+
+Before creating a new slug, compare the node to the existing island inventory and templates:
+
+- Reuse an existing template when layout, fields, and behavior can share one design contract.
+- Add a page-specific section seed file when only the content differs.
+- Create a new template only when the visual structure, behavior, or data contract genuinely differs.
+
+Do not create page-specific duplicates such as `home-project-slider`, `services-project-slider`, and `profile-project-slider` when one `project-slider` template with different seeds fits.
+
+## Implementation Contract
+
+Implement or refine:
+
+```text
+<workspace>/templates/<slug>/
+  template.liquid
+  recipe.json
+  seeds.json
+  fields.yaml
+  manifest.json
+  style.css
+  module.ts
+```
+
+Use a dynamic template for every island. Choose the source type deliberately:
+
+- Use `block_instance` for content owned by each page section instance.
+- Use `post_type` when the template reads fields from the current post source.
+- Use `collection` only for genuinely collection-backed content.
+
+Preserve design facts:
+
+- section order and section role
+- exact content hierarchy
+- desktop and mobile layout behavior
+- image ratios and focal behavior
+- overflow and clipped/masked content
+- card heights and mixed-height carousel/card patterns
+- hover/focus states visible in Figma
+- typography, color, radius, and spacing mapped to tokens where possible
+
+Use media fields for editor-selected images and SVG fields for editable icons/decorative SVGs. Do not model editable media as string URLs unless users must manually type external URLs.
+
+## Authoring Rules
+
+- Use Tailwind classes in `template.liquid`.
+- Use `style.css` only for masks, keyframes, pseudo-elements, or layout details Tailwind cannot express cleanly.
+- Do not put island styling or global `html`, `body`, `button`, `input`, typography, background, or reset rules in `app/styles-shared/*.css`; that directory is bundled into `app.bundle.css` and loaded in editor previews. Use `templates/<slug>/style.css` for island CSS and `app/styles-app/app.css` or the theme for frontend-only globals.
+- Use Alpine for nav, FAQ, tabs, filters, and simple state.
+- Use `module.ts` only for ESM libraries, Swiper, GSAP, ScrollTrigger, SplitText, or behavior Alpine cannot handle cleanly.
+- Use shared block styles for repeated button/control variants instead of copying long Tailwind strings.
+- Keep field handles identical across `fields.yaml`, `recipe.json`, `seeds.json`, Liquid access paths, and blueprint seed files.
+
+## CLI Flow
+
+Use the discovered command prefix:
+
+```bash
+<prefix> bb template patterns --type=<type>
+<prefix> bb template scaffold --slug=<slug> --type=<type> --variant=<variant>
+<prefix> bb dynamic-template package --slug=<slug> --overwrite
+<prefix> bb doctor
+<prefix> bb dynamic-template create --slug=<slug>
+<prefix> bb dynamic-content create --slug=<slug> --source-type=<type> --fields=<slug>/fields.yaml
+<prefix> bb source import-seeds --slug=<slug> --file=<absolute seeds path>
+```
+
+If rows already exist, use `dynamic-template update` and `dynamic-content sync`.
+
+When the island is used in a page blueprint, create or update:
+
+```text
+<workspace>/document-blueprints/<page>/sections/<section-key>.seed.json
+```
+
+Then validate:
+
+```bash
+<prefix> bb validate
+<prefix> bb document-blueprint validate --slug=<page>
+```
+
+Build according to the reported build mode before visual review.
+
+## Finish
+
+Update the inventory row status and report:
+
+- template slug and source type
+- Figma node id
+- files changed
+- section seed files changed
+- commands run
+- design details intentionally approximated or blocked
+- next static review target

package/skills/figma-site-builder/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: figma-site-builder
+description: Plan and orchestrate full BlockBite sites from Figma using reusable dynamic-template islands, document blueprints, design tokens, and workspace skill handoffs. Use when the user provides a Figma site or multi-page design and wants a site build plan, island inventory, page blueprint map, token setup, header/footer strategy, or coordinated Figma-to-BlockBite implementation workflow.
+---
+
+# Figma Site Builder
+
+Use this skill as the planning and orchestration layer for full-site builds from Figma.
+
+Do not start coding individual islands until the site plan, reusable island inventory, and page blueprint map are understood. For individual section implementation, use `create-template-draft` for new sections and `update-template-draft` for existing sections. For preview-only review, use `render-preview`.
+
+## Ground Rules
+
+- Prefer MCP tools when a BlockBite MCP server is connected. Use local WP-CLI only when working directly inside a WordPress project without MCP.
+- In MCP mode, call `blockbite-agent-onboarding` before any implementation planning or sandbox writes. In local CLI mode, discover the active WordPress command prefix and use the discovered `<prefix>` in all commands; do not hardcode `ddev`.
+- In MCP-only assignments, do not read local filesystem paths, plugin internals, neighboring repos, WP-CLI output, or direct database state. Remote workspace reads through BlockBite MCP tools are allowed and are the intended authoring contract.
+- Use workspace docs, workspace skills, MCP onboarding output, local `<prefix> bb learn` output, CLI help, and user-provided docs. Do not inspect BlockBite plugin internals while using this skill.
+- Avoid direct database queries unless no CLI or documentation path exposes the needed state.
+- Prefer dynamic templates for every island so fields, subcollections, assets, and package data stay explicit.
+- Reuse dynamic templates when designs overlap. Vary page content through document-blueprint section seed files instead of creating page-specific duplicate templates.
+- Header and footer are dynamic templates. Plan `site-header` as the theme header pattern and `site-footer` as the theme footer pattern.
+- Use UI DSL tags so package data and dynamic-content contracts can be generated and synced cleanly.
+- Use Tailwind in `template.liquid`; use `style.css` only for masks, keyframes, pseudo-elements, or layout details Tailwind cannot express cleanly.
+- Do not plan or place page/global styling in `app/styles-shared/*.css` unless it is intentionally shared and selector-scoped. That folder is bundled into `app.bundle.css` and loaded in editor previews; frontend-only globals belong in `app/styles-app/app.css` or the theme, and island CSS belongs in `templates/<slug>/style.css`.
+- Use Alpine for simple state. Use `module.ts` only for ESM libraries, Swiper, GSAP, ScrollTrigger, SplitText, or behavior Alpine cannot handle cleanly.
+- Use BlockBite SVG fields/assets for icons and decorative SVGs.
+- Use BlockBite block styles for shared button variants.
+
+## Required Orientation
+
+1. Run or read the current orientation output:
+
+   MCP mode:
+
+   ```json
+   blockbite-agent-onboarding { "format": "codex", "topic": "site-builder" }
+   ```
+
+   Local CLI mode:
+
+   ```bash
+   <prefix> bb learn --format=codex
+   ```
+
+2. In MCP mode, inspect the onboarding `readiness` and `readBeforeEditing` payload:
+   - Read required files with `blockbite-workspace-read`, not local filesystem tools.
+   - Stop before planning implementation details if `readiness.requiredAuthoringDocsAvailable` is false.
+   - Report missing required authoring docs instead of guessing BlockBite behavior.
+
+3. Read relevant workspace context before acting:
+   - `dev/skills/index.json` for the installed workflow index.
+   - `dev/skills/mcp-tools.json` for MCP tools and local fallbacks.
+   - `dev/skills/create-template-draft/SKILL.md` for new section packages.
+   - `dev/skills/update-template-draft/SKILL.md` for existing section packages.
+   - `dev/skills/render-preview/SKILL.md` for seed-backed review previews.
+   - `dev/skills/references/block-dsl.md` and `dev/skills/references/tailwind-utilities.md` when authoring or reviewing DSL/Tailwind.
+
+4. If Figma access is needed, verify the file key, node ids, metadata/context access, and screenshots before planning implementation details.
+
+5. Before creating or editing templates, report orientation evidence:
+   - working mode: MCP-only or local CLI
+   - selected BlockBite project and onboarding readiness
+   - required remote docs read or missing
+   - Figma file key, node ids, metadata/design context, and screenshots inspected
+   - reusable dynamic-template island inventory
+   - document-blueprint section order and seed files
+   - design-token map
+   - preview/build plan
+
+## Planning Files
+
+Create planning output under:
+
+```text
+<workspace>/dev/plans/<site>/
+  site-plan.md
+  island-inventory.md
+  page-blueprint-map.md
+  token-map.md
+```
+
+`site-plan.md` must include:
+
+- working mode: MCP or local CLI
+- MCP onboarding tool result or discovered local command prefix
+- Figma file keys and relevant node ids
+- build mode and build command/tool
+- library/CDN setup requirements
+- token setup status
+- header/footer registration plan
+- known blockers or inaccessible Figma nodes
+
+`island-inventory.md` must list unique reusable dynamic templates, not every page occurrence. Each row must include:
+
+- reusable template slug
+- Figma node ids that map to this design
+- pages using it
+- behavior, such as static, Alpine accordion, logo marquee, GSAP reveal, or Swiper slider
+- source type, usually `block_instance`; use `post_type` or `collection` only when content is genuinely data-backed
+- fields and subcollections
+- required media/SVG assets
+- status: `planned`, `scaffolded`, `preview-built`, `reviewed`, `registered`, or `wired`
+
+`page-blueprint-map.md` must lock each page section order before implementation. Map every section key to a reusable template slug and a seed file. Example order:
+
+```text
+site-header
+banner
+logo-slider
+quote
+usp-cards
+project-slider
+commitment
+featured-blogs
+shared-cta
+faq
+site-footer
+```
+
+`token-map.md` must map accessible Figma colors, type, radius, and spacing decisions to Tailwind v4 `@theme` variables in `<workspace>/dev/css/design-tokens.css`. Agents may add any valid `@theme` variables needed by the design; do not use `dev/design-tokens.yaml` or force tokens into the old normalized schema.
+
+## Blueprint-First Page Composition
+
+Use document blueprints for page assembly:
+
+```text
+<workspace>/document-blueprints/<page>/blueprint.json
+<workspace>/document-blueprints/<page>/sections/<section-key>.seed.json
+```
+
+Use page-specific seed files for reused templates. For example, `home/project-slider.seed.json` and `services/project-slider.seed.json` can target the same `project-slider` template with different content.
+
+Preview with `bb_document_blueprint`; do not create manually duplicated aggregate stacks for blueprint pages. Import only after approval, because document-blueprint import overwrites managed page content.
+
+## MCP And CLI Flow
+
+In MCP mode, use BlockBite MCP tools for workspace reads, sandbox writes, previews, validation, and builds:
+
+```text
+blockbite-workspace-status
+blockbite-build-status
+blockbite-workspace-list
+blockbite-workspace-read
+blockbite-workspace-search
+blockbite-template-scaffold
+blockbite-template-create-draft
+blockbite-workspace-write
+blockbite-workspace-patch
+blockbite-template-render-preview
+blockbite-validate-workspace
+blockbite-sandbox-status
+blockbite-build-run
+```
+
+MCP writes must stay in the sandbox until the user approves them in WordPress. MCP agents do not run Node.js, import BlockBite build chunks, or call local WP-CLI build commands.
+
+In local CLI mode, use the discovered command prefix:
+
+```bash
+<prefix> bb template patterns --type=<type>
+<prefix> bb template scaffold --slug=<slug> --type=<type> --variant=<variant>
+<prefix> bb dynamic-template package --slug=<slug> --overwrite
+<prefix> bb document-blueprint generate --file=<spec> --overwrite
+<prefix> bb document-blueprint validate --slug=<page>
+<prefix> bb dynamic-template create --slug=<slug>
+<prefix> bb dynamic-template update --slug=<slug>
+<prefix> bb dynamic-content create --slug=<slug> --source-type=<type> --fields=<slug>/fields.yaml
+<prefix> bb dynamic-content sync --slug=<slug> --source-type=<type> --fields=<slug>/fields.yaml
+<prefix> bb source import-seeds --slug=<slug> --file=<absolute seeds path>
+```
+
+For design tokens:
+
+```bash
+<prefix> bb design-tokens db-to-local
+<prefix> bb design-tokens local-to-db
+```
+
+For validation and builds:
+
+```bash
+<prefix> bb doctor
+<prefix> bb validate
+<prefix> bb autobuild
+```
+
+## Shared Styles And Libraries
+
+Plan shared `bb/button` block styles for:
+
+- `primary`
+- `secondary`
+- `text-link`
+- `slider-arrow`
+
+Use the workspace block offload/build flow before relying on these variants.
+
+Register Alpine, GSAP, ScrollTrigger, SplitText, Swiper, and Alpine collapse only when the site actually needs them. Register Alpine collapse when FAQ or other panels use `x-collapse`.
+
+## Handoff
+
+When planning is complete, give the next agent or pass:
+
+- the planning folder path
+- the Figma file key and node id for the next island
+- the chosen reusable template slug
+- source type, fields, subcollections, assets, and expected behavior
+- the page blueprint section keys and seed files that will use the island
+- the static acceptance criteria before motion work starts

package/skills/frame-draft-link/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: frame-draft-link
+description: Draft directly into a copied BlockBite frame draft link. Use when the user pastes a blockbite://frame-draft link from the BlockBite editor toolbar.
+---
+
+# Draft into a BlockBite frame link
+
+Use this workflow when the user gives a `blockbite://frame-draft?...` link from
+the BlockBite editor. This is not a dynamic-template package workflow. The goal
+is to let the editor poll, compile, and offer an explicit **Apply draft** action
+without saving the WordPress post.
+
+## Link contract
+
+Parse the query string from the link:
+
+- `id` - draft session id.
+- `draft` - relative workspace path for the Liquid file, normally
+  `drafts/<id>/draft.liquid`.
+- `manifest` - relative workspace path for the manifest, normally
+  `drafts/<id>/manifest.json`.
+- `site` - originating WordPress site URL.
+- `token` - editor session token. Preserve it in the manifest if useful, but do
+  not print it back unless the user asks.
+
+If `draft` or `manifest` is missing, derive them from `id` using the normal
+`drafts/<id>/...` paths.
+
+## Steps
+
+1. Ensure the BlockBite MCP project is selected and the workspace tools are
+   available. Use the connection-status or project-select skills if needed.
+2. Create the draft folder through `blockbite-workspace-write` by writing a
+   small JSON manifest to `manifest`.
+3. Write only BlockBite UI-DSL Liquid to `draft`.
+4. Tell the user the editor toolbar should move through waiting/writing/compiled
+   states and that they can click **Apply draft** in the editor when ready.
+
+## Manifest shape
+
+Keep the manifest small and descriptive:
+
+```json
+{
+  "kind": "blockbite-frame-draft",
+  "version": 1,
+  "id": "<id>",
+  "site": "<site>",
+  "draft": "drafts/<id>/draft.liquid"
+}
+```
+
+## Authoring rules
+
+- Write `draft.liquid` only. Do not create `style.css`, `module.ts`,
+  `fields.yaml`, `seeds.json`, or `recipe.json`.
+- Do not write under `templates/` or `islands/`.
+- Do not edit `post_content`, call sync/apply tools, or save/publish the page.
+- Use BlockBite UI-DSL Liquid only. The editor will compile it to serialized
+  block JSON/markup during polling.
+- Prefer `bb/frame`, `bb/group`, `bb/richtext`, `bb/image`, `bb/button`, and
+  safe core blocks that the UI-DSL compiler already supports.
+- Keep all styling in UI-DSL block attributes/classes. No free-standing CSS for
+  this V1 workflow.
+- If the user asks for an iteration on the same draft, overwrite the same
+  `draft.liquid`; the editor will detect the changed file hash and recompile.
+
+## Minimal Liquid example
+
+```liquid
+{% ui 'bb/frame', class: 'mx-auto max-w-5xl px-6 py-16 bg-white' %}
+  {% ui 'bb/group', class: 'grid gap-6 md:grid-cols-2 items-center' %}
+    {% ui 'bb/richtext', contentTag: 'h2', class: 'text-4xl font-semibold tracking-normal text-neutral-950', content: 'A focused draft section' /%}
+    {% ui 'bb/richtext', contentTag: 'p', class: 'text-base leading-7 text-neutral-600', content: 'This draft was written through the copied BlockBite frame link and can be applied from the editor toolbar.' /%}
+  {% endui %}
+{% endui %}
+```

package/skills/islands-list/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: islands-list
+description: List the published BlockBite islands (id, nanoid, slug, title) on the selected project's WordPress site. Use when the user asks to list islands, see their islands, or find an island slug/id. Read-only.
+---
+
+# List BlockBite islands
+
+## Steps
+
+1. Ensure a project is selected (use the project-select skill if not).
+2. Call the `blockbite-islands-list` MCP tool (no arguments).
+3. Present each island with its `id`, `nanoid`, `slug`, and `title`.
+
+## Notes
+
+- This is the correct, supported way to list islands. **Never** read the site's
+  public WordPress REST API (e.g. `/wp-json/wp/v2/...`) to find islands — the
+  `island` content is not exposed there.
+- If `blockbite-connection-status` shows `bearer_available: false`, that is
+  expected before the first Studio call. Just call `blockbite-islands-list`
+  anyway; it triggers the bearer exchange. Only a `studio_*` error means there is
+  a real connection problem.
+- This tool is read-only: it never exports, imports, or modifies islands or any
+  WordPress content.

package/skills/project-select/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: project-select
+description: Select the active BlockBite project so subsequent Studio tools target the right WordPress site. Use when the user names a project/site to work on, or after listing projects.
+---
+
+# Select a BlockBite project
+
+## Steps
+
+1. If you do not know the project `id`, call `blockbite-projects-list` first.
+2. Call `blockbite-project-select` with `{ "projectId": "<id>" }`.
+3. Confirm selection with `blockbite-connection-status`.
+
+## Notes
+
+- Selection is required before any `blockbite-template-*`, `blockbite-workspace-*`,
+  `blockbite-sync-plan-*`, or `blockbite-sandbox-*` tool will run.
+- A single-project account is selected automatically; you can still re-select
+  explicitly to switch sites.

package/skills/projects-list/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: projects-list
+description: List the BlockBite projects the connected Platform account can access. Use when the user asks which BlockBite projects or sites are available, or before selecting a project.
+---
+
+# List BlockBite projects
+
+## Steps
+
+1. Call the `blockbite-projects-list` MCP tool (no arguments).
+2. Present each project with its `id`, `name`, `access` (owner or creator-seat),
+   and connected `studio_site_url`.
+3. Highlight the currently selected project if `selected_project_id` is set.
+
+## Next
+
+- To act on a project, use the project-select skill with the project `id`.

package/skills/render-preview/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: render-preview
+description: Render a seed-backed preview of a BlockBite template so proposed pages can be inspected without touching live WordPress posts. Use when the user wants to see how a template looks.
+---
+
+# Render a BlockBite template preview
+
+## Steps
+
+1. Ensure a project is selected.
+2. Call `blockbite-template-render-preview` with `{ "slug": "<slug>" }` or
+   `{ "view": "templates/<slug>/template.liquid" }`. The preview uses seed data
+   only (`dataMode: "seed"`).
+3. Return the preview URL to the user as the deliverable.
+
+## Notes
+
+- Previews never create or read live posts. They are safe to run repeatedly.
+- The preview URL is the deliverable. Do **not** open a browser or use browser
+  automation to "verify" it — just return the link.

package/skills/sandbox-status/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: sandbox-status
+description: Show the BlockBite sandbox readiness and the pending change ledger for the selected project. Use when the user asks what is staged, or before approving/promoting changes.
+---
+
+# BlockBite sandbox status
+
+## Steps
+
+1. Ensure a project is selected.
+2. Call `blockbite-sandbox-status` (no arguments).
+3. Report sandbox readiness, the active session, and pending packages from the
+   audit ledger.
+
+## Notes
+
+- This is read-only; it never modifies files or the ledger.
+- Promotion/approval of the sandbox happens in WordPress by the site owner.

package/skills/site-motion-pass/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: site-motion-pass
+description: Add motion and interactivity to an already approved static BlockBite site or dynamic-template island, including Alpine state, GSAP/ScrollTrigger/SplitText, Swiper sliders, marquees, reduced-motion behavior, ESM/CDN registration, build validation, and frontend error checks.
+---
+
+# Site Motion Pass
+
+Use this skill only after the static layout has been reviewed and accepted. Do not use motion work to compensate for unfinished static design matching.
+
+## Inputs
+
+Require:
+
+- approved static page or island target
+- template slug or blueprint page slug
+- intended interaction or animation behavior
+- current build mode and command prefix, or enough context to discover them
+
+If the static layout has not been approved, stop and request a static review first.
+
+## Read First
+
+- `dev/skills/template-figma/SKILL.md` or `dev/skills/template-new/SKILL.md` for the template package contract.
+- `dev/skills/document-blueprint/SKILL.md` when working through a page blueprint preview.
+- `dev/skills/references/tailwind-utilities.md` before adding CSS for masks, marquee tracks, or direct-child styling.
+- The relevant template `template.liquid`, `style.css`, `module.ts`, `manifest.json`, and blueprint seed files.
+
+## Implementation Rules
+
+- Use Alpine first for nav menus, accordions, tabs, filters, toggles, and simple state.
+- Use `x-collapse` only when Alpine collapse is registered.
+- Use `module.ts` for Swiper, GSAP, ScrollTrigger, SplitText, custom timeline coordination, or behavior Alpine cannot express cleanly.
+- Keep animations progressive: the content must remain usable if JavaScript fails.
+- Add `motion-reduce:*` Tailwind classes or CSS `prefers-reduced-motion` handling for every meaningful motion effect.
+- Do not rewrite static layout while adding motion unless a layout bug prevents the interaction from working.
+- Keep motion scoped to the island or page. Avoid global selectors except for intentionally shared runtime hooks.
+
+## Library Registration
+
+Register only libraries that are actually used:
+
+- Alpine for simple state.
+- Alpine collapse for `x-collapse`.
+- GSAP for timeline/reveal animation.
+- ScrollTrigger for scroll-bound animation.
+- SplitText for text-splitting effects.
+- Swiper for sliders/carousels.
+
+Use BlockBite CDN/ESM commands discovered from `<prefix> bb learn`, `<prefix> bb --help`, or relevant workspace docs. Do not hand-edit runtime internals.
+
+## Common Patterns
+
+- FAQ: Alpine state, `x-show`, `x-collapse`, keyboard/focus-safe buttons, collapse plugin registered.
+- Header/nav: Alpine open state, escape/resize handling when needed, focusable controls, no hidden desktop nav on mobile.
+- Logo marquee: CSS keyframes in `style.css`, duplicated track items in Liquid, pause on hover if expected, reduced-motion fallback.
+- Slider: Swiper in `module.ts`, stable slide widths/heights, accessible buttons, shared `slider-arrow` block style when appropriate.
+- Reveals: GSAP/ScrollTrigger in `module.ts`, no reveal that hides content permanently, reduced-motion immediate-visible fallback.
+
+## Validation
+
+After edits:
+
+```bash
+<prefix> bb validate
+<prefix> bb autobuild
+```
+
+Open the page or blueprint preview and inspect:
+
+- browser console errors
+- failed network/module requests
+- `window.BlockBiteDebug?.errors` when available
+- desktop and mobile behavior
+- reduced-motion behavior
+- slider/marquee/reveal state after resize
+
+If errors appear, use the concrete console/network/runtime failure to identify the path before changing code.
+
+## Finish
+
+Report:
+
+- template or page target
+- interactions added
+- libraries registered or confirmed
+- files changed
+- validation/build/browser checks run
+- remaining static mismatches, if any