Claude Code integration

Kept can manage Claude Code project assets — skills, memory, and templates — across all your projects from one place.

What it manages

For each Claude Code project Kept finds on your machine, you get a unified view of:

  • .claude/ skills — the skill files that customize how Claude Code behaves in that project
  • .claude/CLAUDE.md and ~/.claude/CLAUDE.md — project-scoped and global memory
  • .claude/settings.json — local Claude Code configuration
  • Templates — shareable skill/memory templates you've defined

Why this exists

If you use Claude Code across more than two or three projects, you accumulate skills and memory snippets that you want to reuse. Maybe you've written a great code-review.md skill in one project; you want to copy it to another. Maybe your global memory has gotten unwieldy and you want to see it next to a project's local memory to refactor.

Manually navigating .claude/skills/, .claude/CLAUDE.md, etc. across many directories is tedious. Kept gives you a project switcher and a diff view.

Getting started

Settings → Claude Code → Scan projects. Kept walks the directories you've configured (default: ~/projects, ~/code, ~/work — configurable) and lists every Claude Code project it finds (anything with a .claude/ directory).

Each project shows up in the sidebar with:

  • Skill count
  • Memory file count (CLAUDE.md, plus any custom memory files)
  • Template count

Click a project to open its assets.

Operations

Edit a skill

Open the skill file. The desktop app's editor has markdown rendering, syntax highlighting for code blocks, and a save indicator. Saving writes the file back to disk in place — no Kept-specific format, no migration step.

Diff between projects

Pick two projects from the project list. Kept shows a side-by-side diff of their skills and memory files. Useful for "what does my code-review skill look like in project A vs project B?"

Copy a skill to another project

Right-click a skill → Copy to project → pick the destination. Kept writes the file to the target project's .claude/skills/ directory and you're done.

Templates

If you find yourself copying the same skill into many projects, save it as a template:

Skill → Save as template. The template is stored in Kept's own config (under ~/.kept/claude-templates/) and accessible from any project. Apply a template to a project to drop the skill in.

Global memory

Your global ~/.claude/CLAUDE.md is treated as a project-equivalent — it shows up in the project list as global. Edit it like any other project's memory. Useful for keeping the global file shorter (review it next to project files and move things into project scope where they belong).

What Kept doesn't do

  • It doesn't run Claude Code itself. It just edits the files.
  • It doesn't sync to a cloud. Everything stays in your projects' .claude/ directories on disk.
  • It doesn't lock files while you have them open. If you also have your editor open on the same skill, last-write-wins.
  • It doesn't enforce a particular skill format. Whatever Claude Code accepts, Kept accepts.

See also