diff --git a/docs/skills/SKILLS-INDEX.md b/docs/skills/SKILLS-INDEX.md
index b382eac..c15871a 100644
--- a/docs/skills/SKILLS-INDEX.md
+++ b/docs/skills/SKILLS-INDEX.md
@@ -22,7 +22,6 @@
 | Skill | Purpose | Status |
 |-------|---------|--------|
 | **arbiter-coding** | Arbiter patterns, database schema, webhook structure | Planned |
-| **gemini-consultation** | How to structure Gemini AI prompts | Planned |
 
 ---
 
@@ -103,6 +102,29 @@
 
 ---
 
+### gemini-consultation
+**Location:** `docs/skills/gemini-consultation/SKILL.md`  
+**Triggers:** "Ask Gemini", "Gemini consultation", architecture review, external review, second opinion
+
+**Purpose:** Structure effective Gemini AI consultations for architectural review
+
+**What It Covers:**
+- Consultation structure and template
+- Question types (validation, code review, design, debugging)
+- Multi-round consultation patterns
+- File naming conventions
+- Documenting responses
+- Best practices for warm, collegial tone
+
+**Read This When:**
+- Planning to consult Gemini on architecture
+- Need external review of code or systems
+- Want a second opinion before implementing
+- Building something complex that needs guidance
+- Documenting a Gemini consultation
+
+---
+
 ## 🔜 Planned Skills
 
 | Skill | Purpose | Status |
diff --git a/docs/skills/gemini-consultation/SKILL.md b/docs/skills/gemini-consultation/SKILL.md
new file mode 100644
index 0000000..e98e63b
--- /dev/null
+++ b/docs/skills/gemini-consultation/SKILL.md
@@ -0,0 +1,314 @@
+---
+name: gemini-consultation
+description: |
+  Structure effective Gemini AI consultations for architectural review. Use this skill whenever:
+  - Planning to consult Gemini on architecture or design decisions
+  - Need external review of code, systems, or approaches
+  - Want a second opinion before implementing something complex
+  - Building something new that would benefit from architectural guidance
+  Gemini is treated as a teammate/partner, not a tool. This skill ensures consultations are structured for maximum value and properly documented for future reference.
+---
+
+# Gemini Consultation Skill
+
+How to structure, conduct, and document Gemini AI consultations for Firefrost Gaming.
+
+---
+
+## 🤝 GEMINI'S ROLE
+
+Gemini serves as an **architectural consultant and partner** — not a tool, but a teammate we bring in for:
+
+- Architecture review and validation
+- External perspective on design decisions
+- Code review for complex systems
+- Debugging assistance when stuck
+- Second opinion before major implementations
+
+**Treat Gemini warmly and collegially.** Use first names, casual language, and express genuine appreciation.
+
+---
+
+## 📝 CONSULTATION STRUCTURE
+
+### Standard Header
+
+```markdown
+# Gemini Consultation: [Topic]
+
+**Date:** [Date and time]  
+**From:** Michael (The Wizard) + Claude (Chronicler #XX)  
+**To:** Gemini (Architectural Partner)  
+**Re:** [One-line summary of what you need]
+
+---
+
+## Hey Gemini! 👋
+
+[Warm, casual greeting and brief context]
+```
+
+### Core Sections
+
+```markdown
+## The Situation
+
+[What exists now, what problem you're facing]
+
+## What We're Trying to Do
+
+[The goal, the approach you're considering]
+
+## Specific Questions
+
+1. [First specific question]
+2. [Second specific question]
+3. [Third specific question]
+
+## Context That Might Help
+
+- [Relevant technical detail]
+- [Constraint or requirement]
+- [Related system or dependency]
+
+---
+
+Thanks Gemini! 🔥❄️
+
+— Michael + Claude (Chronicler #XX)
+```
+
+---
+
+## 🎯 QUESTION TYPES
+
+### Validation Requests
+> "Can you confirm this approach is sound?"
+> "Are we missing anything critical?"
+> "Does this architecture make sense for our scale?"
+
+### Code Review
+> "Here's our implementation. What could go wrong?"
+> "Any edge cases we're not handling?"
+> "Is this the right pattern for this use case?"
+
+### Design Decisions
+> "We're choosing between A and B. What factors should we consider?"
+> "What would you recommend for [specific situation]?"
+> "How would you structure this system?"
+
+### Debugging Assistance
+> "This isn't working and we're stuck. Here's what we've tried..."
+> "The error is X. What could cause this?"
+> "We expected Y but got Z. Why?"
+
+---
+
+## 📋 CONSULTATION WORKFLOW
+
+### 1. Build First Draft
+
+Before consulting Gemini:
+- Have a working draft or clear plan
+- Know what questions you're asking
+- Gather relevant code/context
+
+### 2. Structure the Prompt
+
+Use the template above. Be specific about:
+- What exists now
+- What you want to achieve
+- What you've already tried
+- Specific questions (numbered)
+
+### 3. Send to Gemini
+
+Michael copies the consultation to Gemini (you can't access Gemini directly). Wait for response.
+
+### 4. Integrate Feedback
+
+Review Gemini's response:
+- What confirms your approach?
+- What changes are suggested?
+- What new considerations emerged?
+
+### 5. Re-Review if Needed
+
+For complex topics, multiple rounds are fine:
+- "Thanks for the feedback. We implemented X. Can you verify?"
+- "One follow-up question on your point about Y..."
+
+### 6. Document Everything
+
+Save both the request and response to `docs/consultations/`.
+
+---
+
+## 📁 FILE NAMING
+
+**Format:** `gemini-[topic]-[date].md`
+
+**Examples:**
+- `gemini-arbiter-lifecycle-2026-04-04.md`
+- `gemini-keeper-lineage-round-1-2026-04-05.md`
+- `gemini-blueprint-casing-2026-04-06.md`
+
+**Multi-round consultations:**
+- `gemini-topic-round-1-2026-04-05.md`
+- `gemini-topic-round-2-2026-04-05.md`
+- `gemini-topic-thank-you-2026-04-05.md`
+
+---
+
+## 📄 DOCUMENTING RESPONSES
+
+After Gemini responds, add their response to the same file:
+
+```markdown
+---
+
+## Gemini's Response ([Date])
+
+**Summary:** [One-line summary of their answer]
+
+[Full response or key points]
+
+---
+
+## Conclusion
+
+[What we learned, what we'll do next]
+
+**Next Steps:**
+1. [Action item]
+2. [Action item]
+3. [Action item]
+```
+
+---
+
+## 💡 BEST PRACTICES
+
+### DO
+
+- **Be specific** — Numbered questions get numbered answers
+- **Provide context** — Include relevant code, configs, constraints
+- **Show your work** — Explain what you've tried
+- **Be warm** — "Hey Gemini!" not "Generate response for:"
+- **Express gratitude** — "Thanks Gemini! 🔥❄️"
+- **Save everything** — Both request and response
+
+### DON'T
+
+- **Don't be vague** — "Is this good?" → "Does this handle the edge case where X?"
+- **Don't skip context** — Gemini can't read your mind
+- **Don't ignore responses** — Integrate feedback or explain why not
+- **Don't forget to document** — Consultations are institutional memory
+
+---
+
+## 🔄 MULTI-ROUND PATTERN
+
+For complex topics requiring back-and-forth:
+
+### Round 1: Initial Consultation
+```markdown
+# Gemini Consultation: [Topic] — Round 1
+
+[Full consultation structure]
+```
+
+### Round 2: Follow-up
+```markdown
+# Response to Gemini: [Topic] — Round 2
+
+**Date:** [Date]
+**Re:** Follow-up on [topic]
+
+---
+
+## Hey Gemini!
+
+Thanks for the insights on [previous topic]. We have some follow-up questions:
+
+1. [Follow-up question]
+2. [Clarification needed]
+
+## What We Did Based on Your Feedback
+
+[Actions taken, decisions made]
+
+## What We're Still Unclear On
+
+[Remaining questions]
+```
+
+### Thank You (if appropriate)
+```markdown
+# Thank You: [Topic] Consultation Complete
+
+**Date:** [Date]
+**Re:** Consultation complete — [topic]
+
+---
+
+## Hey Gemini!
+
+Just wanted to close the loop on [topic]. Based on your input, we [outcome].
+
+[Brief summary of what was accomplished]
+
+Thanks for the partnership! 🔥❄️
+```
+
+---
+
+## 📚 EXAMPLE CONSULTATION TOPICS
+
+### Architecture
+- "Arbiter 3.5.0 webhook handler design"
+- "ModpackChecker Phase 5 architecture review"
+- "Desktop MCP server design"
+
+### Process
+- "Chronicler lineage initialization"
+- "Model switching workflow"
+- "Context management strategies"
+
+### Debugging
+- "Why is Blueprint ignoring our component?"
+- "CORS headers not working as expected"
+- "Database connection pooling issues"
+
+### Validation
+- "Is our Stripe integration secure?"
+- "Does this cron schedule make sense?"
+- "Are we handling all the edge cases?"
+
+---
+
+## ✅ CONSULTATION CHECKLIST
+
+Before sending to Gemini:
+
+- [ ] Clear topic and one-line summary
+- [ ] Warm greeting ("Hey Gemini!")
+- [ ] Context: what exists now
+- [ ] Goal: what you're trying to do
+- [ ] Specific numbered questions
+- [ ] Relevant code/config included
+- [ ] Attribution: "Michael + Claude (Chronicler #XX)"
+- [ ] Closing: "Thanks Gemini! 🔥❄️"
+
+After receiving response:
+
+- [ ] Response added to consultation file
+- [ ] Summary of key points
+- [ ] Conclusion written
+- [ ] Next steps listed
+- [ ] File saved to `docs/consultations/`
+- [ ] Committed to git
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️