菜单
Audit CLAUDE.md files for redundancy, verbosity, and adherence to best practices. This skill should be used when reviewing, improving, or cleaning up CLAUDE.md files to ensure they remain effective and concise.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run a kill-spawn UI/UX prototyping feedback loop from a 1-sentence brief. Hearing → brief/flow → designer → evaluator (max 15 rounds, fresh context per round) → HITL. Uses HTML + Tailwind CDN single-file output for minimum-viable verification.
アプリ開発の起点。ユーザーの要求から KPI → Spec → Story → (UI screens) の 4 段収束レビューループで設計ドキュメント一式を生成する。Ticket は作らず、/generate が lazy materialization する。Trigger: アプリ作って, 〜を作りたい, 設計して, spec, 仕様, 企画
テストの報酬ハックを検出し、AC カバレッジを確認する。context:fork で実装者から独立。
E2E + UI/デザイン評価。アプリを実動テストし、AC 検証 + デザイン4軸評価を行う。Trigger: E2Eテスト, 受け入れテスト, UIチェック, デザイン評価
自律開発 harness の内側ループ orchestrator。Story から lazy に Sprint Contract を交渉し、決定論 tier 判定 (T1/T2/T3) で fork 構成を選択、atomic skill 群をチェインして 1 sprint を完遂する。旧 /tdd-cycle と /ticket-cycle を統合。Trigger: /generate <story-id>, /generate --dry-run, sprint実行
TDD GREEN phase - テストを通す実装を作成。context:fork で tester コンテキストから分離。
| name | claude-md-auditor |
| description | Audit CLAUDE.md files for redundancy, verbosity, and adherence to best practices. This skill should be used when reviewing, improving, or cleaning up CLAUDE.md files to ensure they remain effective and concise. |
| disable-model-invocation | true |
Audit and improve CLAUDE.md files based on Claude Code Best Practices.
Read the CLAUDE.md file specified by $ARGUMENTS. If no path is provided, look for CLAUDE.md in the current working directory.
Read references/best-practices.md to understand the evaluation criteria.
For each section in CLAUDE.md, evaluate:
Output a structured report in this format:
# CLAUDE.md Audit Report
## Summary
- Total lines: X
- Lines to remove: Y
- Lines to improve: Z
- Health score: X/10
## Issues Found
### Redundant Content
[List items that Claude can infer from code]
### Overly Verbose
[List sections that should be condensed]
### Stale/Outdated
[List references to old patterns or removed features]
### Vague Instructions
[List non-actionable guidance]
### Missing Information
[List recommended additions based on codebase analysis]
## Recommended Changes
### Remove
[Specific lines/sections to delete]
### Condense
[Suggestions for making sections more concise]
### Add
[Recommended additions with rationale]
After presenting the report, ask the user if they want to apply the recommended changes automatically.