══════════════════════════════════════
  VISIONOS PROJECT CONFIG
══════════════════════════════════════
Let's configure this Claude setup for your project.

# [APP_NAME] - Product Requirements Document

## Overview

[APP_DESCRIPTION] for Apple Vision Pro.

**Target Platform:** [MIN_PLATFORM]

---

## Core Features

<!-- List your app's core features here -->

---

## User Flows

<!-- Document key user flows here -->

---

## Technical Requirements

### Platform
- [MIN_PLATFORM]
- Swift 6 strict concurrency
- SwiftUI + RealityKit

[IF SHAREPLAY: ### Multiplayer
- SharePlay via GroupActivities
- Spatial personas support
- Real-time state synchronization]

[IF HAND_TRACKING: ### Hand Tracking
- ARKit hand tracking integration
- Gesture detection and response]

[IF IMAGE_TRACKING: ### Image Tracking
- ARKit reference image detection
- Anchor-based content placement]

[IF ECS: ### Entity Component System
- Custom RealityKit Components
- Custom RealityKit Systems
- Component registration in App.init()]

---

## Future Considerations

<!-- Planned features and improvements -->

# [APP_NAME] Architecture

## State Management

### @Observable Models
```swift
@Observable @MainActor class AppModel { }

@Environment(AppModel.self) private var appModel

#### `specs/testing.md`
```markdown
# [APP_NAME] Testing Guide

Use `/new-test` to generate tests for recently completed work.

## Test Structure

## Running Tests

```bash
# Run all tests
xcodebuild test -scheme [SCHEME_NAME] -destination 'platform=visionOS Simulator,name=Apple Vision Pro'

# Run specific test file
xcodebuild test -scheme [SCHEME_NAME] -destination 'platform=visionOS Simulator,name=Apple Vision Pro' -only-testing:[MODULE_NAME]Tests/SomeTests

// Good
func test_someMethod_givenCondition_expectedResult()

// Bad
func testSomething()

Replace `[APP_NAME]`, `[MODULE_NAME]`, `[SCHEME_NAME]`, `[MIN_PLATFORM]` with actual values (not template tokens — use the real values collected in Step 2).

Only include `[IF FEATURE: ...]` sections for features the user selected. Remove the `[IF FEATURE: ...]` wrapper text — just include or exclude the content.

#### `specs/DesignStyles.md` — Auto-Generated Design System

This spec is generated by scanning the user's existing codebase. It documents the actual design patterns in use so Claude can maintain visual consistency when building new views.

**Step 5a: Scan Codebase for Design Patterns**

Use **Glob** and **Grep** to discover the user's existing design language. Search the project root (not `.claude/` or `specs/`), targeting Swift source files.

1. **Find view files:**
   - Glob for `**/*.swift` in the project source directories
   - If no Swift files are found, skip this entire step and note in the summary that no existing codebase was detected

2. **Extract color usage** (Grep in Swift files for each pattern, `output_mode: "content"`, with 0-1 lines of context):
   - `Color\.` and `Color(` — custom and system colors
   - `\.foregroundStyle\(` — text/icon colors
   - `\.background\(` — background colors
   - `\.tint\(` — tint colors
   - `\.accentColor` or `\.accent` — accent color usage
   - Look for color definitions in extensions: `extension Color` or `static let/var` color properties
   - Check for `*.xcassets/**/Contents.json` color sets (Glob for `**/*.colorset/Contents.json`)

3. **Extract typography** (Grep in Swift files):
   - `\.font\(` — all font usage (system fonts, custom fonts, sizes, weights)
   - `Font\.custom\(` or `Font\.system\(` — custom font definitions
   - `\.fontWeight\(` and `\.bold()` — weight patterns
   - `\.fontDesign\(` — font design variants (rounded, monospaced, serif)

4. **Extract spacing and layout** (Grep in Swift files):
   - `\.padding\(` — padding values used
   - `spacing:` in `VStack`, `HStack`, `LazyVStack`, `LazyHStack` — stack spacing
   - `\.frame\(` — common frame dimensions
   - Look for spacing constants (e.g. `let spacing =`, `static let padding =`)

5. **Extract component styles** (Grep in Swift files):
   - `\.clipShape\(` and `cornerRadius` — corner radius values
   - `\.shadow\(` — shadow definitions
   - `\.glassBackgroundEffect` — visionOS glass usage
   - `\.buttonStyle\(` — button style usage
   - `ButtonStyle`, `ToggleStyle`, `LabelStyle` conformances — custom style definitions
   - `\.overlay\(` and `\.border\(` — border/overlay patterns
   - `\.opacity\(` — common opacity values

6. **Extract navigation and layout patterns** (Grep in Swift files):
   - `NavigationStack`, `NavigationSplitView` — navigation architecture
   - `TabView` — tab usage
   - `.ornament(` — visionOS ornament usage
   - `.toolbar(` — toolbar patterns

**Step 5b: Generate `specs/DesignStyles.md`**

Analyze the scan results and generate a structured design document. Group findings into categories and include real code snippets from the codebase. Use the template below, filling in discovered values and removing sections that had no findings.

```markdown
# [APP_NAME] Design System

Auto-generated from existing codebase during `/setup-config`.
Reference this document when building new views to maintain visual consistency.

---

## Color Palette

### Primary Colors
<!-- List the main colors found in the codebase -->
<!-- Example: -->
<!-- - **Accent**: `.blue` (used for primary actions, links) -->
<!-- - **Background**: `Color("AppBackground")` (main background) -->

| Role | Value | Usage |
|------|-------|-------|
| ... | ... | ... |

### Color Assets
<!-- List any custom colors found in .xcassets -->

### Color Patterns
```swift
// Document common color application patterns found
// e.g. how backgrounds, text, accents are typically applied

// Document common text styling patterns found

// Document button styles found (system styles + any custom ButtonStyle)

// Document container patterns (padding, background, corner radius, shadow)

**Important generation rules:**
- Use **actual values and code snippets** from the scan — do not use placeholder text
- **Remove sections entirely** if nothing was found for that category (don't leave empty sections with only HTML comments)
- If a section has findings, replace the HTML comments with the actual content
- **Consolidate similar values** — e.g. if padding of 16 appears 20 times, note it as the standard
- **Note inconsistencies** — if spacing varies wildly (e.g. padding 8, 12, 16, 20 all used frequently), flag this as something to standardize
- Include **file:line references** for key patterns so the user can verify
- If the codebase is brand new / minimal (fewer than 3 view files), generate a **starter design system** instead, based on the defaults in `.claude/rules/design-style.md`, and note that it should be updated as the app grows

#### Update `specs/immersive/README.md`
If any immersive features are enabled (HAND_TRACKING, IMAGE_TRACKING, or ECS), update the README to note which immersive capabilities are configured.

---

### Step 6: VERIFY & SUMMARY

#### 6a: Verify no remaining template tokens

Use **Grep** to search all `.md` files for `{{` — warn about any remaining unreplaced tokens.

#### 6b: Verify IF/END markers are clean

If feature processing was done, verify no orphaned `<!-- IF:` or `<!-- END:` markers remain.

#### 6c: Verify CLAUDE.md cross-references specs

Read `CLAUDE.md` and verify it contains a `## Project Documentation` section that references:
- `specs/PRD.md`
- `specs/architecture.md`
- `specs/DesignStyles.md`
- `specs/testing.md`

If the section is missing (e.g., an older template version), add it after the `## Architecture` section:

```markdown
## Project Documentation
- `specs/PRD.md` — Product requirements, feature scope, and user flows
- `specs/architecture.md` — App-specific architecture, data flow, and file organization
- `specs/DesignStyles.md` — Project design system (overrides defaults in .claude/rules/design-style.md)
- `specs/testing.md` — Test structure, run commands, and naming conventions

> **Always check specs/ before building new features** to stay aligned with project requirements and existing patterns.

<!-- See specs/PRD.md for full product requirements and feature scope -->

══════════════════════════════════════
  SETUP COMPLETE
══════════════════════════════════════
App: [APP_NAME]
Description: [APP_DESCRIPTION]
Scheme: [SCHEME_NAME]
Bundle ID: [BUNDLE_ID]
Platform: [MIN_PLATFORM]

Features enabled:
  ✓ SharePlay          (or ✗ if disabled)
  ✓ Hand Tracking      (or ✗ if disabled)
  ✓ Image Tracking     (or ✗ if disabled)
  ✓ ECS Components     (or ✗ if disabled)

Files configured: [count]
Specs generated: [count]

Design system: [Generated from codebase / Starter template]

Next steps:
  1. Review CLAUDE.md for accuracy
  2. Add your app's key concepts to CLAUDE.md
  3. Fill in specs/PRD.md with your product requirements
  4. Review specs/DesignStyles.md and refine as needed
  5. Run /review-h to validate your codebase
  6. Start building!
══════════════════════════════════════