claude-tweaks

claude-tweaks

A structured workflow system for Claude Code — from idea capture through build, review, and wrap-up.

What this does

Claude Code is powerful but unstructured. claude-tweaks adds a complete development lifecycle: capture ideas, challenge assumptions, decompose into specs, build with quality gates, and learn from what was built. Every finding is explicitly resolved — nothing silently drops.

What's new in v6.3.0 — Human acceptance sign-off (/claude-tweaks:demo)

A new seventh work-record axis (demo:pending / demo:approved / demo:changes-requested) closes the gap between tests passing, spec completion, and an actual human verifying a built feature does what was asked. /claude-tweaks:wrap-up applies demo:pending and writes a Verification Brief (what changed, why, how to verify) while it still has full build context; the new /claude-tweaks:demo skill aggregates every pending record — across parallel threads, regardless of merge timing — and captures your verdict.

What's new in v6.0.0 — The unified work record

Every captured idea, health-skill finding, and human-filed issue is now the same thing: one durable work record (a GitHub issue, or its local-files twin — a plain markdown file), tracked through a single spine instead of the old two-file backlog design and per-artifact frontmatter:

BACKLOG ──/specify shapes──► READY ──human grants──► AUTHORIZED ──/dispatch claims──► BUILDING ──user merges──► CLOSED

with parked (on hold, wakes on a trigger) and not-planned (wontfix/duplicate/absorbed) exits at any stage. Two storage drivers back the same taxonomy — work-backend: github-issues (labels + native Issue Types) or work-backend: local-files (frontmatter on a tracked file) — set once by /init, read identically by every consumer skill. See "Work Records" below and skills/_shared/work-record.md for the full contract.

Human-granted auto:build/auto:merge labels replace the retired tier:approved/tier:fast-track/tier:needs-review three-way split — /claude-tweaks:triage is now the interactive grant gate only. A new skill, /claude-tweaks:dispatch, is the queue consumer: it claims an authorized record's whole file-overlap group and hands it to /flow — the triage dispatch headless subcommand no longer exists.

/claude-tweaks:specify and /claude-tweaks:build//flow now materialize a record reference (#N) into a build-time header + spec-shaped body file rather than requiring a pre-existing numbered spec file — the legacy specs/{n}-*.md path still works as an alias for projects that haven't migrated. /claude-tweaks:tidy and /claude-tweaks:help scan the live record queue directly; the former INBOX scan, Deferred-Work scan, and the separate spec index they used to read are retired.

See "Migrating from 5.x" below if this project still carries pre-6.0 state (live tier:*/status:* labels, specs/backlog/ files, or the old backlog-backend flag name).

What's new in v5.27.0 — Native diagram generation replaces the Diagram Design companion

/claude-tweaks:visualize replaces the external diagram-design companion-plugin integration introduced in v4.7 with a fully native skill — no separate plugin install. It generates self-contained HTML+SVG diagrams (architecture, flowchart, sequence, state, ER, timeline, swimlane, quadrant, nested, tree, org chart, layers, venn, pyramid), themed from the project's own DESIGN.md tokens (or a neutral default skin when Impeccable isn't set up). An optional D2-backed enhanced rendering path handles diagrams-as-code source generation for types with a native D2 construct. The same three soft-hook call sites — /journeys Step 3.6, /specify Step 2.5d, /review Lens 3i-diagram — now suggest invoking it directly, gated by diagram-suggestions: enabled in CLAUDE.md (renamed from diagram-integration:), written by /init Step 11. Diagrams co-locate with what they illustrate (docs/journeys/, docs/plans/) rather than a single central folder; docs/diagrams/ is the fallback for context-free, direct invocations.

What's new in v5.18.0 — shadcn/ui bootstrap + Phase 0 step renumbering

/init gains a new Optional Enhancement step: on a detected frontend project without components.json, it offers to bootstrap shadcn/ui — CLI init, plus wiring shadcn's own first-party MCP server into .mcp.json and installing shadcn's official Skill (skills add shadcn/ui), both of which give Claude Code live project context so it stops guessing at component APIs. Writes a shadcn-integration: enabled | cli-only | disabled flag to CLAUDE.md's ## Design integration section (currently write-only — no other skill reads it yet). See /init Step 12.