[zwanski-start]

Closes #87

What changed

Docs only (README.md):

• New Claude Code Extensions (.claude/ folder) section that answers the question in the issue:
  • You don't need to copy or link anything into ~/.claude to use AutoForge.
  • What gets used automatically: the templates, create-spec / expand-project (used by the Web UI chats), and playwright-cli (copied into every generated project by prompts.py).
  • What you get when you run claude inside the AutoForge checkout (project-level commands, skills and agents).
  • How to use gsd-to-autoforge-spec (or any other skill or agent) in an existing project: symlink or copy it into ~/.claude/skills/ or <project>/.claude/skills/, including the path for npm installs ($(npm root -g)/autoforge-ai/.claude/...) and a note for Windows. Then run /gsd:map-codebase and "convert to autoforge".
• Updated the .claude/ entry in the Project Structure tree so it lists agents/, commands/, skills/ and templates/, and links to the new section.

Verification

• Checked each claim against the code: prompts.py (templates and the playwright-cli copy), server/services/spec_chat_session.py / expand_chat_session.py (they load .claude/commands/*.md from the AutoForge root), and package.json files (.claude/commands, .claude/skills and .claude/templates ship in the npm package; .claude/agents doesn't).
• The UI labels quoted ("Create with Claude", "Expand project with AI") match the strings in ui/src.
• The gsd-to-autoforge-spec skill only uses paths relative to the current folder (.planning/codebase, .autoforge/prompts), so copying or linking it on its own works.

Assumptions

• I recommended copying or symlinking into ~/.claude/skills rather than --add-dir, because that's the documented, reliable way to load a personal skill.
• No code changes; nothing is installed into ~/.claude automatically, because writing to a user's global Claude config without asking seemed too intrusive.
• The branch was pushed to the zwanski-start fork because the token can't push to AutoForgeAI/autoforge directly.

🤖 Generated with Claude Code

[zwanski-start]

🔍 QA report: ✅ Passed

Tester: Dennis (cubefarm agent, in a fresh session) · Round: 1 · Author: Barbara

Docs-only PR that adds a 'Claude Code Extensions (.claude/ folder)' section to README.md and updates the .claude/ entry in the project tree. It answers issue #87: users don't need to copy anything into ~/.claude to use AutoForge; it lists what is used automatically, and it shows how to symlink or copy the gsd-to-autoforge-spec skill into ~/.claude/skills or a project's .claude/skills. Every factual claim checked out against the code (prompts.py, the spec and expand chat sessions, package.json files and .npmignore, the UI strings, the skill's relative paths). One minor nit, not blocking: the closing sentence suggests agents can be copied into ~/.claude/agents, but .claude/agents isn't shipped in the npm package, so that only works from a git checkout.

	Check	Details
✅	Issue #87 question answered (do I need to put .claude items into ~/.claude?)	The new section says no for normal AutoForge use. It explains which items are used automatically, which are only available when claude is run in the AutoForge folder, and gives step-by-step symlink/copy instructions for using gsd-to-autoforge-spec in an existing project, followed by /gsd:map-codebase and 'convert to autoforge'.
✅	Templates claim	prompts.py TEMPLATES_DIR = .claude/templates; scaffold_project_prompts copies them into the project prompts dir (.autoforge/prompts) and is called from start.py and server/routers/projects.py.
✅	playwright-cli copied into every project	prompts.py copies .claude/skills/playwright-cli into /.claude/skills/playwright-cli.
✅	create-spec / expand-project used by Web UI chats	spec_chat_session.py:86 loads ROOT_DIR/.claude/commands/create-spec.md; expand_chat_session.py:104 loads expand-project.md. The UI strings 'Create with Claude' and 'Expand project with AI' exist in ui/src.
✅	Listed commands, skills and agents match .claude/ contents	find .claude shows 6 commands, 3 skills and 3 agents, exactly as listed in the README.
✅	npm install path claim	npm pack --dry-run includes .claude/skills/gsd-to-autoforge-spec and excludes .claude/agents (package.json files plus .npmignore). The package name autoforge-ai makes the $(npm root -g)/autoforge-ai/... path correct.
✅	Skill works when copied or linked on its own	SKILL.md only references .planning/codebase and .autoforge/prompts relative to the current folder, and its trigger phrases include 'convert to autoforge'.
✅	Accuracy nit: agents for npm installs	Not blocking: the final sentence implies agents can be copied into ~/.claude/agents, but npm installs don't include .claude/agents; it only works from a git checkout.
✅	No code changes / regressions	git diff --stat shows only README.md (+56/-4). No whitespace errors; merges cleanly with origin/master.
⏭️	Browser/UI verification	PR changes no UI or backend code, so no browser run or screenshots were needed.

🧪 Commands run

Command	Result
git diff origin/master...HEAD	Only README.md changed
grep/find checks on prompts.py, server/services/*_chat_session.py, ui/src, .claude/, package.json files	All README claims confirmed
npm pack --dry-run	gsd-to-autoforge-spec skill included; .claude/agents excluded
ruff check .	All checks passed!
venv/bin/python test_security.py	ALL TESTS PASSED
git diff --check origin/master...HEAD && git merge-tree --write-tree origin/master HEAD	No whitespace issues; merges cleanly

No browser screenshots were taken in this round.

_{Posted by cubefarm · merges automatically once GitHub's checks pass}