원클릭으로 Manus에서 모든 스킬 실행

bricks-site-audit

스타16

포크0

업데이트2026년 6월 16일 06:49

Use for a complete site-wide health check: "audit my site", "what's wrong with my Bricks install", "check everything". Covers design rot, template hygiene, revision bloat, dynamic-data mismatches, and Bricks abilities availability. For design-system-only audits, use bricks-audit-design-system instead.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

codeerhq

codeerhq/bricks-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Update check

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.

Bricks: site audit

A structured read-only audit. Uses only ability reads: never mutates.

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.

Checks

1. Design-system rot

Call bricks/audit-design-system (scope: "all"). It returns severity-tagged issues covering orphan references, unused classes/variables/components, dead theme styles, and palette fragmentation. Use the bricks-audit-design-system skill for how to triage and fix the output.

Manual follow-ups the ability doesn't cover:

Duplicate-intent classes. .button + .btn, .card + .cards. Read list-global-classes and scan names.
Single-use components. usageCount === 1 from get-design-context with includeUsage: true: was it meant to be reused, or should it be inlined back?

2. Template hygiene

Call bricks/list-templates.

Unused templates. No condition, not referenced.
Overlapping template conditions. Two templates both targeting archive: products: only one wins, the other is dead weight.
Missing default templates. No default single template means the theme's built-in template runs, which may not be what the user expects.

3. Revision bloat

For posts with Bricks data, count revisions via bricks/list-revisions. Post with >50 revisions is a candidate for cleanup (revisions accumulate on every save).

4. Dynamic data

Call bricks/list-dynamic-data-tags and bricks/list-cms-sources.

Missing providers referenced in content. Posts using {acf_foo} on a site without ACF installed. Check by scanning element settings for {*} patterns that don't resolve against list-dynamic-data-tags.
Ambiguous modifiers. Tags using |upper (JS pipe syntax) instead of :upper (Bricks syntax): broken.

5. Bricks abilities

Call bricks/get-mcp-version. Record bricksVersion, bricksAbilitiesVersion, adapterVersion, wordpressVersion, abilitiesApiActive, and disabledAbilityCount. If an expected bricks/* ability is missing as a direct tool, remember that many abilities are dispatcher-only; call bricks/list-ability-status before concluding the site is outdated or misconfigured.

Report format

Return a structured audit:

## Design system
- Fragmentation: <count> issues
- Duplicate-intent classes: <list>
- Unused classes (>30 days): <list>
- ...

## Components
- Orphans: <list>
- Single-use (candidates for inline): <list>

## Templates
- Overlapping conditions: <list>
- Unused: <list>

## Revisions
- Posts with >50 revisions: <list>

## Dynamic data
- Missing providers: <list>
- Broken tag syntax: <list>

## Bricks abilities
- Abilities version: <bricksAbilitiesVersion>
- Missing expected abilities: <list or none>

Never do

Never perform cleanup actions from this audit: only report. The user must explicitly approve any deletion or consolidation.
Never blame the user. Phrase findings as observations, not judgments.

이 저장소의 다른 Skills

같은 저장소

bricks-custom-controls

codeerhq/bricks-skills

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.

2026-07-1416

bricks-element-schemas

codeerhq/bricks-skills

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.

2026-07-1416

bricks-quality-gate

codeerhq/bricks-skills

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.

2026-07-1416

bricks-skills-update

codeerhq/bricks-skills

Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack.

2026-07-1416

bricks-start-here

codeerhq/bricks-skills

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.

2026-07-1416

bricks-design-systems

codeerhq/bricks-skills

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.

2026-07-0816

name	bricks-site-audit
description	Use for a complete site-wide health check: "audit my site", "what's wrong with my Bricks install", "check everything". Covers design rot, template hygiene, revision bloat, dynamic-data mismatches, and Bricks abilities availability. For design-system-only audits, use bricks-audit-design-system instead.

Requires: Bricks 2.4+ with the Abilities API enabled

Update check

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

Bricks: site audit

A structured read-only audit. Uses only ability reads: never mutates.

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.

Checks

1. Design-system rot

Manual follow-ups the ability doesn't cover:

Duplicate-intent classes. .button + .btn, .card + .cards. Read list-global-classes and scan names.
Single-use components. usageCount === 1 from get-design-context with includeUsage: true: was it meant to be reused, or should it be inlined back?

2. Template hygiene

Call bricks/list-templates.

Unused templates. No condition, not referenced.
Overlapping template conditions. Two templates both targeting archive: products: only one wins, the other is dead weight.
Missing default templates. No default single template means the theme's built-in template runs, which may not be what the user expects.

3. Revision bloat

For posts with Bricks data, count revisions via bricks/list-revisions. Post with >50 revisions is a candidate for cleanup (revisions accumulate on every save).

4. Dynamic data

Call bricks/list-dynamic-data-tags and bricks/list-cms-sources.

Missing providers referenced in content. Posts using {acf_foo} on a site without ACF installed. Check by scanning element settings for {*} patterns that don't resolve against list-dynamic-data-tags.
Ambiguous modifiers. Tags using |upper (JS pipe syntax) instead of :upper (Bricks syntax): broken.

5. Bricks abilities

Report format

Return a structured audit:

## Design system
- Fragmentation: <count> issues
- Duplicate-intent classes: <list>
- Unused classes (>30 days): <list>
- ...

## Components
- Orphans: <list>
- Single-use (candidates for inline): <list>

## Templates
- Overlapping conditions: <list>
- Unused: <list>

## Revisions
- Posts with >50 revisions: <list>

## Dynamic data
- Missing providers: <list>
- Broken tag syntax: <list>

## Bricks abilities
- Abilities version: <bricksAbilitiesVersion>
- Missing expected abilities: <list or none>

Never do

Never perform cleanup actions from this audit: only report. The user must explicitly approve any deletion or consolidation.
Never blame the user. Phrase findings as observations, not judgments.