Claude Code Plugin

Your projects remember themselves.

An Obsidian vault maintained by Claude Code. Project status, decisions, infrastructure, and cross-project relationships -- tracked automatically, browsed visually.

Project context is scattered and stale.

Status lives in your head. Decisions live in Slack threads you can't find. Infrastructure details are spread across READMEs that nobody updates. Every new session starts with "where was I?"

knowledge-base keeps an Obsidian vault updated automatically after work sessions. Claude writes the notes. You browse them in Obsidian with graph view, tags, and search. Git history is the timeline.

/knowledge-base:setup

Vault initialized at ~/vault

Created Projects/, Projects/meta/

 

deploy gummymine to production

... deploying ...

 

// vault auto-updates after session

gummymine.md: "Where I'm at" updated

deploy.md facet updated

How it works.

1

Work normally

Build features, fix bugs, deploy. After meaningful work, Claude updates the vault automatically. Each project gets its own note with a "Where I'm at" section that stays current.

2

Structure accumulates

Wikilinks connect related projects. Tags slice by status and needs. Facet notes track specific concerns like Stripe, marketing, or deployment. The graph grows organically.

3

Browse in Obsidian

Open the vault in Obsidian. Graph view shows project relationships. Tag pane filters by status. Full-text search finds anything. Git log shows the timeline of every change.

Claude writes. Obsidian reads. Git tracks. No extra tools, no syncing, no maintenance.

Per-project notes

Each project gets a directory under Projects/ with a main note and optional facet notes (marketing.md, stripe.md, deploy.md). The main note always has a current "Where I'm at" section.

Wikilinks for graph view

Related projects are connected with [[wikilinks]]. Dependencies, shared infrastructure, upstream/downstream relationships -- all visible in Obsidian's graph view.

Tags for vertical slicing

Frontmatter tags like status/active, status/paused, needs/marketing, and type/plugin let you filter the vault by any dimension. See all paused projects or everything that needs docs.

Git as the timeline

Every vault update is a git commit with a descriptive message. The commit log is your changelog -- when things changed, what was decided, how projects evolved over time.

Setup skill

Run /knowledge-base:setup to initialize the vault. Detects if Obsidian is installed, creates the directory structure, and sets up the git repo. One command, ready to go.

Cross-project awareness

Meta notes in Projects/meta/ track shared concerns: infrastructure, accounts, services. When a decision affects multiple projects, it lives in one place with links to each.

Install

Requires Claude Code. Obsidian recommended for browsing the vault.

1

Add the marketplace

claude plugin marketplace add softwaresoftware-dev/softwaresoftware-plugins

Run in your terminal.

2

Install the installer

claude plugin install softwaresoftware@softwaresoftware-plugins

Run in your terminal.

3

Launch Claude Code

claude

Start a new session so the installer is available.

4

Install knowledge-base + dependencies

/softwaresoftware:install knowledge-base

Run inside Claude Code. Run /reload-plugins when done.

5

Initialize the vault

/knowledge-base:setup

Run inside Claude Code after reloading plugins. Detects Obsidian and creates vault structure.