Create CLAUDE.md Locations

[4eckd]

Create CLAUDE.md Locations

• Path: Root directory (CLAUDE.md)
• Based on organization needs

Claude Code Instructions for Fused Gaming Organization

Organization Context

• Gaming community organization
• 5+ active projects
• Distributed team with strong governance framework
• Focus on transparency, automation, and community engagement

Repository Role

This is the .github organization repository serving as:

• Central governance hub
• Label definition source (83 labels in .github/labels.yml)
• Workflow automation center (6 GitHub Actions)
• Documentation central
• Issue/PR template provider

Critical Files (DO NOT MODIFY WITHOUT REVIEW)

1. .github/labels.yml - Organization-wide label definitions (syncs to all repos)
2. .github/GOVERNANCE.md - Governance framework
3. .github/GOALS.md - Strategic goals and OKRs
4. .github/workflows/sync-labels.yml - Label synchronization

Workflow Automation

6 GitHub Actions workflows:

1. sync-labels.yml - Syncs labels org-wide (weekly + on push)
2. auto-label-issues.yml - Auto-labels based on content
3. add-to-project.yml - Adds items to project board
4. goal-alignment-check.yml - Checks strategic alignment
5. quarterly-okr-tracker.yml - Tracks OKR progress
6. play_tictactoe.yml - Interactive game

Standard Processes

When working with this repository:

For Commits

• See: docs/processes/COMMIT_CHECKLIST.md
• Use conventional commits format
• Reference issues
• Co-author with Claude: Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

For Pull Requests

• See: docs/processes/PULL_REQUEST_CHECKLIST.md
• Use PR template (.github/PULL_REQUEST_TEMPLATE.md)
• Test label sync before merging label changes

For Issues

• See: docs/processes/ISSUE_CHECKLIST.md
• Use appropriate issue template
• Auto-labeling handles priority/type/area

Label System

83 labels organized in categories:

• Priority: 🚨CRITICAL, 🔴HIGH, 🟠MEDIUM, 🟢LOW, ℹ️INFO
• Projects: ☕DRIFT, 💎GAMBAREWARDS, 🔫GAMBARELOAD, 🔬VLN, 🏆LEADERBOARDS
• Teams: 👷DEV, 💉DEVOPS, 🎨DESIGN, 🌐DOMAIN, ⚖️LEGAL, 💰STAKE-HOLDERS
• Status: ✅COMPLETED, 🗺️PLANNED, 🐌BLOCKED, 🎯IN-PROGRESS, ⏳WAITING
• Deployment: 🚀READY-FOR-DEPLOY, ✅PRODUCTION, 🔄STAGING
• Security: 🔒SECURITY, 🛡️AUDIT, 🔐COMPLIANCE
• Transparency: 📢ANNOUNCEMENT, 📝CHANGELOG, 🎮PLAYER-IMPACT, 💥BREAKING-CHANGE

Testing Requirements

Before committing changes:

1. Validate YAML files (workflows, labels.yml, issue templates)
2. Check markdown links
3. Test workflow changes in fork first
4. For label changes: test sync on single repo before org-wide

Documentation Standards

• Markdown for all documentation
• 120 character line width
• Auto-format with Prettier
• Link to related docs using relative paths
• Update docs/catalog.yml when adding new docs

Decision Authority

• Routine (docs, fixes): Individual contributor
• Significant (workflows, templates): 2+ core team
• Strategic (labels, governance): Community input + 3+ core team

Getting Help

• Governance questions: See .github/GOVERNANCE.md
• Process questions: See docs/processes/
• Technical questions: See docs/technical/
• Setup questions: See docs/setup/

Common Tasks

1. Update labels: Edit .github/labels.yml, commit, push (auto-syncs)
2. Add workflow: Create in .github/workflows/, document in workflows/README.md
3. Update goals: Edit .github/GOALS.md, ensure OKR tracker compatibility
4. New issue template: Create in .github/ISSUE_TEMPLATE/, update config.yml

Best Practices

• Always read existing docs before making changes
• Keep documentation DRY (Don't Repeat Yourself) - link instead of duplicate
• Update catalog when adding documentation
• Test automation changes thoroughly
• Consider org-wide impact of label/workflow changes