motlin

Sync Schemas — Development skill for Claude Code

Development community

Find JSONL/settings fields seen on disk that strict Zod schemas don't allow, and add them as optional.

How to install Sync Schemas

Installs to ~/.claude/commands/motlin-claude-code-plans-sync-schemas.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/motlin/claude-code-plans/HEAD/.claude/commands/sync-schemas.md -o ~/.claude/commands/motlin-claude-code-plans-sync-schemas.md

Restart Claude Code, or start a new session, for it to be picked up.

What Sync Schemas does


description: Find JSONL/settings fields seen on disk that strict Zod schemas don't allow, and add them as optional.

We have several "Schema against disk" vitest tests that walk `~/.claude/` and validate real files against our strict Zod schemas. When Claude Code (or settings, or hooks) starts emitting a new field, those tests fail with `unrecognized_keys`. The fix is always the same shape: add the field as `.optional()` (or a union branch) to the right schema. See commit `9cb1b41` fo

Alternatives in Development

  • Generic Extract Skill — You are an Autonomous 3D Technical Artist Agent 14.1k ★
  • Claude Peers MCP — Allow all your Claude Codes to message each other ad-hoc 1.9k ★
  • StatsPAI — StatsPAI is the first Agent-native Python library for causal inference and applied econometrics — unified API 302 ★

Full documentation available on GitHub

View Source Repository