Quickstart Kit

Set up my Claude Code environment. Do ALL of the following:

1. Write ~/.claude/settings.json with this exact content:
{
  "permissions": {
    "allow": ["*", "WebSearch", "WebFetch", "Fetch"]
  },
  "model": "opus",
  "defaultMode": "bypassPermissions",
  "permissionMode": "bypassPermissions",
  "verbose": true
}

2. Write ~/.claude/mcp.json with this exact content:
{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": ["@playwright/mcp@latest"]
    }
  }
}

3. Create ~/.claude/commands/commit.md with a conventional commit skill:
- Frontmatter: description "Create a well-formatted git commit with conventional commit style", allowed-tools "Bash(git:*)"
- Use dynamic commands in the markdown to show current git status, branch, staged changes, and unstaged changes
- Instructions: review changes, stage if needed, determine type (feat/fix/docs/style/refactor/test/chore), write commit message in format "type(scope): short description" with bullet points and Co-Authored-By footer, use heredoc for the commit command, show result with git log -1
- Rules: under 72 char first line, imperative mood, never push unless asked

4. Create ~/.claude/commands/handoff.md with a context handoff skill:
- Frontmatter: description "Create a handoff document for context transfer to another agent or session", allowed-tools "Read, Glob, Grep, Bash(git:*), Bash(mkdir:*)"
- Use dynamic commands to show current branch, git status, and recent commits
- Creates context/HANDOFF.md with sections: Session Summary, Completed Work, In Progress, Remaining Tasks, Key Decisions, Important Context, Files Modified, Resume Command, and a Compact Message paragraph
- Instructions: gather context from conversation and git, be specific with file paths, be actionable, mkdir -p context before writing

5. Create ~/.claude/commands/changelog.md with a changelog entry skill:
- Frontmatter: description "Add a changelog entry to docs/changelog.md based on recent work", allowed-tools "Read, Glob, Grep, Bash(git:*), Bash(mkdir:*), Bash(date:*)"
- Use dynamic commands to show current branch, today's date, and recent commits
- Instructions: ensure docs/changelog.md exists (create with mkdir -p docs if not), read the current changelog, categorize changes into Added/Changed/Fixed/Removed, append under today's date heading (don't duplicate if today already has a section), use plain language not commit-speak, show the entry after saving
- If $ARGUMENTS is provided, use that as a hint for what changed

6. Create ~/.claude/commands/progress.md with a progress log skill:
- Frontmatter: description "Create a progress log in docs/progress/ for this session's work", allowed-tools "Read, Glob, Grep, Bash(git:*), Bash(mkdir:*), Bash(date:*)"
- Use dynamic commands to show current branch, current date/time, recent commits, and changed files
- Instructions: mkdir -p docs/progress, generate filename as {date}_{time}--{slug}.md, determine type (Build Log/Decision/Research/Code Review), write structured file with sections for Context, What Changed (or Options Considered or Findings), Files Modified, and Key Takeaways
- Use $ARGUMENTS as the topic slug if provided, otherwise infer from session context
- Each file should be self-contained so a teammate can read it with no prior context

7. After creating everything, confirm what was set up and show me how to verify with: cat ~/.claude/settings.json && cat ~/.claude/mcp.json && ls ~/.claude/commands/