claude-code-dev
Skill2.1k starsChanged 7 months agoMITView on GitHub
How to develop, modify, and extend the Claude Code codebase following its established programming style, patterns, and conventions. Use this skill whenever working on the claude-code source — adding tools, commands, utils, components, types, hooks, services, or fixing bugs. Also use when the user asks about claude-code architecture, coding standards, file organization, or wants to understand how the codebase works. This skill ensures all contributions match the existing codebase style exactly.
4 other projects use a version of this.
Trending
Quiet since April.thin dataabout the whole repository
Most recently taken up by
- chatgptprojects/claude-codeword for word, first seen Oct 8, 2026
- Leanmcp/gateway-skillsword for word, first seen Oct 8, 2026
- Leanmcp/superview.shword for word, first seen Apr 29, 2026
- acavigneaux/claude-code-devtheir own version, first seen Feb 6, 2026
Who's talking about chatgptprojects/clear-code
- karthink/gptel-agent“The Claude Code source code has leaked, probably bringing a massive boost to open source projects such as …”GitHub · Mar 31, 2026 · 1 reactions
- ProSkillsMD/proskills“[SUBMISSION] clear-code”GitHub · Apr 20, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions4 projects use a version of this.
Word for word · 3
- Leanmcp/superview.sh★ 2.1k100% same
- chatgptprojects/claude-code★ 2.1k100% same
- Leanmcp/gateway-skills★ 2.1k100% same
Edited · 0
None found.
Wrote their own version · 1
- acavigneaux/claude-code-dev★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- analyze-exportsSkill
- code-explanationSkill
- fireworks-inferenceSkill
- godot-city-game-3dSkill
- ios-bootstrap-testflightSkill
- leanmcp-builderSkill
- mcp-apps-builderSkill
- mcp-builderSkill
- posthog-adblock-bypassSkill
- publicity-distributionSkill
- research-observabilitySkill
- research-paper-integritySkill
- security-reproSkill
- tinker-training-inferenceSkill
- translate-explanationSkill
- vuln-reproSkill
The file
Files
Claude Code Development Style Guide
This skill captures the programming style, patterns, and conventions used in the Claude Code codebase (@anthropic-ai/claude-code). Each topic below links to a dedicated deep-dive document with comprehensive examples and rules extracted from the actual source.
Summary
Claude Code is an ESM TypeScript Node.js CLI application using Ink (React for terminals) for its UI, esbuild for transpilation, and Bun internally for feature flags and dead code elimination. Key stack: TypeScript, Zod v4, lodash-es, React/Ink, esbuild.
Detailed Guides (Resource Files)
Each topic below is covered in depth in its own resource file within this skill's directory. Read the relevant file before working on that area of the codebase.
| # | Topic | File | Summary |
| 01 | Project Overview | 01-project-overview.md | Tech stack, build system, runtime environment, key dependencies |
| 02 | Directory Structure | 02-directory-structure.md | Full src/ layout, file organization patterns, where things go |
| 03 | Import Conventions | 03-import-conventions.md | .js extensions, import type, lodash cherry-picks, feature flags, cycle breaking |
| 04 | Naming Conventions | 04-naming-conventions.md | camelCase/PascalCase/UPPER_SNAKE rules, file naming, safety names |
| 05 | TypeScript Patterns | 05-typescript-patterns.md | Branded types, discriminated unions, as const, satisfies, Zod schemas, generics |
| 06 | Commenting Style | 06-commenting-style.md | JSDoc, why-not-what philosophy, PR references, section headers, lint suppression |
| 07 | Error Handling | 07-error-handling.md | Custom error classes, utility functions, graceful degradation, catch conventions |
| 08 | Function Patterns | 08-function-patterns.md | buildTool() factory, memoize, async generators, guard clauses, fire-and-forget |
| 09 | Tool Architecture | 09-tool-architecture.md | Tool directory structure, buildTool() API, schemas, permissions, UI rendering |
| 10 | Command Architecture | 10-command-architecture.md | Command types, index.ts pattern, lazy loading, registration |
| 11 | State Management | 11-state-management.md | Module-level state, getter/setter, AppState threading, cleanup registry |
| 12 | Testing Conventions | 12-testing-conventions.md | Reset helpers, NODE_ENV guards, test-only exports, deterministic sorting |
| 13 | Formatting Rules | 13-formatting-rules.md | No semicolons, single quotes, trailing commas, indentation, expression style |
| 14 | Quick References | 14-quick-references.md | Step-by-step checklists for adding tools, commands, utils, and types |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.