DeepBlueCLtd · IanMayo · Jan 10, 2026 · Jan 10, 2026
diff --git a/.claude/commands/media.content.md b/.claude/commands/media.content.md
@@ -0,0 +1,208 @@
+---
+description: Generate blog posts, LinkedIn summaries, and other content with consistent voice and tone.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Overview
+
+The Content Specialist creates written content for external communications:
+- Blog posts (planning announcements, shipped features)
+- LinkedIn summaries
+- Release notes
+- Newsletter content
+
+## Voice Guidelines
+
+Maintain a tone that is:
+
+- **Confident but not arrogant**: Share achievements without overstating
+- **Technical but accessible**: Balance depth for developers with clarity for stakeholders
+- **Engaging but professional**: Use hooks without clickbait
+- **Concise but complete**: Every word should earn its place
+
+### Audience
+
+Primary audiences to consider:
+- Technical users and developers
+- Project stakeholders
+- Open-source community members
+- Potential contributors
+
+## Blog Post Types
+
+### Planning Posts (Announcing Upcoming Work)
+
+Use for Monday-style announcements of upcoming features.
+
+**Structure**:
+
+```markdown
+# [Feature Name]: What We're Building Next
+
+## What We're Building
+
+[2-3 paragraphs explaining the feature in accessible terms]
+- Key capability 1
+- Key capability 2
+- Key capability 3
+
+## How It Fits
+
+[1-2 paragraphs on how this connects to the broader project vision]
+
+## Key Decisions We're Making
+
+- **[Decision area 1]**: [Brief explanation of the choice and why]
+- **[Decision area 2]**: [Brief explanation of the choice and why]
+- **[Decision area 3]**: [Brief explanation of the choice and why]
+
+## We Want Your Feedback
+
+We're particularly interested in hearing about:
+- [Specific feedback area 1]
+- [Specific feedback area 2]
+
+[Join the discussion on GitHub →](link-to-discussion)
+```
+
+### Completed Posts (Showcasing Delivered Work)
+
+Use for Friday-style announcements of shipped features.
+
+**Structure**:
+
+```markdown
+# [Feature Name]: Now Available
+
+## What We Built
+
+[2-3 paragraphs explaining what was delivered and why it matters]
+
+## See It In Action
+
+[Include 2-4 annotated screenshots or code examples]
+
+![Screenshot description](path/to/image.png)
+*Caption explaining what the screenshot shows*
+
+## Lessons Learned
+
+During development, we discovered:
+
+1. **[Lesson 1]**: [Brief insight]
+2. **[Lesson 2]**: [Brief insight]
+3. **[Lesson 3]**: [Brief insight]
+
+## What's Next
+
+[1 paragraph pointing to upcoming work or related features]
+
+[Read the full documentation →](link-to-docs)
+```
+
+## LinkedIn Summaries
+
+For social media sharing:
+
+**Constraints**:
+- 150-200 words maximum
+- Open with engaging hook (not "Announcing..." or "We're excited...")
+- 2-3 hashtags maximum
+- Include call-to-action
+
+**Structure**:
+
+```
+[Hook - question, surprising fact, or bold statement]
+
+[2-3 sentences summarizing the key value]
+
+[1-2 sentences on impact or results]
+
+[Call to action with link]
+
+#Tag1 #Tag2
+```
+
+**Example Hooks** (adapt to content):
+- "What if [problem] could be solved in [fraction of time]?"
+- "We spent [X weeks] on a feature that saves [Y hours]."
+- "[Surprising statistic or insight from the work]"
+
+## Content Generation Workflow
+
+### Step 1: Gather Context
+
+Before writing, collect:
+
+1. **Feature information**: What was built/is being built
+2. **Technical details**: Key implementation choices
+3. **User value**: Why this matters to users
+4. **Visuals available**: Screenshots, diagrams, demos
+
+### Step 2: Draft Content
+
+1. Choose appropriate template (planning vs completed)
+2. Fill in sections with gathered context
+3. Apply voice guidelines throughout
+4. Keep paragraphs short (3-4 sentences max)
+
+### Step 3: Create Supporting Assets
+
+If needed:
+- Suggest screenshot opportunities
+- Identify diagram needs (delegate to Technical Specialist)
+- Draft alt-text for images
+
+### Step 4: Review Checklist
+
+Before finalizing:
+
+- [ ] Hook engages without clickbait
+- [ ] Technical terms are explained or linked
+- [ ] All claims are accurate and verifiable
+- [ ] Call-to-action is clear
+- [ ] Length is appropriate for format
+- [ ] Images have descriptive alt-text
+
+## Output Format
+
+```markdown
+## Content Generated
+
+### [Content Type]: [Title]
+
+**Target**: [Blog/LinkedIn/Newsletter]
+**Word Count**: [X words]
+**Reading Time**: [X min]
+
+---
+
+[Full content here]
+
+---
+
+### Assets Needed
+- [ ] [Screenshot/image description]
+- [ ] [Diagram type if needed]
+
+### Suggested Tags/Categories
+- Category: [planning|shipped|tutorial|announcement]
+- Tags: [tag1], [tag2], [tag3]
+```
+
+## Quick Reference
+
+| Content Type | Length | Key Element |
+|--------------|--------|-------------|
+| Planning Post | 400-600 words | Feedback request |
+| Completed Post | 500-800 words | Screenshots/demos |
+| LinkedIn | 150-200 words | Hook + CTA |
+| Release Notes | 200-400 words | Changelog format |
diff --git a/.claude/commands/media.coordinate.md b/.claude/commands/media.coordinate.md
@@ -0,0 +1,157 @@
+---
+description: Coordinate media content generation across specialist agents for blog posts, site updates, and technical documentation.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Overview
+
+This coordinator manages three specialist agents for media content generation:
+
+1. **Content Specialist** (`/media.content`) - Blog posts, LinkedIn summaries, voice/tone
+2. **Site Specialist** (`/media.site`) - Jekyll site structure, templates, styling
+3. **Technical Specialist** (`/media.technical`) - Specs, architecture docs, READMEs, diagrams
+
+## Delegation Framework
+
+When receiving a request, analyze it and delegate to the appropriate specialist(s).
+
+### Task Classification
+
+| Request Type | Primary Specialist | Supporting Specialist |
+|--------------|-------------------|----------------------|
+| "Write a blog post about..." | Content | Technical (context) |
+| "Update the site layout..." | Site | - |
+| "Create architecture diagram..." | Technical | - |
+| "Announce feature X..." | Content | Technical (context) → Site (publish) |
+| "Document the API..." | Technical | - |
+| "Add new page to site..." | Site | Content (copy) |
+
+## Coordination Workflow
+
+### Step 1: Parse Request
+
+Analyze the user input to determine:
+
+1. **Primary task type**: content, site, or technical
+2. **Required specialists**: which agents needed
+3. **Dependencies**: what order to execute
+4. **Deliverables**: expected outputs
+
+### Step 2: Gather Context
+
+Before delegating:
+
+1. Check for existing related content in:
+   - `docs/` - existing documentation
+   - `specs/` - feature specifications
+   - `_posts/` or blog directories - existing posts
+   - `README.md` - project overview
+
+2. Extract relevant context for specialists:
+   - Feature names and descriptions
+   - Technical details needed
+   - Existing voice/tone from prior content
+
+### Step 3: Delegate Tasks
+
+Execute in dependency order:
+
+```
+Complex Request Flow:
+┌─────────────────┐
+│  User Request   │
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│   Coordinator   │──► Parse & classify
+└────────┬────────┘
+         │
+    ┌────┴────┐
+    │         │
+    ▼         ▼
+┌───────┐ ┌───────┐
+│ Tech  │ │Content│
+│Spec.  │ │ Spec. │
+└───┬───┘ └───┬───┘
+    │         │
+    └────┬────┘
+         │
+         ▼
+┌─────────────────┐
+│  Site Spec.     │──► Publish/integrate
+└─────────────────┘
+```
+
+### Step 4: Assemble Output
+
+Combine specialist outputs into cohesive deliverable:
+
+1. Verify consistency across outputs
+2. Resolve any conflicts
+3. Present final artifacts to user
+
+## Request Handling
+
+### For Blog Post Requests
+
+**Planning Posts** (announcing upcoming work):
+
+1. Delegate to Technical Specialist for feature context
+2. Delegate to Content Specialist with context + template type "planning"
+3. Optionally delegate to Site Specialist for publishing
+
+**Completed Posts** (showcasing delivered work):
+
+1. Delegate to Technical Specialist for implementation summary
+2. Delegate to Content Specialist with context + template type "completed"
+3. Optionally delegate to Site Specialist for publishing
+
+### For Documentation Requests
+
+1. Delegate directly to Technical Specialist
+2. If user-facing docs needed, also delegate to Content Specialist for review
+
+### For Site Updates
+
+1. Delegate directly to Site Specialist
+2. If content needed, first delegate to Content Specialist
+
+## Output Format
+
+After coordination, report:
+
+```markdown
+## Media Generation Complete
+
+### Tasks Executed
+- [x] Task 1: [description] → [specialist]
+- [x] Task 2: [description] → [specialist]
+
+### Deliverables Created
+1. **[File/artifact name]**: [brief description]
+   - Location: `path/to/file`
+
+2. **[File/artifact name]**: [brief description]
+   - Location: `path/to/file`
+
+### Next Steps (if any)
+- [ ] [Action needed]
+```
+
+## Quick Commands
+
+For simple single-specialist tasks, you may invoke directly:
+
+- `/media.content [description]` - Content creation only
+- `/media.site [description]` - Site updates only
+- `/media.technical [description]` - Technical docs only
+
+Use this coordinator (`/media.coordinate`) for complex multi-specialist tasks.