Menu
Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 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.
Use when get-design-context returns empty or near-empty and the user wants a full design system seeded on a greenfield Bricks install. Prescriptive flow: palette + shades, spacing scale, typography scale, root theme style, base classes: in the right order.
| name | bricks-skills-update |
| description | Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack. |
| allowed-tools | ["Bash","Read"] |
Requires: Bricks skills installed from https://github.com/codeerhq/bricks-skills
Use this skill when the update check prints:
BRICKS_SKILLS_UPDATE_AVAILABLE <old> <new> <tag>
_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
echo "$_BS_UPDATE_CHECK"
If no path is found, tell the user the update checker is not available in this install and point them to the README install section.
Force a fresh check:
sh "$_BS_UPDATE_CHECK" --force || true
_BS_ROOT=$(cd "$(dirname "$_BS_UPDATE_CHECK")/.." && pwd)
sh "$_BS_ROOT/scripts/bricks-skills-upgrade" "<tag>"
If the update check did not include a tag, omit the argument. The script will fetch the latest GitHub Release tag itself.
BRICKS_SKILLS_NOT_GIT_INSTALL, this install is managed by the host client rather than by a Bricks-owned git checkout. Tell the user to either:/plugin marketplace update bricks-skills in Claude Code.If the upgrade script prints BRICKS_SKILLS_NO_RELEASE_FOUND, no published GitHub Release is available yet. Tell the user to keep the current version.
If the upgrade succeeds and the user is using Claude Code plugin install from a local marketplace, tell them to run:
/plugin marketplace update bricks-skills
/reload-plugins
This refreshes Claude Code's installed plugin cache from the updated git checkout.
If the upgrade succeeds, read CHANGELOG.md and summarize the changes between the old and new versions in 3-5 bullets.
If the upgrade script prints BRICKS_SKILLS_LOCAL_CHANGES_STASHED, tell the user local changes were stashed in the skills repo and can be restored manually from that repo with git stash pop.
If the upgrade script prints BRICKS_SKILLS_STASH_FAILED, stop. No fetch or checkout was attempted; inspect the reported git error before retrying.
If it prints BRICKS_SKILLS_WORKTREE_NOT_CLEAN, stop. The script refused to fetch or check out a release because changes remained after the stash attempt. Inspect both git status and git stash list before retrying.