code-comments

```bash

git clone https://github.com/petekp/claude-code-setup.git

cd claude-code-setup && ./setup.sh

// Optional prompt to streamline usage

claude "This is someone else's Claude Code configuration setup. I also want to version my Claude Code configuration. Analyze this configuration and provide a concise summary of its contents, how it differs from my current setup, what I may find particularly useful. After that, interview me about what I do or don't want to bring over to my own configuration, and my preferences around where nad how to store my own versioned Claude Code repo."

```

That's it. Your Claude Code now uses this repo's skills and commands.

This repo symlinks into ~/.claude/, so your Claude Code configuration lives in a git repo you control.

```

~/.claude/

├── skills/ → /skills/

├── commands/ → /commands/

├── agents/ → /agents/

├── hooks/ → /hooks/

└── scripts/ → /scripts/

```

Edit files in either location — they're the same files. Commit and push to sync across machines.

Fork and Clone (Recommended)

1. Fork this repo on GitHub
2. Clone and run setup:

```bash

git clone https://github.com/petekp/claude-code-setup.git

cd claude-code-setup && ./setup.sh

```

1. Customize — see [FORKING.md](FORKING.md)

Direct Clone

```bash

git clone https://github.com/petekp/claude-code-setup.git

cd claude-code-setup && ./setup.sh

```

Clone it wherever you keep projects — the setup script detects its own location.

From the repo directory:

```bash

git add -A && git commit -m "Update config" && git push

```

On another machine, just git pull.

```bash

./setup.sh --undo

```

Removes symlinks and restores any backed-up directories.

Skills

| Skill | Purpose |

| ----------------------- | ------------------------------------------------------------ |

| cognitive-foundations | User psychology, attention, memory limits, HCI research |

| design-critique | UI/UX reviews with severity ratings and accessibility checks |

| dreaming | Expansive thinking, 10x questions, breaking constraints |

| interaction-design | Component behaviors, micro-interactions, state transitions |

| model-first-reasoning | Formal logic, state machines, constraint systems |

| nextjs-boilerplate | Next.js + Tailwind + shadcn/ui project setup |

| oss-product-manager | Open source strategy, community dynamics, governance |

| react-component-dev | React patterns, forwardRef, accessibility, composition |

| startup-wisdom | Product strategy, PMF, prioritization, founder decisions |

| stress-testing | Pre-mortems, risk analysis, assumption audits |

| tutorial-writing | Educational content, step-by-step implementation guides |

| typography | Type scales, font selection, hierarchy, readability |

| unix-macos-engineer | Shell scripts, CLI tools, launchd, system admin |

| ux-writing | Microcopy, error messages, empty states, voice/tone |

| wise-novice | Fresh perspectives, naive questions, challenging assumptions |

Commands

| Command | Purpose |

| ---------------------- | ------------------------------------------------------------------ |

| /commit-and-push | Generate conventional commit and push to remote |

| /grok | Deep 6-phase codebase analysis for authoritative understanding |

| /interview | Gather context for planning with suggested answers |

| `/ne