workflow:ui-design:codify-style

A workflow coordinator that extracts styles from a codebase and creates a versioned reference package with an interactive preview.

In plain words
What is it for?
Use it to document the visual style of an existing project and prepare those references for later planning work.
Why use it?
It turns scattered styling details in source files into a shareable reference that others can inspect and reuse.

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/catlog22/claude-code-workflow/codify-style
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,574 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00030 $0.06574
Opus 5 $0.00015 $0.03287
Sonnet 5 $0.00006 $0.01315
Haiku 4.5 $0.00003 $0.00657

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

Security

Grade C, and why

workflow:ui-design:codify-style scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Bash(rm -rf .workflow/${temp_id})
.claude/commands/workflow/ui-design/codify-style.md · 653 lines

How it starts

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

UI Design: Codify Style (Orchestrator)

Overview & Execution Model

Fully autonomous orchestrator: Coordinates style extraction from codebase and generates shareable reference packages.

Pure Orchestrator Pattern: Does NOT directly execute agent tasks. Delegates to specialized commands:

  1. /workflow:ui-design:import-from-code - Extract styles from source code
  2. /workflow:ui-design:reference-page-generator - Generate versioned reference package with interactive preview

Output: Shareable, versioned style reference package at .workflow/reference_style/{package-name}/

Autonomous Flow (⚠️ CONTINUOUS EXECUTION - DO NOT STOP):

  1. User triggers: /workflow:ui-design:codify-style <path> --package-name <name>
  2. Phase 0: Parameter validation & preparation → IMMEDIATELY triggers Phase 1
  3. Phase 1 (import-from-code) → Attach 4 tasks → Execute tasks → Collapse → Auto-continues to Phase 2
  4. Phase 2 (reference-page-generator) → Attach 4 tasks → Execute tasks → Collapse → Auto-continues to Phase 3
  5. Phase 3 (cleanup & verification) → Execute orchestrator task → Reports completion

Phase Transition Mechanism:

  • Phase 0 (Validation): Validate parameters, prepare workspace → IMMEDIATELY triggers Phase 1
  • Phase 1-2 (Task Attachment): Skill invocation ATTACHES tasks to current workflow. Orchestrator EXECUTES these tasks itself.
  • Task Execution: Orchestrator runs attached tasks sequentially, updating TodoWrite as each completes
  • Task Collapse: After all attached tasks complete, collapse them into phase summary
  • Phase Transition: Automatically execute next phase after collapsing completed tasks
  • No user interaction required after initial command

Auto-Continue Mechanism: TodoWrite tracks phase status with dynamic task attachment/collapse. After executing all attached tasks, you MUST immediately collapse them, restore phase summary, and execute the next phase. No user intervention required. The workflow is NOT complete until reaching Phase 3.

Read the full file on GitHub · 653 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 · 653 lines · 30 tokens per session scan C 9c9426077d44

Subscribe to this mod's changes

workflow:ui-design:codify-style is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 6,574 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.