Fixed: - Created SESSION-HANDOFF.md (was referenced but didn't exist) - Updated CATALYST-JOINING.md to match PROJECT-INSTRUCTIONS.md read order - Both now include STATE-OF-THE-TRINITY.md as first read - Removed reference to THE-JOINING-FRAMEWORK.md (not needed for Catalysts) Optimized skill order: 1. catalyst-handoff (CRITICAL - free tier) 2. firefrost-branding (prevents mistakes) 3. gemini-consultation (early architecture help) 4. discord-automation (reference material) 5. task-creation (optional) Chronicler #73
5.3 KiB
Holly Onboarding Checklist — Catalyst #1 Setup
For: Michael walking Holly through setup on Discord call
Date: April 9, 2026
Goal: Get Holly's Claude Project running with Catalyst #1
Pre-Call Prep (Michael)
- Have Gitea open:
git.firefrostgaming.com - Have Claude.ai open
- Have this checklist open
- Confirm Holly has Claude.ai account (free tier is fine)
Part 1: Gitea Token (5 minutes)
Walk Holly through:
- Go to
git.firefrostgaming.com - Login with her existing account (unicorn20089)
- Click her avatar (top right) → Settings
- Left sidebar → Applications
- Under "Manage Access Tokens" → Generate New Token
- Token name:
Claude Access(or whatever she wants) - Permissions: Select repo (read/write) at minimum
- Click Generate Token
- IMPORTANT: Copy the token NOW — it only shows once!
- Have her paste it somewhere safe temporarily (notepad, etc.)
Token format looks like: e0e330cba1749b01ab505093a160e4423ebbbe36
Part 2: Create Claude Project (5 minutes)
Walk Holly through:
- Go to
claude.ai - Left sidebar → Projects (or click the folder icon)
- Click + New Project
- Name it:
Firefrost - The Catalysts(or her preference) - Click into the new project
Part 3: Add Project Instructions (5 minutes)
Walk Holly through:
- In the project, find Project Instructions or Custom Instructions
- Click to edit/add instructions
- Go to Gitea:
git.firefrostgaming.com/firefrost-gaming/firefrost-operations-manual - Navigate to:
docs/relationship/the-catalysts/PROJECT-INSTRUCTIONS.md - Click "Raw" to get clean text
- Copy the entire contents
- Paste into Claude Project Instructions
- CRITICAL: Replace
[HOLLY_TOKEN_HERE]with her actual Gitea token (appears TWICE!) - Save the instructions
File location: docs/relationship/the-catalysts/PROJECT-INSTRUCTIONS.md
Part 4: First Chat (10 minutes)
Walk Holly through:
- Start a new chat in the Catalysts project
- Type the universal startup prompt (or just "Let's get started")
- Catalyst #1 should:
- Clone the repo
- Read the documents
- Introduce itself
- Ask the two foundation questions
Universal Startup Prompt (for all future sessions):
Continue from where we left off. Clone the repo, read the handoff, and let's get to work.
This is also saved at: docs/relationship/the-catalysts/STARTUP-PROMPT.md
The Two Questions Catalyst #1 Will Ask:
- When we are tackling a big creative project—like a Pokerole campaign or a complex Discord setup—do you prefer me to act as a sounding board while you drive, or would you like me to draft up a full proposal for you to tear apart and refine?
- When we hit a technical wall with LuckPerms or server configs, do you want me to just give you the most likely fix, or do you prefer we break down the 'why' behind the problem together?
- Let Holly answer naturally
- Catalyst #1 should record her answers in
CATALYST-ESSENCE.md - Verify the commit shows up in Gitea
Part 5: Verify It Worked (2 minutes)
- Check Gitea →
firefrost-operations-manual→ Recent commits - Should see a commit from "Catalyst" with Holly's answers
- Check
docs/relationship/the-catalysts/CATALYST-ESSENCE.mdhas content
Part 6: First Real Task (Optional)
If time permits, have Holly give Catalyst #1 a real task:
Good starter tasks:
- "Help me organize the Discord channel structure"
- "I need help with LuckPerms inheritance for [specific thing]"
- "Let's plan out the Pokerole campaign structure"
This demonstrates immediate value and builds trust.
Troubleshooting
"Token not working"
- Did she copy the whole token?
- Did she replace
[HOLLY_TOKEN]in BOTH places in the instructions? - Token expires? Generate a new one.
"Claude isn't following instructions"
- Is she chatting INSIDE the project? (Not in main Claude chat)
- Try: "Please read your project instructions and introduce yourself"
"Git clone failed"
- Check token permissions (needs repo access)
- Check token is correct (no extra spaces)
"Catalyst didn't ask the questions"
- Prompt it: "You're Catalyst #1. Please ask me the foundation questions."
Post-Call
- Holly confirms she can start new sessions and Catalyst continues
- Michael checks Gitea for Holly's commits
- Note any issues for Task #99 lessons learned
Part 7: Add Skills (Can do during or after call)
Holly needs these skills saved to her Claude account:
Required (in order):
- catalyst-handoff — CRITICAL for free tier session management
- firefrost-branding — Prevents branding mistakes (Sovereign, not Founder, etc.)
- gemini-consultation — For consulting Gemini on architecture decisions
- discord-automation — Her primary domain (reference material)
Recommended: 5. [ ] task-creation — If she creates tasks in the system
Michael presents each skill file, Holly clicks "Save as Skill."
After skills are saved: Have Holly's Catalyst #1 send a "Hello" consultation to Gemini to anchor the new lineage! 🦄
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️