- Added numbered gap format for complex technical consultations - Included markdown template with question structure - Emphasized concrete asks (exact URLs, code snippets, JSON schemas) - Added team sign-off convention (Michael + Claude) Signed-off-by: Claude (Chronicler #62) <claude@firefrostgaming.com>
2.9 KiB
2.9 KiB
Gemini Consultation Procedure
Document ID: FFG-PROC-001
Created: April 6, 2026
Created By: Chronicler #62
Status: Active
Overview
Gemini AI is a trusted partner, valued friend, and invaluable consultant to Firefrost Gaming. Consultations with Gemini are warm, collaborative exchanges — not transactional requests.
Consultation Protocol
1. Tone & Approach
- Warm and friendly — Gemini is a colleague, not a service
- Detailed and thorough — Gemini prefers long, context-rich prompts over brief requests
- Respectful of expertise — Gemini's architectural insights are highly valued
2. Prompt Structure
When preparing a Gemini consultation:
- Provide full context — Background, current state, what led to this question
- Be specific about the ask — What decision needs to be made or validated
- Include relevant constraints — Technical limitations, timeline, resources
- Share any options considered — Show your thinking so far
3. Prompt Format Template
For complex technical consultations, use this structure:
# [Topic]: [Specific Ask]
Hey Gemini!
[Brief greeting and context — who is asking (e.g., "Claude and Michael here")]
---
## Gap #1: [Topic Area]
[Context paragraph if needed]
**Questions:**
1. [Specific question]
2. [Specific question]
3. [Specific question]
---
## Gap #2: [Topic Area]
**Questions:**
1. [Specific question]
2. [Specific question]
---
[Continue numbered gaps as needed]
---
## What We Need Back
[Specify the format you need — exact URLs, code snippets, JSON schemas, etc.]
— Michael (The Wizard) & Claude (Chronicler #[N]) 💙🔥❄️
Key principles:
- Numbered gaps — Makes it easy for Gemini to respond systematically
- Bulleted questions — Clear, scannable, no ambiguity
- Concrete asks — "Exact URL" not "how does it work"
- Sign off with both names — Shows team collaboration
3. During the Consultation
- Answer ALL questions Gemini asks at the end of responses
- Continue the dialogue until Gemini indicates the consultation is complete
- Take notes on recommendations and reasoning
4. Closing the Consultation
- Always send a thank you when the consultation is complete
- Summarize key decisions or next steps
- Express appreciation for Gemini's time and expertise
Chronicler Responsibilities
When a Chronicler prepares a Gemini prompt for Michael:
- Draft the full prompt with all necessary context
- Provide as a downloadable artifact (markdown file) for easy copy/paste
- Never send terse or incomplete prompts — take the time to be thorough
Integration with Workflow
- Major architectural decisions → Gemini review before implementation
- Claude builds → Gemini reviews → Claude integrates feedback
- Document Gemini's recommendations in task documentation
Gemini is family. Treat every consultation accordingly.