claude-dotfiles v1.4.0 — Available Now

If you use Claude Code on more than one machine, you've probably noticed that ~/.claude/CLAUDE.md— your global configuration file — is completely machine-local. Set up a new laptop, and you're starting from scratch. Change your workflow on one machine, and the others don't know about it.

At Spyced Concepts, a developer can be working across a macOS machine, a Linux laptop, and a Windows desktop on the same project. This became a genuine daily friction point. So we built claude-dotfiles.

One-line install

curl -fsSL https://raw.githubusercontent.com/Spyced-Concepts/claude-dotfiles/main/install.sh | bash

That's it. No git knowledge required. The installer handles everything and guides you through the rest with plain-language questions.

What it is

A lightweight, tool-agnostic framework that makes Claude Code understand your work — your notes, your documents, your projects — and carry that understanding across every machine you use.

The core idea: keep your CLAUDE.md in a git repository, symlink it to ~/.claude/CLAUDE.md on every machine, and point Claude at the folders where your work lives. Machine-specific paths stay in a local machine.json file that is never committed.

Knowledge directories

Point Claude at your folders — your research notes, your documents, your project files — and Claude reads them. Every session starts with Claude already knowing your work, rather than starting from scratch.

Tool-agnostic by design: Obsidian vaults, plain folders of notes, VS Code workspace docs, exported Notion pages — anything in markdown.

Built-in commands

v1.4.0 ships six ready-to-use commands: --daily, --todo, --week-review, --journal, --health-check, and --commands. Enable them during setup and use any prefix you like — or none at all.

Not just for developers

Writers, researchers, filmmakers, designers, advertisers — anyone who works with documents on their computer gets a Claude that has read everything and remembers it. The guided first-run setup asks plain-English questions. No JSON editing required.

This is our working version — now a public beta

claude-dotfiles v1 is not a concept or a side project built for show. It is the setup Spyced Concepts runs every day. Every command, every convention, every installer decision has been made because it solved a real problem in a real working environment.

When we decided to release it, we made a deliberate choice not to wait for a "proper" v1.0. The working version was already more useful than anything else out there for this problem, and the best way to make it better is to put it in front of real users. So consider v1 the public beta: fully functional, genuinely useful, and actively being shaped by what people actually need.

We want to hear from both ends of the spectrum. If you are a power user who lives in the terminal and has opinions about how Claude Code should be configured — tell us. If you are someone who has never touched a config file and wants Claude to just understand your work without any friction — that matters just as much, and we want to know where the setup falls short for you.

Feedback, ideas, and bug reports all go to GitHub Issues. If you have a broader idea about the direction of the project, open a Discussion. Everything is considered.

What's next

The public roadmap includes v2.0.0: a Node.js package with a local web UI, removing the last technical barriers for non-developer users.

MIT licence. Contributions welcome. github.com/Spyced-Concepts/claude-dotfiles →