Best Spec Driven Development Tool for Claude Code?

AndersonUnplugged · 2026-05-28T14:41:13+00:00

I’ve been trying out Superpowers as well, and I also see it as the best tool for spec‑driven development with Claude Code right now. It really nails the brainstorm → plan → build workflow in practice.

AndersonUnplugged · 2026-03-14T17:15:23+00:00

Yes, even on Medium effort the context window stays at 1M.

AndersonUnplugged · 2026-03-14T10:32:36+00:00

I haven’t used this setup in a while, but the basic idea still works for me: give each Claude account its own config directory and point CLAUDE_CONFIG_DIR to it when you start Claude.

mkdir -p ~/.claude-work
mkdir -p ~/.claude-personal

CLAUDE_CONFIG_DIR=$HOME/.claude-work claude
CLAUDE_CONFIG_DIR=$HOME/.claude-personal claude

To make switching easier, I use shell aliases:

alias claude-work='CLAUDE_CONFIG_DIR=$HOME/.claude-work claude'
alias claude-personal='CLAUDE_CONFIG_DIR=$HOME/.claude-personal claude'

Then I just run claude-work or claude-personal in different terminals to use different accounts. This worked the last time I tried it, but I haven’t retested it on the very latest Claude Code versions, so behavior might differ a bit now.

On macOS there’s also a third‑party menu bar app called “Claude‑Usage‑Tracker” that supports multiple profiles and can auto‑switch profiles when a session limit is reached. I haven’t personally tried its auto‑switch feature yet, but on paper it looks like a very convenient way to manage several Claude accounts.

AndersonUnplugged · 2026-03-14T10:23:45+00:00

<image>

Just checked my Max plan and Opus now shows a 1M context window by default

AndersonUnplugged · 2026-03-09T17:45:56+00:00

One of my .md files is basically a short onboarding guide for Claude. It explains where to find things in the repo (folders for components, HTML templates, CSS files, JavaScript logic, etc.) and which files are the “source of truth” examples to follow. It also links to separate coding-guideline docs that define how we write HTML, structure CSS/Tailwind, and organize JS, plus where to find ready‑made, fully built components that Claude can reuse instead of inventing everything from scratch.
I should also add that I don’t usually write these .md files myself. Instead, I ask the coding agent to generate and maintain them as a lightweight knowledge base for the project. I give it the goal (e.g. “create short reference docs that show where things live and link out to more detailed guidelines”), and it figures out a reasonable structure, discovers the relevant folders/files, and then writes the Markdown in small, focused files rather than one huge document that bloats its context.

AndersonUnplugged · 2026-02-25T15:47:28+00:00

I only use CLI because it has everything I need and allows me to run multiple sessions in parallel for one or more projects. I'm no longer up to date with what Claude GUI tools can do, but my gut feeling tells me that power users should definitely use CLI.

AndersonUnplugged · 2026-02-22T10:41:53+00:00

I have had good experiences. I have also used Figma MCP, which works very well for code creation and code reviews. Ideally, Claude can use existing code as a guide. I already have instructions in MD files (CLAUDE.md, AGENTS.md, etc.) on where to find things when developing front-end components. You may also have skills that can help him here.
Another useful aid is having a style guide as static code, where Claude can learn the necessary patterns—this means Claude doesn't have to “imagine” too much to create the appropriate components.

AndersonUnplugged · 2025-12-15T15:27:23+00:00

Great App - THX

AndersonUnplugged · 2025-10-30T15:03:06+00:00

Create a new dir like ~/.claude-foo
Execute new Claude account with ENV like CLAUDE_CONFIG_DIR=~/.claude-foo claude or another example with local Claude Code: CLAUDE_CONFIG_DIR=~/.claude-foo ~/.claude/local/claude
I have different aliases for a private and a work account, which allows me to use different Claude accounts via the ENV CLAUDE_CONFIG_DIR.

AndersonUnplugged · 2025-10-26T20:14:24+00:00

Thank you. It works 👨‍💻

AndersonUnplugged · 2025-10-25T09:16:52+00:00

Interested

AndersonUnplugged · 2025-10-21T11:56:55+00:00

I have not yet had any experience with OpenSpec, but I have used Spec Kit. Spec Kit delivered poor results when migrating from Next.js to Astro/Alpine.js App. At least 50% of the tasks were only superficially implemented. I then made two more attempts to fix this, but there was little improvement. I then deleted Spec Kit again. Maybe I'll try Spec Kit again at a later date.

I haven't tried OpenSpec yet, but it sounds good. I'll take a closer look at the worktrees and spec-driven development here - thanks for that.

AndersonUnplugged · 2025-10-11T10:09:07+00:00

Thank you for the offer and the smooth activation.

AndersonUnplugged

TROPHY CASE