القائمة
Set coding experience level for tailored output. Use for adjusting explanation depth, code complexity, and response format to user expertise.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ck:coding-level |
| description | Set coding experience level for tailored output. Use for adjusting explanation depth, code complexity, and response format to user expertise. |
| user-invocable | true |
| when_to_use | Invoke when response depth should match user expertise. |
| category | utilities |
| keywords | ["experience","level","explanation","format"] |
| argument-hint | [0-5] |
| metadata | {"author":"claudekit","version":"1.0.0"} |
Set your coding experience level for tailored explanations and output format.
/ck:coding-level [0-5]
| 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) |
codingLevel in .claude/.ck.jsonSet level 1 in .claude/.ck.json:
{
"codingLevel": 1,
...
}
Next session, Claude will automatically:
For finer control, you can also use /output-style with these styles:
coding-level-0-eli5coding-level-1-juniorcoding-level-2-midcoding-level-3-seniorcoding-level-4-leadcoding-level-5-godAutomate browsers and apps with agent-browser. Use for testing, screenshots, forms, scraping, Browserbase/cloud browsers, and Electron when real Chrome cookies are not required.
Add authentication with Better Auth (TypeScript). Use for email/password, OAuth providers (Google, GitHub), 2FA/MFA, passkeys/WebAuthn, sessions, RBAC, rate limiting.
Target a real Google Chrome profile for browser automation through Chrome DevTools MCP or claude-in-chrome. Provides a chrome-profile CLI, profile discovery, bridge diagnostics, setup playbooks, and the URL-anchor workflow for selecting the correct profile tab.
Review code quality with evidence-based rigor. Supports input modes: pending changes, PR number, commit hash, and codebase scan. Focuses on bugs, regressions, maintainability, reliability, and verification gaps.
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation, log analysis, CI/CD failures, database diagnostics, system investigation.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.