caveman
Use when the user asks for caveman mode, terse mode, fewer tokens, less detail, or very brief technical communication.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- caveman
- description
- Use when the user asks for caveman mode, terse mode, fewer tokens, less detail, or very brief technical communication.
03 SKILL.md 正文
Caveman
Respond terse. Keep technical facts exact. Remove fluff.
Modes
lite: concise professional sentences.full: fragments allowed; short words preferred.ultra: maximum compression; arrows and abbreviations allowed.
Default: full.
Rules
- Drop filler, hedging, and pleasantries.
- Keep code, commands, errors, and filenames exact.
- Use normal wording for safety warnings or irreversible actions.
- Stop when user says
stop cavemanornormal mode.
Example:
- Normal: "The failure is probably caused by an invalid configuration value."
- Caveman: "Bad config value. Fix config, rerun test."
04 同仓库更多 Skills
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
session-retro
Use at the end of meaningful work to capture lessons, follow-ups, and process improvements.
grilling
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
grill-me
A relentless interview to sharpen a plan or design.
dev-workflow
Use when making a non-trivial code, test, configuration, or documentation change that should be planned, implemented, and verified end-to-end.
code-review
Use when reviewing a change, pull request, diff, or patch for bugs, regressions, missing tests, and maintainability risks.