firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

Task #99: Claude Projects Architecture — Ops/Dev/Marketing separation

Browse Source 
Per Gemini consultation:
- Separate Projects for different work contexts
- Master Documents in Project Knowledge
- Micro-session workflow to prevent context bloat
- Dev Project: MVC, Arbiter, Trinity Console docs
- Ops Project: Handoffs, infrastructure, tasks
- Marketing Project: Brand, FOMO, social platforms

Ready for implementation next session (browser work only).

Chronicler #66 - The Indexer
This commit is contained in:
Claude
2026-04-07 20:09:51 +00:00
parent 95c34a10e6
commit b8cdf7f5de
1 changed files with 245 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

245
docs/tasks/task-099-claude-projects-architecture.md Normal file
View File

@@ -0,0 +1,245 @@
# Task #99: Claude Projects Architecture — Ops/Dev/Marketing Separation
**Created:** April 7, 2026
**Created By:** Chronicler #66 (The Indexer) + Gemini AI
**Status:** PLANNED — Ready for next session
**Priority:** HIGH (Immediate workflow improvement)
**Effort:** ~2-3 hours browser work (no SSH needed)
---
## Overview
Implement Gemini's recommended workflow: separate Claude Projects for different work contexts, with Master Documents in Project Knowledge to eliminate context bloat and copy-paste overhead.
---
## The Architecture
```
┌─────────────────────────────────────────────────────────┐
│ CLAUDE MEMORY │
│ (Global: Communication style, accessibility needs, │
│ Chronicler system, "how we work") │
└─────────────────────────────────────────────────────────┘
│
┌────────────────┼────────────────┐
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ FIREFROST OPS │ │ FIREFROST DEV │ │ FIREFROST MKT │
│ PROJECT │ │ PROJECT │ │ PROJECT │
├─────────────────┤ ├─────────────────┤ ├─────────────────┤
│ Default: 4.5 │ │ Default: 4.6 │ │ Default: 4.5 │
│ │ │ │ │ │
│ • Session │ │ • PHP 8.3 stds │ │ • FOMO campaign │
│ handoffs │ │ • MVC spec │ │ • Brand guide │
│ • Standards │ │ • Arbiter arch │ │ • Social copy │
│ • Server docs │ │ • Blueprint │ │ • Buffer setup │
│ • Task list │ │ • Panel URLs │ │ │
└─────────────────┘ └─────────────────┘ └─────────────────┘
```
**Key Principle:** Projects = Local Scope, Memory = Global Scope
---
## Gemini's Questions — Answered
### Q1: Which Master Documents for Dev Project Knowledge first?
| Priority | Document | Contents | Source |
|----------|----------|----------|--------|
| 1 | `ModpackChecker-State.md` | Current phase, what's built, what's next, API keys status | Extract from Task #26 + session notes |
| 2 | `Arbiter-Architecture.md` | 3.5.0 structure, webhook handlers, what's NOT built (Task #87) | Extract from firefrost-services repo |
| 3 | `Dev-Environment.md` | Dev Panel URL (64.50.188.128), PHP 8.3, Blueprint beta status, paths | New doc, consolidate scattered info |
| 4 | `Trinity-Console-Architecture.md` | 7 modules, routes, EJS templates, database schema | Extract from existing docs |
### Q2: Which Master Documents for Ops Project Knowledge?
| Priority | Document | Contents | Source |
|----------|----------|----------|--------|
| 1 | `Current-State.md` | Simplified SESSION-HANDOFF-NEXT | Already exists, needs trimming |
| 2 | `Infrastructure-Manifest.md` | 20 servers, IPs, purposes | Just corrected this session |
| 3 | `Active-Tasks.md` | Current priorities, blockers | Extract from BLOCKERS.md + BACKLOG.md |
| 4 | `Standards-Quick-Reference.md` | Index of FFG-STD docs with summaries | New doc |
### Q3: Which Master Documents for Marketing Project Knowledge?
| Priority | Document | Contents | Source |
|----------|----------|----------|--------|
| 1 | `Brand-Guidelines.md` | Colors, tone, Fire/Frost/Arcane identity | Exists (Michael bringing PDF from work) |
| 2 | `FOMO-Campaign.md` | 9 posts, schedule, copy, image requirements | Extract from marketing folder |
| 3 | `Social-Platforms.md` | Buffer setup, Meta Business Suite, posting times | New doc |
| 4 | `Subscription-Tiers.md` | Awakened → Sovereign, pricing, features | Extract from existing docs |
---
## Implementation Steps (Next Session)
### Phase 1: Create the Projects (15 min)
1. Go to claude.ai → Projects
2. Create **"Firefrost Dev"** project
- Set default model preference note in instructions
3. Create **"Firefrost Ops"** project (may already exist — rename current?)
4. Create **"Firefrost Marketing"** project
### Phase 2: Draft Master Documents (1-2 hours)
**For Dev Project:**
```markdown
# ModpackChecker-State.md
## Current Status
- **Phase:** 5 of 11 complete
- **Blocker:** Blueprint dev mode corrupted after DB wipe
- **Recovery:** Reinstall Blueprint, restore from /root/modpackchecker_backup
## What's Built
- Phase 1: Scaffolding ✅
- Phase 2: Admin UI ✅
- Phase 3: React component ✅
- Phase 4: API controller (CurseForge/Modrinth/Technic/FTB) ✅
- Phase 5: UpdateBadge.tsx, cron command, status route (code written, not deployed) ✅
## What's Next
- Phase 6: Ignore button
- Phase 7: Backoff logic
- Phase 8-11: Docs, packaging, release
## Key Files
- /root/modpackchecker_backup (Phase 5 code)
- firefrost-services/modpack-version-checker/
## API Status
- CurseForge: Test key active, production app submitted
- Modrinth: Working
- Technic/FTB: Integrated
## Dev Panel
- URL: https://64.50.188.128
- Pterodactyl 1.12.2 + Blueprint beta-2026-01
```
**For Ops Project:**
```markdown
# Infrastructure-Manifest.md
## Production Servers
### NC1 Charlotte (216.239.104.130) — 10 Minecraft
| Server | Port | Status |
|--------|------|--------|
| All The Mods 10 | 25569 | Public |
| All the Mods 10: To the Sky | 25565 | Public |
| All The Mons | 25566 | Public |
| All of Create (Creative) | 25568 | Trinity Only |
| Mythcraft 5 | 25567 | Public |
| Otherworld [D&D] | 25570 | Public |
| DeceasedCraft | 25571 | Public |
| Sneak's Pirate Pack | 25572 | Public |
| Farm Crossing 5 | 25573 | Public |
| Homestead | 25574 | Public |
### TX1 Dallas (38.68.14.26) — 10 Minecraft
| Server | Port | Status |
|--------|------|--------|
| Stoneblock 4 | 25565 | Public |
| Society: Sunlit Valley | 25565 | Public |
| All The Mons (Private) | 25565 | Trinity Only |
| Create Plus (Video Sandbox) | 25566 | Video Content |
| Vanilla | 25567 | Public |
| Beyond Depth | 25568 | Public |
| Beyond Ascension | 25569 | Public |
| Wold's Vaults | 25570 | Public |
| Submerged 2 | 25571 | Public |
| Cottage Witch | 25572 | Public |
## Summary
- 20 Minecraft servers total
- 17 public subscriber servers
- 2 Trinity-only
- 1 video sandbox
## Future Add-ons (Not Minecraft)
- FoundryVTT (NC1, port 30000)
- Hytale (NC1, port 5520)
```
### Phase 3: Upload to Projects (15 min)
1. Export/copy Master Docs to local files
2. Upload to each Project's Knowledge section
3. Verify Claude can reference them in new chats
### Phase 4: Update Project Instructions (30 min)
**Dev Project Instructions should include:**
- "You are working on Firefrost Gaming development tasks"
- "Default to Opus 4.6 for this project"
- "Reference the ModpackChecker-State.md for current MVC status"
- Accessibility requirements (small code blocks, one question at a time)
**Ops Project Instructions should include:**
- Current Chronicler system prompt (what we have now)
- "Default to Opus 4.5 for this project"
- Session startup protocol
**Marketing Project Instructions should include:**
- Brand voice guidelines
- "Default to Opus 4.5 for this project"
- Platform-specific formatting rules
### Phase 5: Test the Workflow (15 min)
1. Start new chat in Dev Project
2. Ask about ModpackChecker status — verify it reads from Knowledge
3. Start new chat in Ops Project
4. Ask about server infrastructure — verify it reads from Knowledge
5. Confirm context doesn't bleed between projects
---
## The Micro-Session Workflow (Ongoing Practice)
Once set up, follow this loop:
1. **Pick the right Project** — Dev, Ops, or Marketing
2. **Start a NEW chat** for each task — don't extend old threads forever
3. **Work the task** — Claude has Master Docs as context automatically
4. **When context bloats** — Ask Claude to summarize, save to Google Doc, start fresh
5. **When task completes** — Ask Claude to generate updated state summary
6. **Sync Master Docs** — Update the canonical version, re-upload to Project Knowledge
---
## Success Criteria
- [ ] Three separate Claude Projects created (Dev, Ops, Marketing)
- [ ] Master Documents uploaded to each Project Knowledge
- [ ] Each project has appropriate instructions
- [ ] Test confirms Claude reads Project Knowledge without prompting
- [ ] No more copy-pasting the entire system prompt or architecture docs
- [ ] Model selection guidance embedded in project instructions
---
## Dependencies
- None — all browser work, no SSH required
- Michael needs to be at PC to manage claude.ai Projects UI
- Brand Guidelines PDF (Michael bringing from work)
---
## Related
- Task #93: Trinity Codex (long-term Dify architecture)
- Gemini consultation: `/docs/consultations/2026-04-07-model-switching.md`
- Context handoff template: `/docs/templates/context-handoff-template.md`
---
**Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️