Claude Code Schema — Development skill for Claude Code
Machine-readable, versioned schema of Claude Code's configuration surface — settings, env vars, CLI flags, and keybindings, auto-generated per release.
How to install Claude Code Schema
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open amitray007/claude-code-schema and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Claude Code Schema does
Machine-readable, versioned schema of Claude Code's configuration surface — settings, env vars, CLI flags, and keybindings, auto-generated per release.
Alternatives in Development
- Define Schema — Renamed → /portaljs-define-schema 2.3k ★
- /install-hook - Install Generated Hook To Settings — Install a generated hook to Claude Code settings (user-level or project-level) 618 ★
- Phistory — Phistory automatically archives versioned system prompt snapshots from agent CLIs like Claude Code, Codex, Ope 560 ★
README
claude-code-schema
A machine-readable, versioned description of selected **Claude Code configuration interfaces**: validation schemas for `settings.json` and `keybindings.json`, an environment-map schema, and catalogs for CLI flags and default keybindings.
It is purpose-built for Claude Code and **auto-maintained**: keyed on the actual npm release, grounded in first-party sources, and independently checked against the integrity-verified release binary. SchemaStore is a benchmark, not a generation dependency.
**Status:** production generator, validation suite, release discovery, review workflow, and publication staging are implemented. [`experiments/`](experiments/) retains the four source-strategy proofs that established the production design.
Release files
Start with `settings.schema.json` for `settings.json`, or `environment.schema.json` for environment variables. Both files are self-contained; the settings schema bundles the environment schema for its `env` field.
| File | Contains |
|---|---|
catalog.json |
Entry point and file guide |
settings.schema.json |
settings.json keys and validation |
settings.catalog.json |
Settings source and runtime evidence |
environment.schema.json |
Environment-variable names and validation |
environment.catalog.json |
Environment source and binary evidence |
cli.catalog.json |
CLI commands, arguments, and options |
global-config.schema.json |
~/.claude.json validation |
keybindings.schema.json |
~/.claude/keybindings.json validation |
keybindings.compat.schema.json |
More permissive keybinding validation |
Related Skills
Claudecode Deepseek Stack
Replace Anthropic Claude Code 200/mo billing with DeepSeek V4 for ~7/mo. Two env vars, no third-party tool. Li
Env Check
Validate local development environment setup. Checks Python version, dependencies, env vars, config files, and
n8n Env
View, set, or validate env vars for a project
Install MCP
Instala MCP server em .mcp.json do projeto desde a lista curada ou URL custom. Configura permissões e env vars
Claude Code Profiles
Manage multiple Claude Code profiles: switch accounts, providers, and env vars with one command
Add MCP Server
Add an MCP server to the current project the safe way — pick the transport and scope, wire secrets through env
Related Agents
Light Security ClaudeSettingsAudit
Audit Claude Code config files (settings.json, settings.local.json, .mcp.json) for unsafe or malicious content
Deployment Validator
Pre-deploy gate: env vars, secrets, flags, build, tests, rollback readiness. Use before deploying to staging o
Docs Auditor
Audits Forge documentation for drift against the code. Checks that README counts, ARCHITECTURE hot paths, SETU