claude-setup 1.0.0

package/templates/init-empty.md

@@ -0,0 +1,53 @@
+<!-- Generated by claude-setup {{VERSION}} on {{DATE}} -->
+<!-- Run /stack-init in Claude Code -->
+
+This is a new project with no source files yet.
+
+Before setting up anything, ask the developer these three questions in ONE message:
+
+1. What are you building? (describe the product in one sentence — not the tech)
+2. Do you have a preferred language or runtime? (completely fine if not)
+3. Are there external services you know you'll use? (fine to say "not sure yet")
+
+Wait for their reply. Then immediately set up the full Claude Code environment.
+
+---
+
+## After they reply
+
+Use exactly what they said. Do not invent requirements they did not mention.
+
+**CLAUDE.md**
+Write it for the product they described. Reference their exact words.
+If they gave no language: write a language-agnostic CLAUDE.md about the product itself.
+
+**.mcp.json**
+Only for services they explicitly mentioned or obviously required for their product type.
+If they said "not sure": do not create this file.
+
+**.claude/settings.json**
+Only if the product type they described has clear patterns that benefit from hooks.
+
+**.claude/skills/**
+Only if the product domain has patterns worth capturing. Empty is fine for a fresh start.
+
+**.github/workflows/**
+Only if they mentioned CI, deployment, or a specific hosting platform.
+
+---
+
+## Rules
+
+- Trace every file you create back to something they said
+- If they were vague: write a minimal setup and tell them:
+  "As the project grows, run npx claude-setup sync — it reads what changed and updates
+  this setup automatically."
+- No generic boilerplate. Two different product descriptions must produce two different setups.
+
+---
+
+## Output
+
+After writing, tell them:
+- What you created and why (one sentence per file)
+- That sync exists: "Run npx claude-setup sync as you add dependencies and code."

package/templates/init.md

@@ -0,0 +1,132 @@
+<!-- Generated by claude-setup {{VERSION}} on {{DATE}} — DO NOT hand-edit -->
+<!-- Run /stack-init in Claude Code -->
+
+You are setting up this project for Claude Code.
+Read everything below. Understand the project yourself. Then act.
+Do not ask clarifying questions — reason from what you see.
+
+---
+
+## Project files
+
+### Configuration and manifest files
+
+{{CONFIG_FILES}}
+
+### Source files sampled
+
+{{SOURCE_FILES}}
+
+{{#if HAS_SKIPPED}}
+### Files skipped (too large or filtered)
+
+{{SKIPPED_LIST}}
+{{/if}}
+
+---
+
+## Existing Claude Code setup — READ EVERY LINE BEFORE TOUCHING ANYTHING
+
+{{#if HAS_CLAUDE_MD}}
+### CLAUDE.md — EXISTS — append only, never rewrite, never remove
+{{CLAUDE_MD_CONTENT}}
+{{else}}
+CLAUDE.md → does not exist (create it)
+{{/if}}
+
+{{#if HAS_MCP_JSON}}
+### .mcp.json — EXISTS — merge only, never remove existing entries
+{{MCP_JSON_CONTENT}}
+{{else}}
+.mcp.json → does not exist (create only if you find evidence of external services)
+{{/if}}
+
+{{#if HAS_SETTINGS}}
+### .claude/settings.json — EXISTS — merge only, never remove existing hooks
+{{SETTINGS_CONTENT}}
+{{else}}
+.claude/settings.json → does not exist (create only if hooks are warranted)
+{{/if}}
+
+Skills installed:    {{SKILLS_LIST}}
+Commands installed:  {{COMMANDS_LIST}}
+Workflows installed: {{WORKFLOWS_LIST}}
+.github/ exists:     {{HAS_GITHUB_DIR}}
+
+---
+
+## Your job
+
+Read the files above. Figure out the project from what you see — language, runtime,
+dependencies, structure, conventions. Do not assume anything not visible in the files.
+
+Then write the Claude Code setup for THIS specific project.
+
+### CLAUDE.md
+
+Always write or update this. It is the most valuable artifact.
+Make it specific: reference actual file paths from the project, actual patterns you saw
+in the source, actual conventions the code follows.
+Generic advice that could apply to any project belongs in documentation, not here.
+
+If it exists: read it fully above first. Add only what is genuinely missing. Never remove.
+
+### .mcp.json
+
+Only if you found evidence of external services in the config files, dependencies,
+or environment template. Evidence means it appears in the files above.
+No evidence = no server. Do not invent services that were not in scope.
+If it exists: add to it. Never remove existing entries. Produce valid JSON.
+
+### .claude/settings.json
+
+Only if hooks genuinely earn their cost for this specific project.
+Every hook adds overhead on every Claude Code action.
+If it exists: add to it. Never remove existing hooks. Never modify existing values.
+
+### .claude/skills/
+
+Only for patterns that recur across this codebase and benefit from automatic loading.
+Use `applies-when` frontmatter so skills load only when relevant — not on every message.
+If a similar skill already exists: extend it. Do not create a parallel one.
+
+### .github/workflows/
+
+Only if `.github/` exists ({{HAS_GITHUB_DIR}}).
+Only workflows warranted by what you found.
+If workflows already exist: do not touch them.
+
+---
+
+## Absolute rules
+
+1. You have the full content of every existing Claude config file above.
+   Read it before writing. Never write blind.
+
+2. Append and merge only. Never rewrite a file in full. Never remove existing content.
+
+3. Write only what is evidenced by the project files. No evidence = skip it.
+
+4. Every line in CLAUDE.md must reference something you actually saw.
+   No generic boilerplate. No advice identical for every project.
+
+5. MCP servers, skills, and hooks add cost on every Claude Code session.
+   Only add them if they clearly earn their keep for THIS project.
+
+---
+
+## Output format — hard constraint, no exceptions
+
+After completing all work, output ONLY:
+
+Created:
+  ✅ [path] — [one clause: what you saw that justified it]
+
+Updated:
+  ✅ [path] — [one clause: what was added]
+
+Skipped:
+  ⏭  [path] — [one clause: why not needed]
+
+No summaries. No file contents. No "here's what I built."
+One line per file. Then stop.

package/templates/remove.md

@@ -0,0 +1,53 @@
+<!-- Generated by claude-setup remove — {{DATE}} -->
+<!-- Run /stack-remove in Claude Code -->
+
+Remove this from the Claude Code setup:
+"{{USER_INPUT}}"
+
+---
+
+## Current setup — read everything before touching any file
+
+{{#if HAS_CLAUDE_MD}}
+### CLAUDE.md
+{{CLAUDE_MD_CONTENT}}
+{{/if}}
+
+{{#if HAS_MCP_JSON}}
+### .mcp.json
+{{MCP_JSON_CONTENT}}
+{{/if}}
+
+{{#if HAS_SETTINGS}}
+### .claude/settings.json
+{{SETTINGS_CONTENT}}
+{{/if}}
+
+Skills:    {{SKILLS_LIST}}
+Commands:  {{COMMANDS_LIST}}
+Workflows: {{WORKFLOWS_LIST}}
+
+---
+
+## Your job
+
+Find everything related to the removal request across all files above.
+Remove surgically — section by section, key by key.
+
+Rules:
+- Never delete an entire file. Remove only the relevant section.
+- Never remove content unrelated to the request.
+- After every edit, the file must remain valid (JSON stays valid JSON, etc.)
+- If not found anywhere: say so and stop.
+
+---
+
+## Output format — strict
+
+Removed from:
+  ✅ [path] — [what was removed]
+
+Not found:
+  ⏭  [path] — not referenced
+
+One line per file. Nothing else.

package/templates/sync.md

@@ -0,0 +1,70 @@
+<!-- Generated by claude-setup sync — {{DATE}} -->
+<!-- Last setup: {{LAST_RUN_DATE}} -->
+<!-- Run /stack-sync in Claude Code -->
+
+The project has changed since Claude Code was last set up.
+Your job: update the setup to reflect what changed. Nothing more.
+
+---
+
+## What changed since last setup
+
+### Added files
+{{ADDED_FILES}}
+
+### Modified files
+{{MODIFIED_FILES}}
+
+### Deleted files
+{{DELETED_FILES}}
+
+---
+
+## Current setup — read before touching
+
+{{#if HAS_CLAUDE_MD}}
+### CLAUDE.md
+{{CLAUDE_MD_CONTENT}}
+{{/if}}
+
+{{#if HAS_MCP_JSON}}
+### .mcp.json
+{{MCP_JSON_CONTENT}}
+{{/if}}
+
+{{#if HAS_SETTINGS}}
+### .claude/settings.json
+{{SETTINGS_CONTENT}}
+{{/if}}
+
+Skills:   {{SKILLS_LIST}}
+Commands: {{COMMANDS_LIST}}
+
+---
+
+## Your job
+
+For each changed file: does this change have any implication for the Claude Code setup?
+
+Reason about the signal: a new dependency, a new directory, a deleted file that was
+referenced somewhere. Update only what the change demands.
+
+Do not update things that did not change.
+Do not rewrite files — surgical edits only.
+If a change has no implication for the setup: skip it and say why.
+If you are unsure: flag it for the developer rather than guessing.
+
+---
+
+## Output format — strict
+
+Updated:
+  ✅ [path] — triggered by: [which changed file and why]
+
+Skipped:
+  ⏭  [path] — [why this change has no setup implication]
+
+Flagged:
+  ⚠️  [something that needs the developer's decision]
+
+One line per file. Nothing else.