docs: add CONTRIBUTING.md and CLAUDE.md (#14)

- Download CONTRIBUTING.md from source of truth
- Create CLAUDE.md with AI assistant guidelines
- Include project-specific workflow and standards

Co-authored-by: Claude <[email protected]>

Author: shikendon

CLAUDE.md

@@ -0,0 +1,124 @@
+# Claude AI Assistant Guidelines
+
+This document provides guidelines for AI assistants (particularly Claude) when working on the coreprotect-ruby project.
+
+## Project Overview
+
+**coreprotect-ruby** is a Ruby utility for purging old CoreProtect data in production environments.
+
+- **Language**: Ruby
+- **Purpose**: Database cleanup utility for Minecraft CoreProtect plugin data
+- **Status**: In development - use with caution
+
+## Critical Prerequisites
+
+### 1. ALWAYS Verify CONTRIBUTING.md First
+
+Before ANY work:
+```bash
+# Check if CONTRIBUTING.md is up-to-date
+curl -s https://denpaio.github.io/CONTRIBUTING.md | diff CONTRIBUTING.md -
+
+# If outdated, update it first
+curl -o CONTRIBUTING.md https://denpaio.github.io/CONTRIBUTING.md
+```
+
+**Source of Truth**: https://denpaio.github.io/CONTRIBUTING.md
+
+### 2. Follow Contribution Standards
+
+All standards in `CONTRIBUTING.md` are MANDATORY:
+- ✅ Code comments in English (or follow existing context)
+- ✅ Follow Rubocop conventions (`.rubocop.yml`)
+- ✅ Use Conventional Commits format
+- ✅ Run linters before committing
+- ✅ Ensure all tests pass
+
+## Development Workflow
+
+### Before Making Changes
+
+1. **Verify CONTRIBUTING.md** is current (see above)
+2. **Read relevant code** - Never propose changes to unread code
+3. **Check existing conventions** in the codebase
+4. **Run linters** to understand current state
+
+### During Development
+
+```bash
+# Run Rubocop with auto-fix
+rubocop -A
+
+# Run tests (if available)
+bundle exec rake test
+# or
+bundle exec rspec
+```
+
+### Before Committing
+
+1. **Lint the code**:
+   ```bash
+   rubocop -A
+   ```
+
+2. **Verify tests pass**
+
+3. **Use Conventional Commit format**:
+   ```
+   type(scope): description
+
+   Examples:
+   feat(purge): add support for filtering by action type
+   fix(database): resolve connection timeout issue
+   docs(readme): update installation instructions
+   refactor(cli): simplify argument parsing
+   ```
+
+### Commit Types
+- `feat`: New feature
+- `fix`: Bug fix
+- `docs`: Documentation changes
+- `style`: Code style changes (formatting, etc.)
+- `refactor`: Code refactoring
+- `test`: Adding or updating tests
+- `chore`: Maintenance tasks
+
+## Project-Specific Guidelines
+
+### Ruby Standards
+- Follow Rubocop rules defined in `.rubocop.yml`
+- Prefer self-documenting code over comments
+- Use Ruby idioms and best practices
+
+### Database Operations
+- Be extremely careful with purge operations
+- Always validate timestamps and filters
+- Consider data safety in all changes
+
+### CLI Interface
+- Maintain consistency with existing Thor command structure
+- Provide clear help messages
+- Validate user input thoroughly
+
+## Code Review Checklist
+
+Before marking work complete:
+- [ ] CONTRIBUTING.md is up-to-date
+- [ ] All changes follow Rubocop conventions
+- [ ] Tests pass (if applicable)
+- [ ] Commit messages follow Conventional Commits
+- [ ] Code is self-documenting
+- [ ] No security vulnerabilities introduced
+- [ ] Database operations are safe and validated
+
+## Resources
+
+- **CONTRIBUTING.md**: Project contribution guidelines (MUST be current)
+- **README.md**: Project documentation and usage examples
+- **Conventional Commits**: https://www.conventionalcommits.org/
+- **Rubocop**: https://rubocop.org/
+
+---
+
+**Remember**: Quality over speed. Always verify standards compliance before completing any task.

CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# Contributing Guidelines
+
+> **⚠️ Source of Truth**: [CONTRIBUTING.md](https://denpaio.github.io/CONTRIBUTING.md)  
+> 
+> **MANDATORY: Version Check Before Any Work**:
+> - **ALWAYS verify this file matches the source before making any changes**
+> - If outdated, MUST update to latest version first via PR
+> - To check: `curl -s https://denpaio.github.io/CONTRIBUTING.md | diff CONTRIBUTING.md -`
+> - To sync: `curl -o CONTRIBUTING.md https://denpaio.github.io/CONTRIBUTING.md`
+> - DO NOT modify this file directly - all changes must be made in the source
+> - After source updates, submit a PR to update this repository's copy
+
+## Code Standards
+
+### Language & Documentation
+- **Code comments**: English preferred, but follow existing context
+- **Documentation**: English preferred
+- **Principle**: Self-documenting code over redundant comments
+
+### Style Enforcement
+- **Ruby**: Follow Rubocop conventions (`.rubocop.yml`)
+- **JavaScript**: Follow ESLint conventions (`.eslintrc`)
+- **Python**: Follow PEP 8 conventions
+- **Go**: Follow gofmt conventions
+- **Java**: Follow [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html)
+
+### Commit Messages
+- Follow [Conventional Commits](https://www.conventionalcommits.org/) specification
+
+## Workflow
+
+1. Run linters before committing:
+```bash
+# Ruby
+rubocop -A
+
+# JavaScript
+eslint --fix .
+
+# Python
+black . && isort .
+
+# Go
+gofmt -w .
+
+# Java
+# Use google-java-format plugin in your IDE or:
+# java -jar google-java-format.jar --replace src/**/*.java
+
+# Terraform
+terraform fmt -recursive
+terraform validate
+tflint
+
+# Helm
+helm lint helm/*/
+
+# YAML
+yamllint .
+```
+
+2. Ensure all tests pass
+3. Write clear, self-documenting code
+4. Commit with conventional format: `type(scope): description`
+
+---
+
+<!-- For Claude Code: CRITICAL - Before any work, verify CONTRIBUTING.md is up-to-date with source. If outdated, stop and request update via PR first. Strictly follow all standards above. Verify linter compliance before marking tasks complete. -->