メニュー
Use when the user asks what a project `.scratch/` folder is for, wants a safe place for temporary scripts/artifacts, or needs guidance on promoting ad-hoc work into committed project code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | scratch |
| description | Use when the user asks what a project `.scratch/` folder is for, wants a safe place for temporary scripts/artifacts, or needs guidance on promoting ad-hoc work into committed project code. |
A lightweight convention for a project's .scratch/ folder.
Use .scratch/ for temporary, project-local work that is useful during development but should not yet live in the main codebase.
.scratch/bin/, scripts/, docs/, tests, or a real module..env, credentials, tokens, private keys, or customer data in .scratch/.When working in a project:
.scratch/.If .scratch/README.md is missing, create it from this skill's template if available:
mkdir -p .scratch
cp .claude/skills/scratch/templates/README.md .scratch/README.md
If the skill is installed globally instead of project-locally, copy the template manually from the installed skill directory or write the rules above into .scratch/README.md.
When applying this skill, be practical and concise:
.scratch/ exists,.scratch/.Use when the user wants an HTML discussion artifact — a page generated and revised over the life of a conversation. Best for planning a feature, comparing options, surfacing decisions with options grids, recapping analysis, dogfooding a design. Pages save to .scratch/<slug>.html with a sibling .scratch/<slug>.json manifest as source of truth. Sections are byte-addressable by ID via shell scripts in bin/, so revisions cost ~10 tokens each instead of re-reading a 30KB file. Not a build system; not a replacement for visual-explainer.
Use when the user wants an HTML discussion artifact — a page generated and revised over the life of a conversation. Best for planning a feature, comparing options, surfacing decisions with options grids, recapping analysis, dogfooding a design. Pages save to .scratch/<slug>.html with a sibling .scratch/<slug>.json manifest as source of truth. Sections are byte-addressable by ID via shell scripts in bin/, so revisions cost ~10 tokens each instead of re-reading a 30KB file. Not a build system; not a replacement for visual-explainer.
Simulates pair programming with a third-party auditor for autonomous execution of work. Point it at a task, a list of tasks, or a plan with scoped scenarios — the lead decomposes as needed and dispatches a per-scenario trio (ping = navigator, pong = driver, auditor = QC). Use when prior attempts produced premature-done or wrong-diagnosis loops, or when the user invokes /ping-pong.
Claude Code dev-session analytics for THIS repo — DuckDB views over the native session JSONL logs at `~/.claude/projects/<project>/*.jsonl`. Tracks token spend, tool calls, skill activations, sessions, cache efficiency. Use when answering "how much did today cost?", "what tools am I using most?", "show me my last 5 sessions", "which sessions burned the most tokens?".
Run, extract, update, or check the status of the FlowStay feature catalog at `features/`. Use when the user invokes `/features`, asks to extract features from the architecture doc, asks to run the feature catalog against the codebase, asks to re-sync the catalog after a doc edit, or asks about catalog coverage status.
Simulates pair programming with a third-party auditor for autonomous execution of work. Point it at a task, a list of tasks, or a plan with scoped scenarios — the lead decomposes as needed and dispatches a per-scenario trio (ping = navigator, pong = driver, auditor = QC). Use when prior attempts produced premature-done or wrong-diagnosis loops, or when the user invokes /ping-pong.