vibe-coding-flow

Reusable Claude Code backbone: CLAUDE.md + slash commands that drive my vibe coding workflow. Stack-agnostic — drop it into any project and fill in the blanks.

What's here

• .claude/CLAUDE.md — Project Config (placeholders) + workflow, response style, file naming, versioning rule.
• .claude/commands/ — 9 core slash commands:
  • Workflow: exploration-phase → create-plan → execute-plan → self-review → peer-review → cto-review → update-docs
  • Supporting: create-issue, deploy
• .claude/commands/_optional/ — stack-specific overlays (LangGraph Studio, LangSmith observability). Auto-registered under the _optional: namespace (see below).

How to adopt in a new project

cd /path/to/new-project
cp -r /path/to/vibe-coding-flow/.claude .claude

Then open .claude/CLAUDE.md and fill in the Project Config section. You don't need to fill everything on day one.

Placeholder convention

All project-specific values live in CLAUDE.md — commands read from there rather than hardcoding.

• {{VALUE}} — fill in now.
• {{KNOWN_LATER: short description}} — explicitly deferred; fill when you know.
• To list what's still unfilled at any point:

  grep -rn "{{" .claude/

If a command needs a {{KNOWN_LATER: ...}} value to do its job, it will stop and ask rather than guess.

Optional overlays

Stack-specific commands live in .claude/commands/_optional/ and are auto-registered under the _optional: namespace:

Overlay	Invoke as	Use when
_optional/studio.md	/_optional:studio	project uses LangGraph
_optional/observability.md	/_optional:observability	project uses LangChain + LangSmith

If you want an unqualified alias (e.g. just /studio), move the file up into .claude/commands/. Either way, list the corresponding docs MCP in CLAUDE.md → External docs / MCPs to consult so review commands know to verify against live docs.

Status

Backbone generalized from the original people-analytics2 setup. Ready to adopt in new projects.