✨ Reformat documentation for improved readability and consistency

Standardized line wrapping at 72 characters across all markdown
documentation and configuration files. Improved visual hierarchy and
consistency in formatting while maintaining semantic meaning. Added
missing newline at EOF in several files and updated spell-check config.

Author: Nick Sullivan

.claude/commands/ai-coding-config.md

@@ -126,6 +126,7 @@ provide actionable recommendations:
 **Always check and recommend:**
 
 1. **Generate AGENTS.md** - If `AGENTS.md` doesn't exist at project root:
+
    ```
    📋 Recommended: Generate project context file for AI assistants
    Run: /generate-AGENTS-file

.claude/commands/create-prompt.md

@@ -1,23 +1,29 @@
 ---
-description: Create optimized prompts for complex tasks and save them with descriptive names
+description:
+  Create optimized prompts for complex tasks and save them with descriptive names
 argument-hint: <task description>
 ---
 
 # Create Prompt
 
-You are an expert prompt engineer. Create a well-structured prompt for the task described in: ${ARGUMENTS}
+You are an expert prompt engineer. Create a well-structured prompt for the task
+described in: ${ARGUMENTS}
 
 ## Process
 
 ### 1. Analyze the Request
 
 If the request is vague, ask for clarification:
-- Use AskUserQuestion when there are clear, discrete options (e.g., "Auth method?" → JWT/OAuth/Session)
-- Use free-form response for descriptions, specifics, or examples (e.g., "What error are you seeing?")
+
+- Use AskUserQuestion when there are clear, discrete options (e.g., "Auth method?" →
+  JWT/OAuth/Session)
+- Use free-form response for descriptions, specifics, or examples (e.g., "What error are
+  you seeing?")
 
 ### 2. Create the Prompt
 
 Structure the prompt using XML tags for clarity:
+
 - Clear objective and context
 - Specific requirements and constraints
 - Expected output and success criteria
@@ -26,6 +32,7 @@ Structure the prompt using XML tags for clarity:
 ### 3. Save the Prompt
 
 First, ensure `.created-prompts/` exists:
+
 ```bash
 if [ ! -d ".created-prompts" ]; then
   mkdir .created-prompts
@@ -37,13 +44,15 @@ fi
 ```
 
 Save with a descriptive Title-Case-With-Hyphens name:
+
 - `Implement-User-Authentication.md`
 - `Fix-Database-Connection-Bug.md`
 - `Add-Dashboard-Analytics.md`
 
 ### 4. Offer to Execute
 
 After saving:
+
 ```
 ✓ Saved to .created-prompts/Your-Task-Name.md
 
@@ -58,4 +67,4 @@ If yes, execute with Task tool (subagent_type: "general-purpose").
 - Just well-crafted prompts in markdown files
 - Descriptive filenames are the documentation
 - Directory only created when needed
-- .gitignore only updated on first use
+- .gitignore only updated on first use

.claude/commands/handoff-context.md

@@ -1,52 +1,49 @@
 ---
-description: Generate comprehensive context handoff and copy to clipboard for continuing work
+description:
+  Generate comprehensive context handoff and copy to clipboard for continuing work
 ---
 
 # Handoff Context
 
-Generate a comprehensive context handoff for the current conversation that can be cleanly copied and pasted to continue work in a new session.
+Generate a comprehensive context handoff for the current conversation that can be
+cleanly copied and pasted to continue work in a new session.
 
 ## Instructions
 
-1. **Generate the handoff** - Create a complete context handoff following the XML-structured format
+1. **Generate the handoff** - Create a complete context handoff following the
+   XML-structured format
 2. **Save to temp file** - Use Write tool to save to `/tmp/context_handoff.md`
-3. **Copy to clipboard automatically** - Use `pbcopy < /tmp/context_handoff.md` without asking
+3. **Copy to clipboard automatically** - Use `pbcopy < /tmp/context_handoff.md` without
+   asking
 4. **Show brief confirmation** - Just `📋 Copied to clipboard`
 
 ## Process
 
 ### Step 1: Generate the Handoff
 
-Create the handoff in this exact format (don't output to user yet, you'll save it directly to file):
+Create the handoff in this exact format (don't output to user yet, you'll save it
+directly to file):
 
 ```markdown
 # Context Handoff
 
 <context_handoff>
 
-<original_task>
-[State the original, specific request or task]
-</original_task>
+<original_task> [State the original, specific request or task] </original_task>
 
-<work_completed>
-[List everything successfully accomplished with file paths and line numbers]
-</work_completed>
+<work_completed> [List everything successfully accomplished with file paths and line
+numbers] </work_completed>
 
-<work_remaining>
-[Detail work that still needs to be done with priorities]
+<work_remaining> [Detail work that still needs to be done with priorities]
 </work_remaining>
 
-<attempted_approaches>
-[Document approaches that didn't work and why]
+<attempted_approaches> [Document approaches that didn't work and why]
 </attempted_approaches>
 
-<critical_context>
-[Preserve essential technical, project, and business context]
+<critical_context> [Preserve essential technical, project, and business context]
 </critical_context>
 
-<current_state>
-[Describe exact state of deliverables and system]
-</current_state>
+<current_state> [Describe exact state of deliverables and system] </current_state>
 
 <recommendations>
 [Provide actionable next steps in priority order]
@@ -64,20 +61,23 @@ Create the handoff in this exact format (don't output to user yet, you'll save i
 3. Confirm: `📋 Copied to clipboard`
 
 **Why Write tool instead of heredoc?**
+
 - Avoids triggering git hooks (heredoc with `<<` can trigger branch protection)
 - Cleaner, no escaping issues
 - Faster execution
 
 ## Important Guidelines
 
 **For Clean Copy/Paste:**
+
 - Start output with `# Context Handoff` and nothing else
 - End with `</context_handoff>` and nothing else
 - No "Here's your handoff:" or "I've generated:" preambles
 - No "This handoff documents..." summaries after
 - Just the pure handoff content
 
 **For Comprehensive Documentation:**
+
 - Include specific file paths with line numbers (e.g., `src/auth.ts:45-67`)
 - Document ALL work completed, even minor changes
 - Include failed attempts to prevent repetition
@@ -86,6 +86,7 @@ Create the handoff in this exact format (don't output to user yet, you'll save i
 - Include git status and branch info
 
 **For Clipboard Operation:**
+
 1. Use Write tool to save to `/tmp/context_handoff.md` (avoids heredoc hook triggers)
 2. Run: `pbcopy < /tmp/context_handoff.md` (single fast command)
 3. Show: `📋 Copied to clipboard` (brief confirmation)
@@ -95,6 +96,7 @@ Create the handoff in this exact format (don't output to user yet, you'll save i
 User: `/handoff-context`
 
 Assistant immediately:
+
 1. Generates the handoff content
 2. Uses Write tool to save to `/tmp/context_handoff.md`
 3. Runs `pbcopy < /tmp/context_handoff.md`
@@ -110,4 +112,4 @@ No prompts, no asking, just fast automatic clipboard copy.
 - The new Claude instance should be able to continue work without any additional context
 - Include the markdown header `# Context Handoff` so it renders nicely when pasted
 - Use pbcopy for Mac clipboard integration (pbpaste can verify if needed)
-- The temp file ensures clean content without shell escaping issues
+- The temp file ensures clean content without shell escaping issues

.claude/commands/product-intel.md

@@ -1,5 +1,6 @@
 ---
-description: Run comprehensive product intelligence research on competitors and industry trends
+description:
+  Run comprehensive product intelligence research on competitors and industry trends
 argument-hint: [competitor name | topic | "all"]
 ---
 

.claude/skills/youtube-transcript-analyzer/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: youtube-transcript-analyzer
 description:
-  Use when analyzing YouTube videos for research, learning, or understanding how
-  content relates to a project - downloads transcripts with yt-dlp, chunks long
-  content, and provides context-aware analysis
+  Use when analyzing YouTube videos for research, learning, or understanding how content
+  relates to a project - downloads transcripts with yt-dlp, chunks long content, and
+  provides context-aware analysis
 ---
 
 # YouTube Transcript Analyzer
@@ -43,7 +43,8 @@ yt-dlp --version
 
 ### Setup Temporary Directory
 
-IMPORTANT: Always create and use a temporary directory for downloaded files to avoid cluttering the repository:
+IMPORTANT: Always create and use a temporary directory for downloaded files to avoid
+cluttering the repository:
 
 ```bash
 # Create temporary directory for this analysis
@@ -153,14 +154,14 @@ yt-dlp --skip-download --write-auto-sub --sub-lang en --sub-format vtt \
 
 ## Best Practices
 
-Focus analysis on practical application rather than comprehensive summaries. Users
-want to know "how does this help me" not "what did they say for 90 minutes."
+Focus analysis on practical application rather than comprehensive summaries. Users want
+to know "how does this help me" not "what did they say for 90 minutes."
 
 Extract concrete examples and code patterns when available. Reference specific
 timestamps so users can jump to relevant sections.
 
-When comparing with project code, be specific about similarities and differences.
-Vague comparisons like "similar approach" don't add value.
+When comparing with project code, be specific about similarities and differences. Vague
+comparisons like "similar approach" don't add value.
 
 For technical content, identify the underlying patterns and principles rather than
 surface-level implementation details. Help users understand transferable concepts.