メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Test-driven development with vertical slices. Enforces behavior-focused tests through public interfaces, one red-green-refactor cycle at a time. Use when writing tests, adding test coverage, or building features test-first.
Convert markdown to portable, shareable HTML documents with syntax highlighting and optional tabbed navigation. Use when users say "publish", "make HTML", "make this shareable", "create a document for the team", or want to share output with non-technical audiences.
Generates publication-quality illustrations using a 5-agent pipeline inspired by PaperBanana (academic illustration framework). Orchestrates specialized agents: Retriever, Planner, Stylist, Visualizer, and Critic. Use when users need high-quality, iterative image generation with style consistency and quality review.
| 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".
