Add CLAUDE.md with project guidance for Claude Code

.gemini/skills/sketchspark-author/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: sketchspark-author
+description: Specialized authoring guide for the "Pro Git for UX Designers" book revision. Use when writing, editing, or outlining chapters for the SketchSpark storyline.
+---
+
+# SketchSpark Authoring Skill
+
+Use this skill to author high-quality, consistent content for the "Pro Git for UX Designers" revision.
+
+## Authoring Workflow
+
+1.  **Context Alignment:** Identify the target chapter and its storyline goals in [storyline.md](references/storyline.md).
+2.  **Voice Check:** Ensure your writing style matches the [Voice and Tone Guide](references/voice.md).
+3.  **Convention Verification:** Use character names, branch names, and milestones from [conventions.md](references/conventions.md).
+4.  **Content Tagging:** Apply the correct tag to each section based on the [Content Type Lexicon](references/lexicon.md).
+5.  **Technical Validation:** Reference the [SketchSpark Product Spec](references/spec.md) for technical accuracy of the AI prototyping workflow.
+
+## Guidelines
+
+- **Empathetic Narration:** Focus on Nora and Sam's journey. Relate Git commands to design pain points (e.g., losing research, managing multiple layout explorations).
+- **AsciiDoc Formatting:** Use standard AsciiDoc for sections (`==`, `===`, `====`), source blocks (`[source,bash]`), and tags (`tag::type[]`).
+- **Simulated Commands:** When providing terminal examples, use the `sketchspark/` directory structure.
+- **Commit Messages:** Always use the `[Phase: Component]` prefix convention.
+
+## Detailed References
+
+- **[storyline.md](references/storyline.md)**: The 10-chapter narrative arc.
+- **[spec.md](references/spec.md)**: Product details for SketchSpark.
+- **[lexicon.md](references/lexicon.md)**: Tag definitions for sections.
+- **[conventions.md](references/conventions.md)**: Naming standards.
+- **[voice.md](references/voice.md)**: Persona and style guidance.

.gemini/skills/sketchspark-author/references/conventions.md

@@ -0,0 +1,56 @@
+# Cross-Chapter Conventions
+
+This document ensures consistency across the entire book. All walkthroughs and prose must adhere to these facts.
+
+## The SketchSpark Team
+- **Nora:** UX Lead (CLI user)
+- **Sam:** UI Designer (VS Code user)
+- **Priya:** Illustrator (GitHub Desktop user)
+- **Kai:** Frontend/ML Engineer (JetBrains user)
+- **Marcus:** Community Contributor (fork-and-PR workflow)
+
+## Repository Structure
+The repo name is always `sketchspark`.
+```
+sketchspark/
+├── product-brief.md
+├── research/
+├── concept/
+├── screens/
+├── illustrations/
+├── icons/
+├── design-tokens.json
+├── pipeline/
+├── docs/
+├── CONTRIBUTING.md
+├── CHANGELOG.md
+├── .gitignore
+└── .gitattributes
+```
+
+## Milestone Tags
+- `v0.1-concept`: Concept approved, wireframes in place.
+- `v0.5-alpha`: End-to-end pipeline working (web).
+- `v0.8-beta`: Multi-platform, design token integration.
+- `v1.0`: Public launch, refinement editor.
+
+## Standard Branch Names
+- `main`: The stable version of the truth.
+- `option/<name>`: Design explorations (e.g., `option/card-layout`).
+- `feature/<name>`: Approved work (e.g., `feature/onboarding-illustrations`).
+- `fix/<name>`: Corrections (e.g., `fix/contrast-audit`).
+- `research/<name>`: Discovery work.
+
+## Commit Message Format
+The team uses a `[Phase: Component]` prefix:
+- `[Design: Results Screen] Add overlay diff comparison mode`
+- `[Research: Persona] Update early-adopter goals`
+- `[Pipeline: Prompts] Improve mobile layout generation`
+- `[Fix: Onboarding] Correct tablet breakpoint`
+
+## Key File Ownership
+- `product-brief.md`, `research/`: Owned by Nora.
+- `screens/`, `design-tokens.json`: Owned by Sam.
+- `illustrations/`, `icons/`: Owned by Priya.
+- `pipeline/`: Owned by Kai.
+- `prompts/`: Edited by Kai and Marcus.

.gemini/skills/sketchspark-author/references/lexicon.md

@@ -0,0 +1,28 @@
+# Content Type Lexicon
+
+This lexicon defines the content type tags used across all chapter TOC files.
+Each sub-section is tagged to describe the **primary kind of content** it delivers.
+
+## Content Types
+
+| Tag          | Meaning                                                                                     |
+|--------------|---------------------------------------------------------------------------------------------|
+| `concept`    | Explains an idea, model, or theory. Answers "what is this?" or "how does this work?"        |
+| `walkthrough`| Step-by-step narrative that guides the reader through a realistic scenario or workflow       |
+| `procedure`  | Task-oriented instructions: do X, then Y, then Z. Answers "how do I do this?"               |
+| `reference`  | Lookup-oriented listing of options, flags, commands, or settings                             |
+| `history`    | Historical narrative or background context about origins and evolution                       |
+| `comparison` | Evaluates alternatives side-by-side, including pros/cons and trade-offs                      |
+| `diagram`    | Primarily visual — uses diagrams or figures to explain a model or data structure              |
+| `recipe`     | Short, self-contained example showing a specific technique or tip                            |
+| `config`     | Configuration-focused: editing config files, setting options, customizing behavior           |
+| `internals`  | Deep dive into underlying mechanisms, data structures, or protocols                          |
+| `overview`   | Brief orientation or survey — introduces a topic area without going deep                     |
+| `integration`| Covers connecting Git with external tools, services, or platforms                            |
+
+## Usage Rules
+
+1. Every sub-section (`====` level) and leaf section (`===` with no children) gets exactly one tag.
+2. Parent sections (`===` with children) do **not** get tagged — the children carry the type.
+3. When a section blends types, choose the **dominant** one (>50% of content).
+4. `Summary` sections at chapter end are tagged `overview` (they recap, not introduce).