claude-react-kit: Skill for Claude Code

claude-react-kit — Setup

You are setting up claude-react-kit in this project. Your job is to analyze the codebase, understand its real stack and conventions, and generate perfectly customized configuration files.

Phase 1: Deep Analysis

Analyze the project thoroughly. Read and extract information from:

1. package.json — framework, dependencies, scripts, package manager (check for packageManager field too)
2. Lock file — which exists? (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, bun.lockb)
3. tsconfig.json — path aliases, strict mode, baseUrl, target
4. Framework config — next.config.*, vite.config.*, app.json/app.config.* (Expo), metro.config.*, remix.config.*
5. Linter/formatter — .eslintrc*, eslint.config.*, .prettierrc*, biome.json
6. Existing CLAUDE.md — if one exists, read it to preserve any project-specific rules the user already has
7. Existing .claude/ — if it exists, read settings.json and any custom rules to preserve them
8. Source directory structure — ls src/ or equivalent to understand the current architecture (do they already have features/, shared/, core/, design-system/, or different names?)
9. Routing — ls app/ or ls pages/ or ls src/screens/ to understand routing structure
10. State management patterns — grep for store/slice/atom definitions to understand actual usage
11. Test setup — jest.config.*, vitest.config.*, test file patterns
12. CI/CD — .github/workflows/, check what checks run

Build a complete mental model of the project before writing anything.

Phase 2: Ask What You Can't Detect

After analysis, present your findings to the user in a concise summary:

Here's what I detected:
- Framework: [X]
- Package manager: [X]
- Source structure: [describe what you found]
- State management: [X]
- Testing: [X]
- Styling: [X]
- Existing CLAUDE.md: [yes/no, summary if yes]
- Path aliases: [X]

Then ask ONLY about things you genuinely couldn't determine:

• If the architecture doesn't clearly match the 5-layer model, ask how they want to map their directories
• If there are conventions you noticed but aren't sure if they're intentional
• If there's an existing CLAUDE.md, ask what to keep vs replace
• Any ambiguities in their setup