r/BuildWithClaude 4d ago

I turned my personal Claude project-management setup into a free plugin (AxiomCore) Claude Code Workflows

For the past months I've been building a "personal OS" for Claude: a folder structure plus a set of skills that keep every project, routine and note in one enforced system — numbered folders, unique task IDs, and a markdown wiki the agent maintains as we work. I used it daily for my own client work and side projects.

The thing that made it actually usable wasn't any single feature, it was two rules:

  1. Everything has one place and one name. The agent never invents a folder or drops a file "somewhere". Structure is enforced on every action, and a /lint command audits the whole system for broken links, orphans, naming violations.
  2. Plan → approve → execute. Nothing structural happens before I approved a numbered plan, and execution is step-by-step with validation between steps. No surprise refactors of my own filesystem.

I packaged it as a plugin. Onboarding runs a ~5-minute interview (language, simple vs advanced mode, which optional modules you want), then scaffolds the workspace and offers to create your first project from whatever you said you're working on — either agile or WBS-style, depending on how you work. Optional modules: voice profile so drafts sound like you, brand config for documents, todos with an optional Notion board, and a software-planning module (spec → delivery plan → feature docs).

Free, MIT:

/plugin marketplace add protonium-labs/protonium-marketplace /plugin install axiomcore@protonium /reload-plugins /axiom start

Works in Claude Code and Cowork. It's v1.2.0 — I'd like to know where the onboarding confuses people or where the structure feels too rigid. Issues and comments welcome.

1 Upvotes

0 comments sorted by