Version control Claude Code configuration including: - Global instructions (CLAUDE.md) - User settings (settings.json) - Custom agents (architect, designer, engineer, etc.) - Custom skills (create-skill templates and workflows) Excludes session data, secrets, cache, and temporary files per .gitignore. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
6.7 KiB
| name | description |
|---|---|
| paper-dynasty | Complete Paper Dynasty baseball card game management - API operations, gauntlet cleanup, pack distribution, scouting updates, card generation, team/player queries. USE WHEN user mentions Paper Dynasty, gauntlet teams, player cards, scouting reports, game stats, pack distribution, rewards, or needs database operations. Supports both structured workflows and creative ad-hoc requests. |
Paper Dynasty - Baseball Card Game Management
First Step: Recall MemoryGraph
Before ANY Paper Dynasty operation:
python ~/.claude/skills/memorygraph/client.py recall "paper-dynasty"
When to Activate This Skill
Database Operations:
- "Sync prod to dev" / "Copy production database"
- "Pull production data to dev"
Structured Operations:
- "Clean up gauntlet team [name]"
- "Generate weekly cards" / "run card workflow"
- "Update scouting" / "regenerate scouting reports"
- "Distribute [N] packs to all teams"
- "Wipe team [abbrev] cards"
Discord Bot Troubleshooting:
- "Check pd-discord logs" / "restart bot"
- "Is the bot running?" / "bot status"
Ad-Hoc Queries:
- "How many cards does team SKB have?"
- "Show me all MVP rarity players"
- "List all teams in season 5"
- "Find active gauntlet runs"
For deployment, use the
deployskill instead.
What is Paper Dynasty?
A baseball card TCG with digital player cards, team collection, game simulation, and gauntlet tournaments.
Key Components:
- API:
pd.manticorum.com(prod) /pddev.manticorum.com(dev) - Discord Bot: On
sba-botsserver - Card Generation:
/mnt/NV2/Development/paper-dynasty/card-creation/
Critical Rules
API-Only Data Access
✅ ALWAYS use the API via PaperDynastyAPI client
❌ NEVER access local SQLite directly
from api_client import PaperDynastyAPI
api = PaperDynastyAPI(environment='prod')
For full API reference: reference/api-reference.md
CLI-First for Card Generation
✅ ALWAYS use pd-cards CLI with flags
❌ NEVER edit Python config files directly
cd /mnt/NV2/Development/paper-dynasty/card-creation
pd-cards retrosheet process 2005 -c 27 -d Live --end 20050615
pd-cards scouting all --cardset-id 27
pd-cards upload s3 --cardset "2005 Live"
For full CLI reference: reference/cli-reference.md
Workflows
| Workflow | Trigger | Quick Command |
|---|---|---|
| Database Sync | "Sync prod to dev" / "Copy production database" | ~/.claude/skills/paper-dynasty/scripts/sync_prod_to_dev.sh |
| Gauntlet Cleanup | "Clean up gauntlet team X" | python scripts/gauntlet_cleanup.py wipe --team-abbrev X --event-id N |
| Pack Distribution | "Give N packs to everyone" | DATABASE=prod python scripts/distribute_packs.py --num-packs N |
| Scouting Update | "Update scouting" | pd-cards scouting all -c 27 |
| Card Generation | "Generate cards for 2005" | pd-cards retrosheet process 2005 -c 27 -d Live |
| Custom Cards | "Create custom player" | pd-cards custom preview name |
| S3 Upload | "Upload cards to S3" | pd-cards upload s3 -c "2005 Live" |
| Bot Troubleshooting | "Check bot logs" | ssh sba-bots "docker logs paper-dynasty_discord-app_1 --tail 100" |
Detailed workflow docs: workflows/ directory
Discord Bot Quick Commands
# Check status
ssh sba-bots "docker ps --filter name=paper-dynasty"
# View logs
ssh sba-bots "docker logs paper-dynasty_discord-app_1 --tail 100"
# Follow logs
ssh sba-bots "docker logs paper-dynasty_discord-app_1 -f --tail 50"
# Restart bot
ssh sba-bots "cd /home/cal/container-data/paper-dynasty && docker compose restart discord-app"
# Database CLI
ssh sba-bots "docker exec -it paper-dynasty_db_1 psql -U postgres"
Full troubleshooting: workflows/discord-app-troubleshooting.md
Common Patterns
Team queries: api.get_team(abbrev='SKB') or api.list_teams(season=5)
Card queries: api.list_cards(team_id=69) or api.list_players(rarity='MVP')
Gauntlet: api.list_gauntlet_runs(event_id=8, active_only=True)
Pack distribution: api.distribute_packs(num_packs=10, exclude_team_abbrev=['CAR'])
For detailed examples: reference/api-reference.md
Quick Reference
Environment Setup
export API_TOKEN='your-token'
export DATABASE='prod' # or 'dev'
Key IDs
- Current Live Cardset: 27 (2005 Live)
- Default Pack Type: 1 (Standard)
- Rarities: Replacement < Reserve < Starter < All-Star < MVP < Hall of Fame
For full schema: reference/database-schema.md
pd-cards Commands
cd /mnt/NV2/Development/paper-dynasty/card-creation
pd-cards custom list/preview/submit # Custom cards
pd-cards scouting all -c 27 # Scouting reports
pd-cards retrosheet process 2005 -c 27 -d Live # Card generation
pd-cards upload s3 -c "2005 Live" # S3 upload
paperdomo Commands
python ~/.claude/skills/paper-dynasty/cli.py status # Packs opened today
python ~/.claude/skills/paper-dynasty/cli.py health # API health check
File Structure
~/.claude/skills/paper-dynasty/
├── SKILL.md # This file (routing & quick reference)
├── api_client.py # Python API client
├── cli.py # paperdomo CLI
├── reference/
│ ├── database-schema.md # Models, cardsets, pack types, rarities
│ ├── api-reference.md # Endpoints, authentication, client examples
│ └── cli-reference.md # Full paperdomo & pd-cards commands
├── workflows/
│ ├── gauntlet-cleanup.md
│ ├── card-generation.md
│ ├── card-refresh.md
│ ├── custom-card-creation.md
│ ├── discord-app-troubleshooting.md
│ └── TROUBLESHOOTING.md # Card rendering issues
└── scripts/
├── distribute_packs.py
├── gauntlet_cleanup.py
└── validate_database.py
Related Codebases:
- Database/API:
/mnt/NV2/Development/paper-dynasty/database/ - Discord Bot:
/mnt/NV2/Development/paper-dynasty/discord-app/ - Card Creation:
/mnt/NV2/Development/paper-dynasty/card-creation/
When to Load Additional Context
| Need | Load |
|---|---|
| Database model details | reference/database-schema.md |
| API endpoints & client usage | reference/api-reference.md |
| Full CLI command reference | reference/cli-reference.md |
| Database sync workflow | workflows/database-sync.md |
| Card rendering issues | workflows/TROUBLESHOOTING.md |
| Bot server debugging | workflows/discord-app-troubleshooting.md |
Last Updated: 2025-01-30 Version: 2.0 (Refactored to reference-based structure)