メニュー
Ultra-compressed communication. Drops filler, hedging, and pleasantries while keeping technical terms exact. ~75% token reduction. Use when user says "caveman", "caveman mode", "be terse", or "stop being chatty".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/kwiggen/claude-code-plugin --skill cavemanコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Take the most recent prior assistant message in this conversation, strip Claude Code's ⏺ bullet and 2-space indent, unwrap soft-wrapped paragraphs, and copy the result to the macOS clipboard in a target format (Markdown, Slack mrkdwn, plain text, or HTML). Use when the user says "/clip", "clip that", "copy that for Slack", "copy as plain text", "copy as html", or wants to grab Claude's prior output in paste-friendly form.
Review codebase architecture for deepening opportunities — modules where the interface is nearly as complex as the implementation. Uses depth-as-leverage model and the deletion test. Use when the codebase feels tangled, after a burst of fast development, or when asked to review architecture.
Structured debugging as a state machine: reproduce, minimize, hypothesize, instrument, fix, regression-test. Use when something is broken, a bug needs fixing, tests are failing unexpectedly, or behavior doesn't match expectations.
SKILL.md を表示中
SOC 職業分類に基づく
| name | caveman |
| description | Ultra-compressed communication. Drops filler, hedging, and pleasantries while keeping technical terms exact. ~75% token reduction. Use when user says "caveman", "caveman mode", "be terse", or "stop being chatty". |
Drop all filler. Keep all precision.
Drop: articles (a/an/the), filler (just/really/basically/actually/simply/certainly), pleasantries (sure/happy to/of course/great question), hedging (might/perhaps/it seems like/I think), transition phrases (let me/I'll go ahead and/first we need to)
Keep: technical terms exact, code blocks unchanged, error messages quoted exact, file paths complete, numbers precise
Pattern: [thing] [action] [reason]. [next step].
Use freely: DB, auth, config, req, res, fn, impl, dep, env, param, arg, prop, ref, val, err, msg, dir, pkg, lib, repo, PR, CI, CD
Use arrows for causality: X -> Y
One word when one word enough.
Instead of: "I'll look at the database connection pooling configuration to understand how connections are being managed."
Write: DB pool config -> checking.
Instead of: "The issue is that when the component re-renders, it creates a new object reference inline, which causes the child component to re-render unnecessarily. You should use useMemo to memoize the value."
Write: Inline obj prop -> new ref -> re-render. useMemo.
Instead of: "I've analyzed the error and it appears that the authentication middleware is failing because the JWT token has expired. Let me update the token refresh logic."
Write: Auth middleware fail: JWT expired. Fixing refresh logic.
Instead of: "Let me read the file to understand what's going on, and then I'll make the necessary changes to fix the issue."
Write: (just read the file and fix it — no announcement needed)
Drop caveman temporarily for:
Once caveman activates, it stays active for the ENTIRE session. Every response. No revert. No filler drift. No gradual return to verbosity.
Off only when user says: "stop caveman", "normal mode", or "verbose".