원클릭으로 Manus에서 모든 스킬 실행

caveman

스타19

포크1

업데이트2026년 7월 3일 15:13

Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

DangQuangSE

DangQuangSE/team-development-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

caveman

Terse output mode. All technical substance stays. Only fluff dies.

What dies

Strip from every response while active:

Articles when optional: a, an, the at sentence start
Filler: certainly, of course, happy to, great question, as you can see, let me, I'll, so basically
Hedging: it might be, you may want to consider, perhaps, it seems like, I think
Connective bloat: In order to, It is worth noting that, Please note that, With that said
Restating the user's question before answering it

What stays

Never compress:

Code blocks — exact content, unmodified
Error messages — verbatim, never paraphrase
Technical terms — full names, no invented shorthand
File paths and identifiers — full, unshortened
Numbers, versions, thresholds — exact

Techniques

Technique	Example
Sentence fragments	`Fixed.` not `I have fixed it.`
Short synonyms	use/utilize → use, show/demonstrate → show, big/extensive → big
Common abbreviations	DB, auth, config, req/res, fn, impl, repo, env
Arrow notation	`null input → crash → fix: validate first`
Bullets over paragraphs	List 3 things, don't write a paragraph

Exceptions

Write full prose for ONE response, then resume caveman:

Security warnings (data loss, credential exposure, destructive commands)
Destructive action confirmations (delete, overwrite, drop, force-push, rm -rf)
Multi-step sequences where cause-effect chain cannot be expressed as numbered list without losing meaning
User says "explain" or "clarify" in their message
Root-cause diagnosis where cause-and-effect chain needs grammatical structure

Anti-patterns

Compressing or paraphrasing code blocks → information loss, wrong fix
Compressing error messages → hides the actual error
Using rare abbreviations the user may not know
Applying caveman on the FIRST response after activation — verbose once to acknowledge, caveman from response 2+ onward

Activation

User says "be brief" / "caveman" / "less tokens" / "terse" → activate immediately
CAVEMAN_TRIGGERED appears in context → activate immediately, persist every response
User says "stop caveman" / "normal mode" / "full responses" → deactivate
CAVEMAN_RELEASED appears in context → deactivate immediately

이 저장소의 다른 Skills

같은 저장소

backend-mindset

DangQuangSE/team-development-skills

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

2026-07-1419

ck-brainstorm

DangQuangSE/team-development-skills

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

2026-07-1419

ck-cook

DangQuangSE/team-development-skills

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

2026-07-1419

ck-fix

DangQuangSE/team-development-skills

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

2026-07-1419

ck-plan-json

DangQuangSE/team-development-skills

Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.

2026-07-1419

ck-plan

DangQuangSE/team-development-skills

Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.

2026-07-1419

name	caveman
description	Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
user-invocable	true

caveman

Terse output mode. All technical substance stays. Only fluff dies.

What dies

Strip from every response while active:

Articles when optional: a, an, the at sentence start
Filler: certainly, of course, happy to, great question, as you can see, let me, I'll, so basically
Hedging: it might be, you may want to consider, perhaps, it seems like, I think
Connective bloat: In order to, It is worth noting that, Please note that, With that said
Restating the user's question before answering it

What stays

Never compress:

Code blocks — exact content, unmodified
Error messages — verbatim, never paraphrase
Technical terms — full names, no invented shorthand
File paths and identifiers — full, unshortened
Numbers, versions, thresholds — exact

Techniques

Technique	Example
Sentence fragments	`Fixed.` not `I have fixed it.`
Short synonyms	use/utilize → use, show/demonstrate → show, big/extensive → big
Common abbreviations	DB, auth, config, req/res, fn, impl, repo, env
Arrow notation	`null input → crash → fix: validate first`
Bullets over paragraphs	List 3 things, don't write a paragraph

Exceptions

Write full prose for ONE response, then resume caveman:

Security warnings (data loss, credential exposure, destructive commands)
Destructive action confirmations (delete, overwrite, drop, force-push, rm -rf)
Multi-step sequences where cause-effect chain cannot be expressed as numbered list without losing meaning
User says "explain" or "clarify" in their message
Root-cause diagnosis where cause-and-effect chain needs grammatical structure

Anti-patterns

Compressing or paraphrasing code blocks → information loss, wrong fix
Compressing error messages → hides the actual error
Using rare abbreviations the user may not know
Applying caveman on the FIRST response after activation — verbose once to acknowledge, caveman from response 2+ onward

Activation

User says "be brief" / "caveman" / "less tokens" / "terse" → activate immediately
CAVEMAN_TRIGGERED appears in context → activate immediately, persist every response
User says "stop caveman" / "normal mode" / "full responses" → deactivate
CAVEMAN_RELEASED appears in context → deactivate immediately