メニュー
Nebula-specific overlay for Canvas Workbench pages. Use when you need the repository-local rule that `examples/pages/` is reference-only and active Workbench pages belong in `pages/`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for any task touching site chrome — header, footer, sidebar, or global navigation that repeats across pages — and for any region-spec work (create, modify, review, validate region JSON, or the project-level layout component). Also load when a task creates or edits multiple pages that share chrome, or asks for a "site" or "navigation between pages"; shared chrome belongs in regions, never inlined into page JSON.
Create and modify content templates that map Drupal content entities to Canvas component layouts. Use when asked to (1) Create a new content template, (2) Modify an existing content template, (3) Add or change entity field mappings in a template, (4) Compose components in a content template via slots. Content templates live in the configured `contentTemplatesDir` (default `content-templates/`) and define how Drupal entity types, bundles, and view modes render as Canvas component trees.
Push validated Canvas component changes to Drupal Canvas and recover from common push failures. Use only when the user explicitly requests a push/publish/sync action. Handles dependency-related push failures that require retry.
Acquia Source only. Create and edit Drupal menus in the CMS via Source MCP. Do not use for non-Source sites; production nav should still be authored in Drupal, not only in component code.
Design Canvas-ready React components with slots and decomposition-first patterns. Use when (1) Designing a component's prop/slot structure, (2) A component is growing too large, (3) Deciding between props vs slots, (4) Refactoring monolithic components, (5) Modeling repeatable list/grid content, (6) Reusing, composing, or wrapping existing workspace components. Ensures Canvas compatibility.
Start here for any React component task to enforce the canonical Canvas component contract. Use for create, modify, refactor, review, migrate, or validate work. Establishes the canonical Canvas component contract, assuming repository components are Canvas targets, and guides either (1) transforming existing components to meet Canvas requirements or (2) creating new Canvas-ready components.
| name | nebula-workbench-pages |
| description | Nebula-specific overlay for Canvas Workbench pages. Use when you need the repository-local rule that `examples/pages/` is reference-only and active Workbench pages belong in `pages/`. |
Author active Workbench page previews in the top-level pages/ directory.
Nebula may also keep reference examples in examples/pages/, but those are
examples only and should not replace the canonical Workbench pages directory.
If the repository includes examples/pages/, use those files as reference input
when authoring real Workbench pages in pages/.
Only pages in the canonical pages/ directory are valid local verification
targets in this repository. After creating or visually modifying a page, use
nebula-component-validation to run repo-local static validation.
Use canvas-page-definition for the generic page-spec contract, and
canvas-workbench/references/pages.md for the Workbench-specific page preview
flow.
