claude-adhd-skills

(No ADHD required!)

A set of Claude Code skills and hooks I use daily as scaffolding for staying organized while developing with AI agents. The key pieces are time awareness (so Claude knows when to tell me to stop), Obsidian integration (so I can store research and reconstruct what I was doing yesterday), and a nudge system (so promises to "wrap up in 30 minutes" actually stick).

Obsidian is central to the workflow. It's where daily logs, meeting notes, research and ideas land, and because agents can read and write to the vault, it becomes a shared memory between sessions. I can point a new Claude instance at yesterday's journal entry and ask the agent to catch up instead of re-explaining context. Ideas get dumped into notes, marinate, and only the ones that survive get built. obsidian-semantic closes the loop, letting agents search notes by meaning, not just filenames.

What's in the box

Skills

Hooks

CLAUDE.md

A starting point for your own CLAUDE.md. I have found that the following ADHD-specific patterns help me: break suggestions, pacing, focus tracking, and a working relationship that prioritizes asking over assuming.

Installation

1. Copy skills to your Claude Code config

# Clone the repo
git clone https://github.com/ravila4/claude-adhd-skills.git
cd claude-adhd-skills

# Copy skills into your Claude Code skills directory
cp -r skills/* ~/.claude/skills/

# Copy hooks
cp hooks/* ~/.claude/hooks/

2. Wire up the hooks

Copy the hook configuration into your Claude Code settings. The settings file is at ~/.claude/settings.json (global) or ~/.claude/settings.local.json (local/private).

See settings.json.example for the full config. The key hooks are:

• UserPromptSubmit: Runs on every prompt. Shows current time and any due nudges.

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "type": "command",
        "command": "echo \"Today is $(date '+%A, %B %d, %Y'). Time: $(date '+%H:%M')\"",
        "timeout": 5000
      },
      {
        "type": "command",
        "command": "python3 ~/.claude/hooks/check_alerts.py",
        "timeout": 5000
      }
    ]
  }
}

3. Set up your CLAUDE.md

Copy CLAUDE.md to ~/.claude/CLAUDE.md and fill in the {PLACEHOLDERS}:

cp CLAUDE.md ~/.claude/CLAUDE.md

Edit the file and replace:

• {YOUR_NAME}: your name
• {YOUR_ROLE}: your job title or role
• {WHAT_YOU_DO}: brief description of your work
• {YOUR_PLATFORM}: your machine/OS (e.g., "MacBook Pro, macOS")
• {YOUR_WORK_DOMAIN}: your work domain (e.g., "web development", "data engineering")

4. Customize the Obsidian vault skill

The obsidian-vault skill needs to know your vault path. Edit ~/.claude/skills/obsidian-vault/SKILL.md and add your vault path to the description:

# Before:
description: Manage Obsidian vault operations. Handles markdown formatting...
# After:
description: Manage Obsidian vault operations for my vault at ~/path/to/your/vault. Handles markdown formatting...

Then customize references/vault_structure.md to match your actual folder hierarchy. The default is minimal (Programming, Projects, Daily Log, Templates). Add your own topic folders.

5. Customize tags

Both the obsidian-vault and daily-journal skills use tags. Look for <!-- Add your own ... --> comments in the reference files and add tags relevant to your work.

Customization

Adding domain-specific knowledge

The CLAUDE.md has a "Technical Knowledge" section. Add your own domain expertise here: books, frameworks, tools. This shapes how Claude approaches problems with you.

Extending the vault structure

Add folders to vault_structure.md for your own knowledge domains. The skill uses this as a decision tree for where to place notes.

Custom tags

Tags live in vault_structure.md and markdown_formatting.md. Add your domain-specific tags to the taxonomy.

Requirements

• Claude Code CLI
• Python 3.10+
• Obsidian (for the vault and journal skills)
• SQLite3 (usually pre-installed)
• obsidian-semantic (optional, for semantic search in the obsidian-vault skill)

License

MIT