菜单
Use when moving Bricks data between sites with the unified import/export MCP abilities. Covers transfer-package listing, export, inspect, import, conflict handling, sensitive settings, and site-to-site package migration.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing custom-element controls or debugging control behavior: "what control type for a color?", "conditional control visibility", "dynamic data on a custom control". Covers the ~40 control types, the `required` syntax, CSS-binding via `css` key, dynamic-data support, and default-value gotchas.
Use before writing or editing Bricks element JSON, settings, controls, globals, page settings, or template settings. Gives the runtime lookup order plus bundled full resolved schemas so you can check exact control keys and value shapes instead of guessing.
Use after every write through the Bricks MCP: set-page-elements, update-element, update-element-conditions, update-element-interactions, batch-update-elements, set-template-conditions, set-global-variables, create-theme-style, etc. Defines the verify-after-write loop: read back the change, render the affected post, check for silent failures (empty render, unknown tags, unbalanced braces, query:null). Catches the "tool returned success but the page broke" class of bugs.
Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack.
Use at the start of every Bricks session. Orientation rules: call get-design-context before any design-system write, verify mutations with get-page-elements / list-revisions, and never force same-named globals to duplicate.
Use when creating or updating design tokens: global classes, variables, color palettes, theme styles, components. Enforces uniqueness, scale-generator usage, and conditions on theme styles. Prevents system fragmentation.
| name | bricks-import-export |
| description | Use when moving Bricks data between sites with the unified import/export MCP abilities. Covers transfer-package listing, export, inspect, import, conflict handling, sensitive settings, and site-to-site package migration. |
Requires: Bricks 2.4+ with the Abilities API enabled
Run first when filesystem tools are available:
_BS_UPDATE_CHECK=""
for _CAND in "$HOME/.bricks/skills/bricks-skills/scripts/bricks-skills-update-check" "$PWD/scripts/bricks-skills-update-check" "$HOME/.claude/skills/bricks-skills/scripts/bricks-skills-update-check" "$HOME/.codex/skills/bricks-skills/scripts/bricks-skills-update-check"; do
[ -f "$_CAND" ] && _BS_UPDATE_CHECK="$_CAND" && break
done
[ -n "$_BS_UPDATE_CHECK" ] && sh "$_BS_UPDATE_CHECK" || true
If it prints BRICKS_SKILLS_UPDATE_AVAILABLE <old> <new> <tag>, load bricks-skills-update before continuing. If it prints BRICKS_SKILLS_JUST_UPDATED <old> <new>, mention the new version and continue.
The MCP flow mirrors the Bricks UI import/export package, not the older separate global-data JSON and template ZIP flows.
Use these abilities:
bricks/list-transfer-items: read the current site's export selector and exact item IDs.bricks/export-transfer-package: create a base64 ZIP package from explicit selected item IDs.bricks/inspect-transfer-package: inspect a ZIP before import; returns conflicts, warnings, and zipHash.bricks/import-transfer-package: import selected manifest items. Requires expectedZipHash from inspection.Supported transfer types: color-palettes, theme-styles, classes, variables, custom-fonts, breakpoints, global-queries, components, templates, settings, custom-capabilities.
bricks/list-transfer-items.bricks/export-transfer-package with:{
"types": ["classes", "components", "templates"],
"items": {
"classes": ["abc123"],
"components": ["hero-card"],
"templates": ["100", "101"]
}
}
bricks/inspect-transfer-package with the returned zipBase64.manifest.types.*.items, especially conflict and warning.bricks/import-transfer-package with the same zipBase64, the inspected zipHash as expectedZipHash, and explicit manifest item IDs:{
"zipBase64": "UEsDBBQ...",
"expectedZipHash": "sha256-from-inspect",
"types": ["classes", "components"],
"items": {
"classes": ["abc123"],
"components": ["hero-card"]
},
"conflictMode": "skip"
}
expectedZipHash so the imported ZIP matches the package you reviewed.conflictMode defaults to skip. Use replace only when overwriting is requested, and pass allowOverwrite: true.conflictDecisions, keyed by type and item ID; any replace value also requires allowOverwrite: true.api-keys, custom-code) require allowSensitiveSettings: true on export or import.importImages: true only when media migration is intended and the user can upload files.items is required for each selected type. Do not omit it and assume "everything".breakpoints, use items: { "breakpoints": ["all"] }.builder, performance, api-keys, or custom-code.manifest.json; template-only legacy ZIPs without a manifest are not accepted by the unified import flow.If a bricks/* ability is not available as a direct tool, first check whether it is outside the fast path and call it through mcp-adapter-execute-ability with ability_name: "bricks/<name>". If the dispatcher also rejects it, call bricks-list-ability-status to check whether a site admin disabled it under Bricks > AI.
bricks/export-global-data, bricks/import-global-data, bricks/export-templates, or bricks/import-template-bundle flow for unified package migration.expectedZipHash.replace or per-item replacement decisions without clear user intent.importImages: true is passed.