Noddle Deck
Back to docs

Concepts

The ~/.claude folder

How synced content reaches your agent

The ~/.claude folder

Claude Code (and several other agent CLIs) read skills and commands from ~/.claude/ on your machine. Noddle Deck writes there too — that's how synced content shows up natively in your agent.

Layout

text
~/.claude/
├── skills/
│   ├── noddle-deck-developer/
│   │   ├── test-driven-development/SKILL.md
│   │   ├── systematic-debugging/SKILL.md
│   │   └── …
│   └── noddle-deck-qa/
│       └── …
└── commands/
    ├── noddle-deck-developer/
    │   ├── commit.md
    │   ├── pr-review.md
    │   └── …
    └── noddle-deck-qa/
        └── …

Each pack lives under its own noddle-deck-<pack-id>/ subfolder.

How agents read it

Claude Code scans ~/.claude/skills/ recursively at session start. Any folder containing a SKILL.md becomes an available skill. The agent uses the description field in the YAML frontmatter to decide when to auto-activate.

Slash commands work similarly: any .md file under ~/.claude/commands/ becomes a /command-name you can invoke.

Why namespacing

Two reasons:

  1. Clean uninstall. Removing a pack is rm -rf ~/.claude/skills/noddle-deck-developer — no risk of touching skills you wrote yourself.
  2. No collisions. Two packs can have a /commit command without overwriting each other.

Editing by hand

You can hand-edit any SKILL.md or command file under ~/.claude/ — but the next noddle-deck pack sync will overwrite that pack's files with the server version. If you want to customize, copy the file into an unnamespaced folder (e.g. ~/.claude/skills/my-custom-tdd/SKILL.md) and the sync will leave it alone.