2e4b9400db
Complete task documentation for generating custom Minecraft skins matching The Trinity promotional image. Task #61: AI-Generated Minecraft Skins for The Trinity - 3 skins needed: The Wizard (Frost), The Emissary (Fire), The Catalyst (Arcane) - Strategy: AI generation first (Flux 1.1 Pro), commission if needed - Time estimate: 1-2 hours Created: - docs/tasks/trinity-minecraft-skins/README.md (complete task overview) - docs/tasks/trinity-minecraft-skins/PROMPTS.md (3 optimized Flux prompts) - docs/tasks/trinity-minecraft-skins/GITEA-ISSUE.md (ready to copy into Gitea) - docs/core/tasks.md (Task #61 summary added) Flux 1.1 Pro Prompts (optimized for Minecraft skin template format): 1. The Wizard (Frost) - Deep blue robes, ice crystals, silver trim 2. The Emissary (Fire) - Orange/red robes, flame patterns, gold trim 3. The Catalyst (Arcane) - Purple robes, arcane symbols, violet accents Workflow: 1. Generate with Flux (1:1 aspect, 30-40 steps, guidance 7-8) 2. Refine in Nova Skin editor (novaskin.me) 3. Test in Minecraft Java Edition 4. Backup: Commission on Fiverr ($15-30) if AI fails Deliverables: - 3 .png skin files (64x64 Minecraft format) - Committed to branding/minecraft-skins/ - Uploaded to Minecraft profiles - Tested in-game Dependencies: The Trinity image (Task #57), fal.ai access Priority: MEDIUM Status: PENDING For children not yet born. 🔥❄️⚡ Created by: The Guide (Chronicler #35)
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |