apply

A command that creates UI components, such as buttons, cards, modals, and forms, according to a project's design settings and accessibility practices.

In plain words
What is it for?
Use it to generate React or TypeScript component code and variants from the project's design configuration, with checks for design anti-patterns.
Why use it?
It reduces repetitive setup and helps new components stay consistent with the existing visual system while avoiding common interface mistakes.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/b1rdmania/ghostclaw/apply
Clone the repo
git clone --depth 1 https://github.com/b1rdmania/ghostclaw

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02012
Opus 5 $0.00000 $0.01006
Sonnet 5 $0.00000 $0.00402
Haiku 4.5 $0.00000 $0.00201

Measured 2d ago against content hash 4c63b083ce13, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

apply scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/design/commands/apply.md · 294 lines

How it starts

The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Apply

Generate new components using your design system configuration and best practices from Impeccable.

Purpose

Create new UI components that:

  • Follow your design system rules (.design.json)
  • Apply Impeccable principles (typography, color, spatial design, etc.)
  • Avoid common anti-patterns
  • Are production-ready with proper accessibility

When to Use

  • Creating new components from scratch
  • Scaffolding component variants (primary/secondary buttons, card types, etc.)
  • Generating boilerplate that follows your design rules
  • Prototyping new UI elements

How It Works

  1. Load Design System: Read .design.json (or use minimal defaults)
  2. Load Best Practices: Read relevant Impeccable references
  3. Generate Component: Create code following both layers
  4. Anti-Pattern Check: Verify no anti-patterns were introduced
  5. Return Code: Provide ready-to-use component code

Usage

/design-apply <component-type> [variant]

Examples:

/design-apply button
/design-apply button primary
/design-apply card
/design-apply modal
/design-apply form

What You Get

The command generates:

  1. Component Code: React/TypeScript component (or your framework)
  2. Design Notes: Why specific choices were made
  3. Accessibility: ARIA labels, keyboard nav, focus management
  4. Variants: Common variants (size, style, state)
  5. Usage Example: How to use the component

Design System Integration

The component will use:

  • Your color palette from .design.json
  • Your typography scale
  • Your spacing system
  • Your motion tokens (if defined)
  • Your component-specific overrides

If no .design.json exists, uses sensible defaults from examples/minimal.json.

Best Practices Applied

Typography

  • Proper font family from your design system
  • Correct type scale for hierarchy
  • Optimal line-height and letter-spacing
  • Accessible font sizes (min 16px for body)

Color & Contrast

  • WCAG AA contrast ratios (4.5:1 text, 3:1 UI)
  • Semantic color usage (error = red, success = green)
  • OKLCH for consistent perceived brightness
  • Avoids anti-patterns (gray on colored backgrounds)

Read the full file on GitHub · 294 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 294 lines · 0 tokens per session scan A 4c63b083ce13

Subscribe to this mod's changes

apply is a command published in the GitHub repository b1rdmania/ghostclaw (91 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,012 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.