home / skills / duc01226 / easyplatform / coding-level

coding-level skill

safe

This skill sets your coding experience level for tailored explanations and output formatting, delivering clearer guidance aligned with your expertise.

npx playbooks add skill duc01226/easyplatform --skill coding-level

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.8 KB

---
name: coding-level
description: "[Utilities] Set coding experience level for tailored explanations"
argument-hint: [0-5]
infer: true
---

Set your coding experience level for tailored explanations and output format.

## Usage

`/coding-level [0-5]`

## Levels

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

## How It Works

1. Set `codingLevel` in `.claude/.ck.json`
2. Guidelines are **automatically injected** on every session start
3. No manual activation needed - it just works!

## Example

Set level 1 in `.claude/.ck.json`:
```json
{
  "codingLevel": 1,
  ...
}
```

Next session, Claude will automatically:
- Explain concepts and techniques clearly
- Always explain WHY, not just HOW
- Point out common mistakes
- Add "Key Takeaways" after implementations

## Optional: Manual Output Styles

For finer control, you can also use `/output-style` with these styles:
- `coding-level-0-eli5`
- `coding-level-1-junior`
- `coding-level-2-mid`
- `coding-level-3-senior`
- `coding-level-4-lead`
- `coding-level-5-god`

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill sets a developer's coding experience level to tailor explanations, examples, and output styles. It makes responses match the user’s background, from absolute beginner to expert, so guidance is neither too basic nor too dense. Default behavior targets an expert-level concise mode.

How this skill works

The skill stores a numeric codingLevel (0–5) in a local config file and injects matching guidance automatically at session start. Once set, every response adapts tone, detail, and format (e.g., step-by-step analogies for beginners or trade-off analysis for seniors). Optional manual output-style commands provide per-response overrides.

When to use it

Onboard a new developer or learner to receive explanations at the right depth.
Produce tutorials, code reviews, or design explanations that match team seniority.
Create training materials or interview questions targeted to a specific level.
Adjust verbosity and focus when switching between mentoring and decision-making contexts.
Ensure consistency of guidance across sessions and collaborators.

Best practices

Choose the lowest level that a typical recipient understands and increase only when needed.
Set the level in the config file for consistent behavior across sessions rather than toggling every reply.
Combine the coding level with explicit goals (what to learn or build) to shape practical outputs.
Use manual output-style overrides for one-off deviations without changing persistent settings.
Keep sessions focused and ask for clarifying constraints (language, frameworks, policies) to refine recommendations.

Example use cases

A bootcamp instructor sets level 0 to get ELI5 explanations and analogies for novices.
A junior dev requests level 1 so answers explain WHY design choices matter, not just HOW to implement them.
A mid-level engineer uses level 2 to receive pattern recommendations and system-level trade-offs.
A tech lead sets level 4 when assessing risk, business impact, and migration strategy for an architecture change.
Default sessions use level 5 for compact, highly efficient expert outputs and quick decision support.

FAQ

How do I change the coding level?

Edit the codingLevel value (0–5) in your local .claude/.ck.json config; the change takes effect at the next session start.

Can I override the level per message?

Yes. Use the optional /output-style command with the matching coding-level tag to temporarily override the stored level for a single response.

What does each level emphasize?

Levels progress from simple analogies and step-by-step help (0), through conceptual explanations and common pitfalls (1–2), to architecture, trade-offs, risk, and business impact (3–4), with level 5 providing compact expert outputs.