Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (claude-dev-stack) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

🧠 Claude Dev Stack

One command to set up a complete AI-powered development workflow with Claude Code.

Solves the #1 problem: Claude Code forgets everything between sessions.

npx claude-dev-stack

Works on Mac, Linux, and Windows (WSL).

What It Does

An interactive wizard that installs and configures everything you need:

Component	What it does
Knowledge Vault	Obsidian-compatible markdown vault — project context, session logs, ADRs, docs
Session Hooks	Auto-loads context at session start, auto-logs at session end
GSD (Get Shit Done)	Spec-driven development with subagent orchestration
Obsidian Skills	Official skills from Obsidian's CEO — vault file format support
Custom Skills	Session manager, project switcher, auto-router, dev-research
Deep Research	Structured web research from terminal — outlines, investigation, reports
NotebookLM	Docs-grounded research via Google NotebookLM
Plugins	98+ Claude Code plugins with use-case based recommendations
MCP Servers	18 pre-configured servers (GitHub, Postgres, Playwright, etc.)

How It Works

You just talk to Claude Code naturally:

You say	Claude does
"hi, let's continue"	Loads project context + last session TODO
"build user auth with email"	GSD plans → executes → commits
"research best CMS options"	Deep Research → structured report
"switch to my-other-project"	Saves context, loads other project
"done for today"	Creates session log, updates context

No slash commands needed. Skills activate automatically. Hooks guarantee session logging.

Quick Start

1. Install

npx claude-dev-stack

The wizard will guide you through:

Language preferences
Project directory scanning
Component selection (multiselect with arrows)
Plugin installation (with recommendations for your stack)
Vault creation and CLAUDE.md installation

2. Fill in context.md

This is the most important step. Open each project's context.md and describe:

What the project does
Tech stack
Architecture
Current state

# Let Claude help you fill it in:
cd ~/Projects/my-project && claude
> "help me fill in context.md for this project"

3. Open vault in Obsidian

Download Obsidian (free)
File → Open Vault → ~/vault
Browse projects, session logs, and decisions visually

4. Start working

cd ~/Projects/my-project && claude
> "let's continue"   # loads context automatically
# ... work ...
> "done for today"    # logs session automatically

CLI Commands

Setup

claude-dev-stack                        # Full interactive setup wizard

Projects

claude-dev-stack projects               # List projects with status
claude-dev-stack projects add           # Add a project to vault
claude-dev-stack projects remove        # Remove project from vault

Documents

claude-dev-stack docs                   # List documents per project
claude-dev-stack docs add               # Add docs from files, Notion export, or paste

Import from Notion:

In Notion: click ••• → Export → Markdown & CSV
Unzip the downloaded file
claude-dev-stack docs add → select project → Notion export → point to folder

Skills

claude-dev-stack skills                 # List installed skills
claude-dev-stack skills install         # Install from catalog or custom Git URL
claude-dev-stack skills remove          # Remove installed skills

Plugins

claude-dev-stack plugins                # List installed plugins
claude-dev-stack plugins install        # Install via preset or browse all 98+
claude-dev-stack plugins presets        # Install curated set (fullstack, frontend, etc.)
claude-dev-stack plugins marketplaces   # Add third-party marketplaces (19 available)

Presets: fullstack, frontend, backend, mobile, data, devops — each pre-selects relevant plugins.

MCP Servers

claude-dev-stack mcp                    # List configured MCP servers
claude-dev-stack mcp install            # Install from catalog (18 servers)
claude-dev-stack mcp remove             # Remove MCP servers

Available: filesystem, memory, playwright, postgres, sqlite, github, gitlab, slack, google-drive, sentry, linear, brave-search, and more.

Templates

claude-dev-stack new                    # Generate context.md from stack template

Stacks: Next.js, React+Vite, FastAPI, Express, Rails, Django, Flutter, Go, Blank.

Import & Export

claude-dev-stack import                 # Import AI configs from a project directory

Supports: CLAUDE.md, .cursorrules, .windsurfrules, copilot-instructions.md, .clinerules, .aider.conf.yml.

claude-dev-stack export                 # Export vault as .tar.gz
claude-dev-stack sync init              # Initialize vault as git repo
claude-dev-stack sync push              # Commit and push vault
claude-dev-stack sync pull              # Pull latest vault from remote
claude-dev-stack sync status            # Show uncommitted changes

Maintenance

claude-dev-stack doctor                 # Health check (prereqs, vault, skills, plugins)
claude-dev-stack update                 # Update all components (skills, hooks, GSD, CLI)
claude-dev-stack stats                  # Analytics dashboard
claude-dev-stack help                   # Show all commands
claude-dev-stack version                # Show version

Vault Structure

~/vault/
├── meta/
│   ├── project-registry.md       # All projects
│   └── session-protocol.md       # Session conventions
├── shared/
│   ├── patterns.md               # Reusable patterns across projects
│   └── infra.md                  # Infrastructure notes
├── research/                     # Deep Research outputs
├── projects/
│   ├── my-project/
│   │   ├── context.md            # ★ Project context (fill this in!)
│   │   ├── sessions/             # Auto-generated session logs
│   │   ├── decisions/            # Architecture Decision Records
│   │   └── docs/                 # Documentation, plans, specs
│   ├── another-project/
│   └── _template/
└── CLAUDE.md.template

What goes where

Folder	Content	Who creates it
`context.md`	Project overview, stack, architecture, current state	You (with Claude's help)
`sessions/`	Session logs: what was done, decisions, TODO	Claude (automatically)
`decisions/`	ADRs: why we chose X over Y	Claude (when architectural decisions are made)
`docs/`	Documentation, Notion exports, plans, specs	You (via `claude-dev-stack docs add`)
`shared/`	Cross-project patterns, infra notes	You or Claude

Automatic Hooks

Two hooks are installed into Claude Code settings to ensure reliability:

Hook	Event	What it does
session-start-context	SessionStart	Loads project context.md + shows outstanding TODOs
session-end-check	Stop	If no session log exists for today → reminds Claude to create one

These work at the Claude Code level — skills can be ignored by Claude, but hooks always fire.

For Teams

Every team member runs:

npx claude-dev-stack

To share vault across the team:

claude-dev-stack sync init    # Initialize vault as git repo
# Add remote, push to shared repo
# Each team member pulls the vault

Updating

When new versions are released with bug fixes and improvements:

npx claude-dev-stack update

This updates:

Builtin skills (session-manager, dev-router, project-switcher)
Hooks (session start/end)
Git-based skills (obsidian, deep-research)
GSD
Claude Code CLI

Requirements

Node.js 18+
Git
Python 3.10+ (optional, for Deep Research and NotebookLM)
Claude Code CLI (for plugins and MCP)

Missing something? The wizard shows install commands:

✘ node — not found
  ℹ Install: brew install node

Credits

Built on top of:

GSD (Get Shit Done) by TÂCHES
Obsidian Skills by kepano
Deep Research Skills by Weizhena
notebooklm-py by teng-lin

Support

If this saves you time, consider buying me a coffee:

License

MIT