ワンクリックでManusで任意のスキルを実行

progressive-disclosure

スター12

フォーク1

更新日2026年5月21日 09:58

This skill should be used when the user asks to "analyze documentation structure", "audit progressive disclosure", "restructure CLAUDE.md", "restructure AGENTS.md", "create a documentation index", "organize project docs", "find orphaned docs", "map documentation references", "improve context loading", or mentions progressive disclosure, documentation hierarchy, root configuration file organization, or context rot prevention. Analyzes or restructures how a repository discloses documentation through root configuration files.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

florianbuetow

florianbuetow/claude-code

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Progressive Disclosure

Analyze and restructure how a repository progressively discloses its documentation through root configuration files (AGENTS.md, CLAUDE.md, GEMINI.md, USER.md, TOOLS.md, BOOTSTRAP.md, DESIGN.md, NOTICE.md). Maps reference graphs, detects orphaned documents, and generates thematic book-style indexes to prevent context rot.

Routing

This skill auto-selects the correct workflow based on user intent.

Step 1: Determine Mode

User asks to analyze, audit, map, or assess — Route to progressive-disclosure:analyze
User asks to restructure, refactor, index, or organize — Route to progressive-disclosure:restructure
No explicit mode specified — Default to progressive-disclosure:analyze

Step 2: Invoke

Invoke the appropriate subskill. Do not duplicate their logic here.

このリポジトリの他の Skills

同じリポジトリ

clean-code

florianbuetow/claude-code

This skill should be used when the user asks to "check clean code", "review code cleanliness", "find code smells", "is this function too long", "are these names clear", "review my error handling", "check my tests", or "clean up this code". Also triggers when the user mentions Clean Code, Uncle Bob, Robert Martin, meaningful names, function length, comment rot, F.I.R.S.T. tests, or names a dimension directly ("naming", "boundaries", "concurrency"). Supports auditing all nine dimensions at once or focusing on a single dimension.

2026-07-2312

agent-guardrails-analyze

florianbuetow/claude-code

Scan Claude Code chat session logs for recurring agent anti-patterns (hedging, stalling, skipping, false completions, preference-asking, dismissing, cosmetic, caveats, flagging) and produce a ranked report with frequency counts, example excerpts, and suggested guardrail rules. Use when user asks to "analyze sessions for anti-patterns", "find bad patterns in logs", "what anti-patterns am I seeing", "agent-guardrails analyze", or wants data-driven guardrail recommendations.

2026-07-1912

agent-guardrails-install

florianbuetow/claude-code

Install agent behavioral guardrail rules into a project's .claude/ directory. Generates a Stop hook bash script and configures settings.local.json. Includes nine battle-tested rules (no-guessing, no-stalling, no-preference-asking, no-false-completion, no-skipping, no-dismissing, no-cosmetic, no-caveats, no-flagging). Use when user asks to "install guardrails", "set up agent guardrails", "add behavioral hooks", "agent-guardrails install", or wants to enforce assistant discipline.

2026-07-1912

agent-guardrails-test

florianbuetow/claude-code

Test installed agent guardrail hooks by sending trigger phrases through the stop hook script. Checks hook installation first, then runs two test phrases per rule. Use when user asks to "test guardrails", "verify hooks", "check guardrail patterns", "agent-guardrails test", or wants to confirm hooks are working.

2026-07-1912

agent-guardrails-update

florianbuetow/claude-code

Re-analyze Claude Code session logs against existing agent guardrail rules to measure effectiveness, catch false positives, identify missed anti-patterns, and refine regex patterns. Use when user asks to "update guardrails", "refine guardrail rules", "check guardrail effectiveness", "agent-guardrails update", "tune guardrails", or wants to improve existing behavioral rules based on real usage data.

2026-07-1912

product-spec

florianbuetow/claude-code

Use when the user wants to write a "product spec" or "product specification", frame a "product bet", or define a falsifiable hypothesis before building. Also triggers on "replace the PRD", "retire the PRD", "the PRD is too long / too vague", "tighten this spec for an engineer or agent", "what's the bet", "what problem are we solving", "acceptance criteria", "success criteria", "kill / scale / graduate thresholds", "measurement plan", or when scoping a feature's problem, bet, success behaviors, and evaluation before any behavioral spec. Part of the spec-dd workflow; precedes /spec-dd:spec.

2026-06-2912

name	progressive-disclosure
description	This skill should be used when the user asks to "analyze documentation structure", "audit progressive disclosure", "restructure CLAUDE.md", "restructure AGENTS.md", "create a documentation index", "organize project docs", "find orphaned docs", "map documentation references", "improve context loading", or mentions progressive disclosure, documentation hierarchy, root configuration file organization, or context rot prevention. Analyzes or restructures how a repository discloses documentation through root configuration files.
disable-model-invocation	false

Progressive Disclosure

Routing

This skill auto-selects the correct workflow based on user intent.

Step 1: Determine Mode

User asks to analyze, audit, map, or assess — Route to progressive-disclosure:analyze
User asks to restructure, refactor, index, or organize — Route to progressive-disclosure:restructure
No explicit mode specified — Default to progressive-disclosure:analyze

Step 2: Invoke

Invoke the appropriate subskill. Do not duplicate their logic here.