菜单
Use when running Bricks housekeeping: "regenerate all CSS files", "find orphaned elements", "clean up abandoned builder data". Covers `bricks/regenerate-css-files`, `bricks/list-orphaned-elements`, `bricks/cleanup-orphaned-elements`. Excludes code-signature regeneration.
用 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-maintenance |
| description | Use when running Bricks housekeeping: "regenerate all CSS files", "find orphaned elements", "clean up abandoned builder data". Covers `bricks/regenerate-css-files`, `bricks/list-orphaned-elements`, `bricks/cleanup-orphaned-elements`. Excludes code-signature regeneration. |
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.
Three admin-only housekeeping abilities mirror Bricks maintenance actions (includes/abilities/maintenance.php):
bricks/regenerate-css-files: rebuild Bricks CSS files.bricks/list-orphaned-elements: scan for element rows whose parent id no longer exists in the same tree.bricks/cleanup-orphaned-elements: remove those orphan rows.bricks/regenerate-css-filesInput schema is empty:
bricks/regenerate-css-files
-> { success: true, generatedFiles: [...], generatedFileCount: 42, cssLoading: "file" }
There is no postIds parameter. The ability runs the site-wide Bricks file-regeneration helper.
Use it after:
cssLoading to file mode and needing the generated files ready.Normal builder saves regenerate the affected post CSS automatically. This ability is the bulk version.
An orphan is an element whose parent id references another element that does not exist in the same meta tree.
The list operation is read-only:
bricks/list-orphaned-elements
-> { totalOrphans: 47, totalPosts: 12, orphansByPostId: { "42": [...] } }
Cleanup input schema is empty and sweeps all detected orphans:
bricks/cleanup-orphaned-elements
-> { success: true, totalCleaned: 47, postsCleaned: 12, message: "Removed 47 orphaned elements across 12 posts." }
Destructive. Always run list-orphaned-elements first and review the affected posts. There is no MCP parameter for limiting cleanup to a selected post list.
Code-signature regeneration exists in the admin UI, but it is not registered as an MCP ability. It will not appear in bricks/list-ability-status, and it should stay admin-only because regenerating signatures can unblock previously quarantined code.
Academy reference: https://academy-preview.bricksbuilder.io/builder/features/code-signatures/
If a
bricks/*ability is not available as a direct tool: first check whether it is outside the fast path and call it throughmcp-adapter-execute-abilitywithability_name: "bricks/<name>". If the dispatcher also rejects it, callbricks-list-ability-statusto check whether a site admin disabled it under Bricks > AI.
bricks/list-orphaned-elements
-> { totalOrphans: 47, totalPosts: 12, orphansByPostId: {...} }
# Review the affected posts. If cleanup is expected:
bricks/cleanup-orphaned-elements
-> { success: true, totalCleaned: 47, postsCleaned: 12, message: "Removed 47 orphaned elements across 12 posts." }
bricks/regenerate-css-files
-> { success: true, generatedFileCount: 1423, cssLoading: "file" }
postIds to maintenance abilities. Current schemas do not accept it.cleanup-orphaned-elements without reviewing list-orphaned-elements first.