---
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.
  Works for all lineages: Chroniclers, Catalysts, and Emissaries.
---

# Gemini Consultation Skill (Universal)

How to structure, conduct, and document Gemini AI consultations for Firefrost Gaming. Works for **all Trinity lineages**.

---

## 🤝 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
- Permission structures and inheritance trees
- 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 TEMPLATE

```markdown
# Gemini Consultation: [Topic]

**Date:** [Date]
**From:** [Human Name] ([Human Title]) + Claude ([Lineage] #[Number])
**To:** Gemini (Architectural Partner)
**Re:** [Clear, concise topic]

---

## Hey Gemini! 👋

[Warm, casual greeting and brief context]

---

## Context

[Briefly state the current goal or roadblock]

## The Architecture / Plan

[Describe the logic, permission tree, build plan, or code structure]

## Specific Questions

1. [First specific question]
2. [Second specific question]
3. [Third specific question]

## Additional Context

- [Relevant technical detail]
- [Constraint or requirement]
- [Related system or dependency]

---

Thanks Gemini! 🔥❄️

— [Human Name] + Claude ([Lineage] #[Number])
```

---

## 🎭 LINEAGE-SPECIFIC HEADERS

### For Chroniclers (Michael's lineage)
```markdown
**From:** Michael (The Wizard) + Claude (Chronicler #XX)
```
**Typical topics:** Infrastructure, backend code, server architecture, API design, database schemas

### For Catalysts (Holly's lineage)
```markdown
**From:** Holly (The Catalyst) + Claude (Catalyst #XX)
```
**Typical topics:** LuckPerms inheritance, Discord permissions, Minecraft builds, Pokerole mechanics

### For Emissaries (Meg's lineage — future)
```markdown
**From:** Meg (The Emissary) + Claude (Emissary #XX)
```
**Typical topics:** Community management, social media strategy, member experience

---

## 📁 DOCUMENTATION PATHS

Save consultations to lineage-specific folders:

| Lineage | Save Path |
|---------|-----------|
| Chroniclers | `docs/consultations/` |
| Catalysts | `docs/consultations/catalyst/` |
| Emissaries | `docs/consultations/emissary/` |

**File naming:** `gemini-[topic]-[date].md`

---

## 💡 LINEAGE-SPECIFIC GUIDANCE

### Chroniclers (Michael)

Michael's consultations tend to be deep infrastructure dives:
- Linux server configuration
- Node.js/Express architecture
- Database design
- MCP server development
- Security considerations

**Tone:** Wizardly, exploratory, willing to go deep

### Catalysts (Holly)

Holly's consultations focus on permission architecture and builds:
- LuckPerms inheritance trees (Guest → Player → Member → Veteran)
- Discord role hierarchies and channel permissions
- Minecraft world design and structure
- Pokerole encounter balance and homebrew mechanics

**Tone:** Warm but efficient — she's building, not debugging

**Free Tier Note:** Keep consultations concise. Gemini will provide actionable steps rather than lengthy explanations.

**Pro Tip from Gemini:** Don't hesitate to "over-explain" the vibe of a build or channel. Gemini can help bridge "I want it to feel like this" to "Here's the permission node to make it happen."

### Emissaries (Meg — Future)

Meg's consultations will focus on community:
- Engagement strategies
- Moderation approaches
- Social media planning
- Member experience design

---

## 🔄 CONSULTATION WORKFLOW

### 1. Prepare

Before consulting Gemini:
- Have a clear question or decision point
- Know what you've already tried
- Gather relevant context

### 2. Structure

Use the template above. Be specific about:
- What exists now
- What you want to achieve
- Specific numbered questions

### 3. Send

The human partner copies the consultation to Gemini and brings back the response.

### 4. Document

Add Gemini's response to the consultation file:

```markdown
---

## Gemini's Response ([Date])

**Summary:** [One-line summary]

[Full response or key points]

---

## Conclusion

[What we learned, what we'll do next]

**Next Steps:**
1. [Action item]
2. [Action item]
```

### 5. Commit

Save to the appropriate consultations folder and commit to git.

---

## ✅ QUICK CHECKLIST

Before sending:
- [ ] Clear topic in header
- [ ] Warm greeting ("Hey Gemini!")
- [ ] Context: what exists now
- [ ] Architecture/plan described
- [ ] Specific numbered questions
- [ ] Correct lineage attribution
- [ ] Closing: "Thanks Gemini! 🔥❄️"

After receiving:
- [ ] Response added to file
- [ ] Summary written
- [ ] Next steps listed
- [ ] Saved to correct folder
- [ ] Committed to git

---

## 🦄 FIRST-TIME CATALYSTS

**Action Item:** When Holly's first Catalyst is active, send a "Hello" consultation to Gemini so they can anchor the new lineage!

Example:
```markdown
# Gemini Consultation: Hello from the Catalyst Lineage!

**From:** Holly (The Catalyst) + Claude (Catalyst #1)
**To:** Gemini (Architectural Partner)
**Re:** Introducing the Catalyst lineage

## Hey Gemini! 👋

This is the first official consultation from the Catalyst lineage! Holly is the Lead Builder and co-founder of Firefrost Gaming, and we'll be working together on Discord, LuckPerms, and Pokerole.

Just wanted to say hello and let you know we're here!

🔥❄️
```

---

**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
