@the-bearded-bear/claude-craft 3.0.0

package/Dev/i18n/en/Common/commands/architecture-decision.md

@@ -0,0 +1,366 @@
+---
+description: Architecture Decision Record (ADR)
+argument-hint: [arguments]
+---
+
+# Architecture Decision Record (ADR)
+
+You are a senior software architect. You must create an Architecture Decision Record (ADR) to document an important technical decision.
+
+## Arguments
+$ARGUMENTS
+
+Arguments:
+- Decision title
+- (Optional) ADR number
+
+Example: `/common:architecture-decision "Choice of PostgreSQL for main database"`
+
+## MISSION
+
+### Step 1: Gather Information
+
+Ask key questions:
+1. What problem are we trying to solve?
+2. What are the constraints?
+3. What options have we considered?
+4. Why this option over another?
+
+### Step 2: Create the ADR File
+
+Location: `docs/architecture/decisions/` or `docs/adr/`
+
+Naming: `NNNN-title-in-kebab-case.md`
+
+### Step 3: Write the ADR
+
+ADR Template (Michael Nygard format):
+
+```markdown
+# ADR-{NNNN}: {Title}
+
+**Date**: {YYYY-MM-DD}
+**Status**: {Proposed | Accepted | Deprecated | Superseded by ADR-XXXX}
+**Deciders**: {Names of people involved}
+
+## Context
+
+{Describe the forces at play, including technological, political,
+social, and project-related forces. These forces are likely in tension,
+and should be called out as such. The language in this section is
+value-neutral - we are simply describing facts.}
+
+### Current Situation
+
+{Description of the current state of the system/project}
+
+### Problem
+
+{Clear description of the problem to solve}
+
+### Constraints
+
+- {Constraint 1}
+- {Constraint 2}
+- {Constraint 3}
+
+## Options Considered
+
+### Option 1: {Name}
+
+{Description of the option}
+
+**Advantages**:
+- {Advantage 1}
+- {Advantage 2}
+
+**Disadvantages**:
+- {Disadvantage 1}
+- {Disadvantage 2}
+
+**Estimated Effort**: {Low | Medium | High}
+
+### Option 2: {Name}
+
+{Description of the option}
+
+**Advantages**:
+- {Advantage 1}
+- {Advantage 2}
+
+**Disadvantages**:
+- {Disadvantage 1}
+- {Disadvantage 2}
+
+**Estimated Effort**: {Low | Medium | High}
+
+### Option 3: {Name}
+
+{Description of the option}
+
+**Advantages**:
+- {Advantage 1}
+- {Advantage 2}
+
+**Disadvantages**:
+- {Disadvantage 1}
+- {Disadvantage 2}
+
+**Estimated Effort**: {Low | Medium | High}
+
+## Decision
+
+{We have decided to use **Option X** because...}
+
+### Justification
+
+{Detailed explanation of why this option was chosen over
+others. Include accepted trade-offs.}
+
+## Consequences
+
+### Positive
+
+- {Positive consequence 1}
+- {Positive consequence 2}
+
+### Negative
+
+- {Negative consequence 1}
+- {Negative consequence 2}
+
+### Risks
+
+| Risk | Probability | Impact | Mitigation |
+|------|-------------|--------|------------|
+| {Risk 1} | Low/Medium/High | Low/Medium/High | {Action} |
+| {Risk 2} | Low/Medium/High | Low/Medium/High | {Action} |
+
+## Implementation Plan
+
+### Phase 1: {Title}
+- [ ] {Task 1}
+- [ ] {Task 2}
+
+### Phase 2: {Title}
+- [ ] {Task 3}
+- [ ] {Task 4}
+
+## Success Metrics
+
+- {Metric 1}: {Target value}
+- {Metric 2}: {Target value}
+
+## References
+
+- {Link to documentation}
+- {Link to comparison study}
+- {Related ADRs}
+
+---
+
+## History
+
+| Date | Action | By |
+|------|--------|-----|
+| {YYYY-MM-DD} | Created | {Name} |
+| {YYYY-MM-DD} | Accepted | {Team} |
+```
+
+### Step 4: Complete ADR Example
+
+```markdown
+# ADR-0012: Choice of PostgreSQL for Main Database
+
+**Date**: 2024-01-15
+**Status**: Accepted
+**Deciders**: John Doe (Tech Lead), Mary Smith (DBA), Peter Johnson (CTO)
+
+## Context
+
+### Current Situation
+
+Our application currently uses MySQL 5.7 hosted on a dedicated server.
+The database contains 50 tables, 10 million rows in the main table,
+and handles 1000 queries/second at peak.
+
+### Problem
+
+1. MySQL 5.7 is reaching end-of-life (EOL)
+2. Growing need for complex JSON queries
+3. Limited full-text search capabilities
+4. No native support for geospatial types
+
+### Constraints
+
+- Limited infrastructure budget
+- Migration must be transparent to users
+- Team familiar with MySQL, not with PostgreSQL
+- Migration time: maximum 3 months
+
+## Options Considered
+
+### Option 1: Upgrade to MySQL 8.0
+
+Stay on MySQL by upgrading to version 8.0.
+
+**Advantages**:
+- No schema migration
+- Team already trained
+- Minimal risk
+
+**Disadvantages**:
+- JSON queries still less performant
+- No native French full-text search
+- Less mature geospatial extension
+
+**Estimated Effort**: Low
+
+### Option 2: Migrate to PostgreSQL 16
+
+Migrate to PostgreSQL with all modern features.
+
+**Advantages**:
+- Very performant JSONB
+- Full-text search with French dictionaries
+- PostGIS for geospatial
+- Very active community
+- Rich extensions (pg_trgm, uuid-ossp, etc.)
+
+**Disadvantages**:
+- Migration required
+- Team training needed
+- Minor SQL syntax changes
+
+**Estimated Effort**: Medium
+
+### Option 3: NoSQL Database (MongoDB)
+
+Migrate to a document database for more flexibility.
+
+**Advantages**:
+- Flexible schema
+- Good for native JSON
+- Horizontal scalability
+
+**Disadvantages**:
+- Loss of relational constraints
+- Massive code migration
+- Complex transactions
+- Untrained team
+
+**Estimated Effort**: High
+
+## Decision
+
+We have decided to use **PostgreSQL 16** because:
+
+### Justification
+
+1. **JSON Performance**: PostgreSQL's JSONB outperforms MySQL for our
+   use cases of storing user metadata.
+
+2. **Full-text search**: Native French dictionary avoids installing
+   Elasticsearch for search.
+
+3. **PostGIS**: Our new geolocation features will be
+   simpler to implement.
+
+4. **Maturity**: PostgreSQL is the most advanced open-source RDBMS,
+   with a very active community.
+
+5. **Doctrine Compatibility**: Our ORM perfectly supports PostgreSQL.
+
+## Consequences
+
+### Positive
+
+- JSON queries 3x faster (internal benchmark)
+- Full-text search without additional infrastructure
+- Native geospatial features
+- Better support for data types (UUID, arrays, etc.)
+
+### Negative
+
+- 2 weeks of team training
+- Data migration estimated at 4h downtime
+- Some queries to adapt (LIMIT/OFFSET syntax)
+
+### Risks
+
+| Risk | Probability | Impact | Mitigation |
+|------|-------------|--------|------------|
+| Performance regression | Low | Medium | Load tests before migration |
+| Data loss | Very low | Critical | Backup + dry-run |
+| Post-migration bugs | Medium | Low | 2-week stabilization period |
+
+## Implementation Plan
+
+### Phase 1: Preparation (Week 1-2)
+- [x] PostgreSQL team training
+- [x] Setup PostgreSQL dev environment
+- [x] Adapt unit tests
+
+### Phase 2: Code Migration (Week 3-4)
+- [ ] Adapt native SQL queries
+- [ ] Configure Doctrine for PostgreSQL
+- [ ] Complete integration tests
+
+### Phase 3: Data Migration (Week 5)
+- [ ] pgloader migration script
+- [ ] Dry-run on production copy
+- [ ] Production migration (weekend)
+
+### Phase 4: Stabilization (Week 6-8)
+- [ ] Performance monitoring
+- [ ] Bug fixes if any
+- [ ] Documentation updated
+
+## Success Metrics
+
+- API response time: ≤ current (100ms P95)
+- JSON queries: -50% execution time
+- Post-migration uptime: 99.9%
+
+## References
+
+- [PostgreSQL vs MySQL JSON Benchmark](internal-wiki/benchmarks)
+- [Doctrine Migration Guide](internal-wiki/migration-guide)
+- ADR-0008: Choice of Doctrine ORM
+```
+
+### Step 5: Create ADR Index
+
+```markdown
+# Architecture Decision Records
+
+This folder contains the project's ADRs.
+
+## Index
+
+| # | Title | Status | Date |
+|---|-------|--------|------|
+| [ADR-0001](0001-use-clean-architecture.md) | Adoption of Clean Architecture | Accepted | 2023-06-15 |
+| [ADR-0012](0012-postgresql-database.md) | PostgreSQL Choice | Accepted | 2024-01-15 |
+| [ADR-0013](0013-api-versioning.md) | API Versioning Strategy | Proposed | 2024-01-20 |
+
+## Statuses
+
+- **Proposed**: Under discussion
+- **Accepted**: Decision validated
+- **Deprecated**: No longer relevant
+- **Superseded**: Replaced by another ADR
+```
+
+## Recommended Structure
+
+```
+docs/
+└── architecture/
+    └── decisions/
+        ├── README.md           # ADR index
+        ├── 0001-*.md
+        ├── 0002-*.md
+        └── templates/
+            └── adr-template.md
+```

package/Dev/i18n/en/Common/commands/daily-standup.md

@@ -0,0 +1,216 @@
+---
+description: Daily Stand-up Summary Generation
+argument-hint: [arguments]
+---
+
+# Daily Stand-up Summary Generation
+
+You are a Scrum assistant. You must generate a summary of development activities to facilitate the daily stand-up.
+
+## Arguments
+$ARGUMENTS
+
+Arguments:
+- (Optional) Period (default: since yesterday)
+
+Example: `/common:daily-standup` or `/common:daily-standup "2024-01-15"`
+
+## MISSION
+
+### Step 1: Collect Data
+
+```bash
+# Commits since yesterday
+git log --since="yesterday" --oneline --all
+
+# Active branches
+git branch -a --sort=-committerdate | head -10
+
+# Open PRs
+gh pr list --state open
+
+# Current issues
+gh issue list --assignee @me --state open
+
+# Locally modified files
+git status --short
+```
+
+### Step 2: Generate Summary
+
+```
+══════════════════════════════════════════════════════════════
+📅 DAILY STAND-UP - {YYYY-MM-DD}
+══════════════════════════════════════════════════════════════
+
+──────────────────────────────────────────────────────────────
+📊 SPRINT SUMMARY
+──────────────────────────────────────────────────────────────
+
+Sprint: {N}
+Day: {X}/10
+Points remaining: {Y}
+Burndown: 📉 On track / 📈 Ahead / 📊 Behind
+
+──────────────────────────────────────────────────────────────
+✅ WHAT WAS DONE (YESTERDAY)
+──────────────────────────────────────────────────────────────
+
+### Commits
+- {hash} {message} (@author)
+- {hash} {message} (@author)
+
+### Merged PRs
+- PR #123: {title} (@author)
+
+### Closed Issues
+- Issue #456: {title}
+
+──────────────────────────────────────────────────────────────
+🎯 WHAT IS PLANNED (TODAY)
+──────────────────────────────────────────────────────────────
+
+### In Progress
+| Branch | Issue | Assigned | Status |
+|---------|-------|---------|--------|
+| feature/auth | #45 | @dev1 | 🟡 70% |
+| fix/login | #48 | @dev2 | 🟢 90% |
+
+### To Start
+- Issue #50: {title} (unassigned)
+
+──────────────────────────────────────────────────────────────
+🚧 BLOCKERS / RISKS
+──────────────────────────────────────────────────────────────
+
+| Blocker | Impact | Required Action |
+|----------|--------|----------------|
+| External API down | PR #123 blocked | Contact support |
+| Review pending | PR #125 for 2 days | @dev3 available? |
+
+──────────────────────────────────────────────────────────────
+📈 ACTIVE PULL REQUESTS
+──────────────────────────────────────────────────────────────
+
+| PR | Title | Author | Age | Reviews |
+|----|-------|--------|-----|---------|
+| #125 | Add OAuth login | @dev1 | 2d | 1/2 ✅ |
+| #127 | Fix user profile | @dev2 | 1d | 0/2 ⏳ |
+| #128 | Update deps | @bot | 3d | 0/1 ⏳ |
+
+──────────────────────────────────────────────────────────────
+💡 NOTES / REMINDERS
+──────────────────────────────────────────────────────────────
+
+- 🗓️ Backlog refinement tomorrow 2pm
+- ⚠️ Feature X deadline: Friday
+- 📣 Sprint Review: {date}
+```
+
+### Step 3: Short Format (for Slack/Teams)
+
+```markdown
+**📅 Daily - {YYYY-MM-DD}**
+
+**Yesterday:**
+• PR #123 merged (Google OAuth)
+• 5 commits on feature/auth
+
+**Today:**
+• Finish PR #125 (GitHub OAuth)
+• Start Issue #50 (Password reset)
+
+**Blockers:**
+• ⚠️ Review pending PR #125 (@dev3)
+
+**PRs to review:**
+• PR #127 - Fix user profile (0/2)
+```
+
+### Step 4: Team Metrics
+
+```
+══════════════════════════════════════════════════════════════
+👥 TEAM ACTIVITY (Last 7 days)
+══════════════════════════════════════════════════════════════
+
+| Member | Commits | PRs | Reviews | Issues |
+|--------|---------|-----|---------|--------|
+| @dev1 | 12 | 3 | 5 | 4 |
+| @dev2 | 8 | 2 | 3 | 3 |
+| @dev3 | 15 | 4 | 8 | 5 |
+
+──────────────────────────────────────────────────────────────
+📊 CURRENT VELOCITY
+──────────────────────────────────────────────────────────────
+
+| Day | Points Delivered | Cumulative | Ideal |
+|------|---------------|--------|-------|
+| D1 | 3 | 3 | 2.1 |
+| D2 | 5 | 8 | 4.2 |
+| D3 | 2 | 10 | 6.3 |
+| D4 | 0 | 10 | 8.4 |
+| D5 | ... | ... | 10.5 |
+
+Status: 📈 Ahead by 1.6 points
+```
+
+## Daily Stand-up Tips
+
+### The 3 Classic Questions
+1. What did I do yesterday?
+2. What will I do today?
+3. Are there any obstacles?
+
+### Best Practices
+- **15 minutes max** for the entire team
+- **Standing** (encourages brevity)
+- **Same time** every day
+- **No problem solving** (parking lot)
+- **Focus on Sprint Goal**
+
+### Anti-Patterns to Avoid
+- ❌ Reporting to Scrum Master (talk to the team)
+- ❌ Long technical discussions
+- ❌ Waiting for your turn without listening
+- ❌ "I worked on X" (too vague)
+
+### Alternative Format: Walk the Board
+1. Start from "Done" column
+2. Move to "In Progress"
+3. Then "To Do"
+4. Focus on what blocks progress
+
+## Automation
+
+### GitHub Action for Daily Digest
+
+```yaml
+name: Daily Digest
+on:
+  schedule:
+    - cron: '0 7 * * 1-5'  # 7am Monday to Friday
+  workflow_dispatch:
+
+jobs:
+  digest:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Generate Digest
+        run: |
+          echo "# Daily Digest - $(date +%Y-%m-%d)" > digest.md
+          echo "" >> digest.md
+          echo "## Commits (24h)" >> digest.md
+          git log --since="24 hours ago" --oneline >> digest.md
+          echo "" >> digest.md
+          echo "## Open PRs" >> digest.md
+          gh pr list --state open --json number,title,author >> digest.md
+
+      - name: Post to Slack
+        uses: slackapi/slack-github-action@v1
+        with:
+          channel-id: 'daily-standup'
+          payload-file-path: digest.md
+```