Files
2026-02-16 14:02:42 +09:00

2.0 KiB
Raw Permalink Blame History

name, description
name description
ck-coding-level Set coding experience level for tailored explanations and output verbosity. Use when adjusting explanation depth, changing response format, or configuring how technical and detailed answers should be.

Coding Level

Sets explanation depth and output format based on developer experience level.

When to Use

  • User wants simpler explanations (junior or beginner)
  • User wants concise, expert-mode output (senior/lead)
  • Adjusting verbosity for a specific session or project

Don't Use When

  • Task has no explanatory component (pure code output)
  • Level is already set and working correctly

Levels

Level Name Style
0 ELI5 Zero coding experience — analogies, no jargon, step-by-step
1 Junior 02 years — concepts explained, WHY not just HOW
2 Mid-Level 35 years — design patterns, system thinking
3 Senior 58 years — trade-offs, business context, architecture
4 Tech Lead 810 years — risk assessment, business impact, strategy
5 God Mode Expert — default behavior, maximum efficiency (default)

Configuration

Set codingLevel in $HOME/.claude/.ck.json:

{
  "codingLevel": 1
}

Guidelines are automatically injected on every session start — no manual activation needed.

Per-Level Behavior

Level 01: Explain all concepts, add analogies, always explain WHY, point out common mistakes, add "Key Takeaways" section after implementations.

Level 23: Discuss design patterns, trade-offs, architectural implications. Skip basic explanations.

Level 4: Focus on risk, business impact, team/strategic implications. Minimal implementation detail.

Level 5 (default): Maximum efficiency. No hand-holding. Concise, expert-to-expert communication.

Manual Output Style Override

For one-off adjustments without changing config:

  • coding-level-0-eli5
  • coding-level-1-junior
  • coding-level-2-mid
  • coding-level-3-senior
  • coding-level-4-lead
  • coding-level-5-god