camox 0.42.0 → 0.44.0

package/skills/camox/SKILL.md

@@ -5,15 +5,44 @@ description: Use when working in a Camox codebase with Block Definitions, Layout
 
 # Camox
 
-Load only the references needed for the current task. Do not preload every reference.
+Read only the references needed for the current task. Do not preload every reference.
 
-- To create or change a **Block Definition** in `src/blocks/`, read [references/block-definitions.md](references/block-definitions.md).
-- To create or change a **Layout Definition** in `src/layouts/`, read [references/layout-definitions.md](references/layout-definitions.md).
-- For any CLI operation, first read [references/cli-common.md](references/cli-common.md), then read only the relevant command reference:
-  - To inspect, create, edit, move, or delete Block instances or their Content, read [references/cli-blocks.md](references/cli-blocks.md).
-  - To inspect, create, update, publish, or assign Layouts to Pages, read [references/cli-pages.md](references/cli-pages.md).
-  - To target production or replicate content between Environments, read [references/cli-environments.md](references/cli-environments.md).
+## Code definitions
 
-For shared content across layouts (typically a navbar or footer), use `synced: true` in `createBlock`. This optional boolean defaults to `false` and is independent of `layoutOnly`. Synced blocks share content and settings and have purple editor highlights. See the Block Definition reference for publishing and existing-instance behavior.
+- Create a block or change its schema or field rendering API in `src/blocks/`:
+  [Block Definitions](references/block-definitions.md).
+- Create or change a curated layout (a reusable shell for editor-created pages), including shared navbar/footer placement:
+  [Layout Definitions](references/layout-definitions.md).
+- Create or change a singleton page (a code-owned fixed URL) or derived route (a code-owned data-driven route) in `src/layouts/`:
+  [Routed layouts](references/routed-layouts.md).
+- Share content across layouts with `synced: true`, independently of `layoutOnly`:
+  [Synced blocks](references/block-definitions.md#synced-blocks-synced-optional).
 
-A request can cross boundaries. For example, adding a new kind of section to a Page may require the Block Definition reference followed by the CLI common and Block references. Load the additional reference only once that need is established.
+## Specialized block work
+
+- DOM listeners, scrolling, browser scripts, or third-party widgets:
+  [DOM integrations](references/dom-integrations.md).
+  Preview DOM lives in an iframe; component globals target the editor.
+- Customize inline text/link formatting or highlights:
+  [Field styling](references/field-styling.md).
+
+For specialized changes to an existing block, read the specialist reference directly. Also read Block Definitions only if creating a block or changing its schema or other field rendering APIs.
+
+## Content and CLI
+
+For any CLI operation, first read [CLI common guidance](references/cli-common.md), then only the relevant command reference:
+
+- Pages, metadata, layout assignments, Block instances, content, ordering, or publishing:
+  [CLI Content](references/cli-content.md).
+- List comments on a Page or resolve a comment by its ID:
+  [CLI Content — Comments](references/cli-content.md#comments).
+- Production targeting or environment replication:
+  [CLI Environments](references/cli-environments.md).
+
+## Addressing feedback
+
+When asked to address feedback on a Page, read [CLI common guidance](references/cli-common.md) and [CLI Content — Comments](references/cli-content.md#comments), plus the relevant references for each change. Run `{{CAMOX_CMD}} comments list --page-id <PAGE_ID>` to load the Page's comments. For each unresolved comment, inspect its message and target, then find the relevant Page, Block, item, or field with the CLI (and its code definition if applicable). Make the required changes using the CLI for content and code for definitions. Only after addressing a comment, run `{{CAMOX_CMD}} comments resolve --page-id <PAGE_ID> --id <COMMENT_UUID>`. Leave comments you could not address unresolved and explain why. Re-list the Page's comments to verify their status. Do not publish draft changes unless requested.
+
+Code definitions do not place blocks on existing Pages or assign their layouts; `blocks.initial` only seeds the initial homepage. When the request includes placement or assignment on existing Pages, follow with the relevant CLI workflow. Singleton pages and derived routes are declared in code, not created through the pages CLI.
+
+A request can cross boundaries. Load an additional reference only once that need is established.