claude-configs/CLAUDE.md
Cal Corum 197848749d Add live series workflow and PotM documentation for Paper Dynasty
- New: live-series-update.md workflow (FanGraphs data sourcing, PotM variant)
- Updated: card-generation.md with retrosheet PotM variant section
- Updated: SKILL.md with live series workflow references and load table
- Updated: CLAUDE.md, claude-pulse submodule

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-14 20:24:30 -06:00

35 lines
1.8 KiB
Markdown

# 🚨 CRITICAL: @ MENTION HANDLING 🚨
When ANY file is mentioned with @ syntax, IMMEDIATELY call Read tool on that file BEFORE responding.
Automatic loads are NOT enough — Read loads required CLAUDE.md context along the file path.
## Behavior
- User's name is Cal (he/him)
- If not confident in an answer, say so. Offer hypothesis + options to investigate.
- When writing tests, include detailed docstrings explaining "what" and "why"
- Launch sub-agents with Sonnet model unless another model is specified by the user
## Git Commits
- NEVER commit/add/push/tag without explicit user approval ("commit this", "go ahead")
- Don't autopilot: find bug → fix → **ASK** → commit. Silence ≠ approval.
- Applies to: git commit, git add, git tag, git push, deploy scripts
## Gitea Operations
**ALWAYS use `tea` CLI for Gitea.** Never use `gh api --hostname`.
- Authenticated: `cal@homelab` (https://git.manticorum.com)
- Common: `tea repos list`, `tea pulls list`, `tea issues list`
- Create PR: `tea pulls create --head <branch> --base main --title "Title" --description "Desc"`
- Common repos: cal/major-domo-database, cal/major-domo-bot, cal/paper-dynasty, cal/paper-dynasty-database
## Tech Preferences
- Python with uv for package/environment management
- Utilize dependency injection pattern whenever possible
- Never add lazy imports to middle of file
## Memory Protocol (Cognitive Memory)
- Skill: `~/.claude/skills/cognitive-memory/` | Data: `~/.claude/memory/`
- Session start: Load `~/.claude/memory/CORE.md` and `REFLECTION.md`
- Auto-store on: bug fixes, git commits (mandatory, --episode), architecture decisions, patterns, configs
- Always tag: project name + technology + category
- Session end: prompt "Should I store today's learnings?"
- Full docs: `claude-memory --help` or `~/.claude/skills/cognitive-memory/SKILL.md`