Slash Command

/audit

Find UI inconsistencies in your code — off-grid spacing, wrong depth strategy, out-of-palette colors, and component drift from established patterns. Reports violations with file and line numbers. Add --fix to auto-correct safe issues.

From claude-frontforge

Install

Run in your terminal

npx claudepluginhub thiagoedson/claude-frontforge --plugin claude-frontforge

Details

Namespacecommands/

Command Content

Other plugins with /audit

/audit

Logs agent interactions (prompts, responses, tool calls) to append-only .beads/interactions.jsonl. Also supports labeling prior entries via record|label args.

beads

20.3k

/audit

commands/

Audits UI code against design system for spacing, depth, color, and pattern violations. Reports file-specific issues and suggestions. Supports path argument or defaults to common UI paths.

interface-design

4.4k

/audit

security/

Performs security audit of codebase covering dependencies, secrets, OWASP Top 10, inputs, and auth. Produces severity-prioritized report with findings, fixes, and references.

claude-code-toolkit

1.0k

/audit

Runs Rust security audits (default) with cargo audit and geiger, or safety/concurrency/full modes using miri, rudra, lockbud. Outputs prioritized vulnerability reports and fix recommendations.

rust-skills

892

/audit

Audits iOS/Swift projects for issues like memory leaks, concurrency, accessibility, and security. Analyzes codebase to suggest relevant audits or runs specified area.

axiom

692

/audit

Performs security audit on codebase or specified target, checking dependency vulnerabilities, auth, input validation, data exposure, configs, and secrets. Outputs prioritized findings with remediation steps.

Bash(find:*)Bash(grep:*)

audit

624

Stats

Stars1

Forks0

Last CommitMar 16, 2026

Actions

View Source View Plugin View on GitHub View README

claude-frontforge audit

Check existing code against your design system.

Usage

/audit <path>        # Audit specific file/directory
/audit               # Audit common UI paths
/audit <path> --fix  # Auto-fix violations where safe

What to Check

If .frontforge/system.md exists:

Spacing violations
- Find spacing values not on defined grid
- Example: 17px when base is 4px
Depth violations
- Borders-only system → flag shadows
- Subtle system → flag layered shadows
- Allow ring shadows (0 0 0 1px)
Color violations
- If palette defined → flag colors not in palette
- Allow semantic grays
Pattern drift
- Find buttons not matching Button pattern
- Find cards not matching Card pattern

Report format:

Audit Results: src/components/

Violations:
  Button.tsx:12 - Height 38px (pattern: 36px)
  Card.tsx:8 - Shadow used (system: borders-only)
  Input.tsx:20 - Spacing 14px (grid: 4px, nearest: 12px or 16px)

Suggestions:
  - Update Button height to match pattern
  - Replace shadow with border
  - Adjust spacing to grid

If no system.md:

No design system to audit against.

Create a system first:
1. Build UI → establish system automatically
2. Run /extract → create system from existing code

Auto-Fix Mode

When --fix is passed, automatically correct safe violations:

Safe to auto-fix:

Spacing snapped to nearest grid value (e.g., 14px → 12px or 16px)
Shadow replaced with border when system is borders-only

Requires confirmation:

Color changes (palette drift)
Pattern deviations (height/padding changes to components)

Always show a diff preview and ask for confirmation before applying fixes:

Ready to fix 3 violations:
  Button.tsx:12 — 38px → 36px (pattern)
  Card.tsx:8    — shadow → border (depth)
  Input.tsx:20  — 14px → 16px (grid)

Apply these changes? (y/n/review each)

Implementation

Check for system.md
Parse system rules
Read target files (tsx, jsx, css, scss)
Compare against rules
Report violations with suggestions
If --fix: collect safe fixes, preview diff, apply on confirmation