ワンクリックで
complexity-management
Use when frontend files, components, hooks, or helpers exceed complexity gates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when frontend files, components, hooks, or helpers exceed complexity gates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use BEFORE building or changing any UI — components, layout, color, spacing, typography, interaction states, or visual styling — to verify the planned change matches the Figma design via the Figma MCP. Run this gate before writing or editing UI code.
Use when placing features, repositories, hooks, or fixing dependency-cruiser errors.
Use when validating frontend changes before commit, push, or PR.
Use when placing, moving, naming, or splitting frontend files.
Use when retrieving or addressing PR review comments.
Use when creating new repository documentation or agent guides.
| name | complexity-management |
| description | Use when frontend files, components, hooks, or helpers exceed complexity gates. |
This repo uses rust-code-analysis through make lint-metrics. Thresholds live in
config/metrics-policy.json and must not be lowered to pass a change.
make lint-metrics
make lint
If UI behavior changes while reducing complexity, also run the focused client, E2E, or visual test that covers the changed path.
Before applying this skill, confirm the active task against ../AI-AGENT-GUIDE.md and ../SKILL-DECISION-GUIDE.md so every relevant skill is consulted.
Before presenting changes, check changed text files for lines longer than 100 characters.
If any exist, tell the user each path:line and measured character count.
Treat this as disclosure, not failure, unless a project gate fails.