moai-adk 0.15.1__py3-none-any.whl → 0.32.8__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-alfred-expertise-detection/reference.md

@@ -1,126 +0,0 @@
-# Alfred Expertise Detection - Quick Reference
-
-> **Main Skill**: [SKILL.md](SKILL.md)  
-> **Examples**: [examples.md](examples.md)
-
----
-
-## Signal Detection Cheat Sheet
-
-| Signal Type | Beginner | Intermediate | Expert | Weight |
-|-------------|----------|--------------|--------|--------|
-| **Command Syntax** | Trial-and-error | Mostly correct | Always correct | +2/+1/0 |
-| **Questions** | "How?", "Why?" | "Can I?" | Direct commands | +2/+1/0 |
-| **Error Recovery** | Needs help | Self-corrects | Debugs alone | +2/+1/0 |
-| **Documentation** | Frequent refs | Occasional refs | Rare refs | +2/+1/0 |
-| **Git Workflow** | `/alfred:*` only | Mixed usage | Direct git | +2/+1/0 |
-
-**Score calculation**: Sum all weights → 0-3=Expert, 4-7=Intermediate, 8-10=Beginner
-
----
-
-## Behavioral Adaptation Matrix
-
-### Response Verbosity
-
-| Level | Length | Examples | Context |
-|-------|--------|----------|---------|
-| Beginner | 200-400 words | 2-3 | Deep background |
-| Intermediate | 100-200 words | 1-2 | Key points |
-| Expert | 50-100 words | 0-1 | Action-focused |
-
-### Confirmation Gates
-
-| Risk Level | Beginner | Intermediate | Expert |
-|------------|----------|--------------|--------|
-| **Low** | Confirm | Skip | Skip |
-| **Medium** | Confirm | Confirm | Skip |
-| **High** | Confirm + explain | Confirm | Confirm |
-
-### Proactive Suggestions
-
-| Level | Suggestions/Session | Threshold |
-|-------|---------------------|-----------|
-| Beginner | 3-5 | Low (common patterns) |
-| Intermediate | 2-3 | Medium (optimizations) |
-| Expert | 1-2 | High (advanced techniques) |
-
----
-
-## Quick Decision Tree
-
-```
-User Request
-    ↓
-Analyze 5 signals (commands, questions, errors, docs, git)
-    ↓
-Calculate weighted score (0-10)
-    ↓
-├─ 0-3: Expert → Efficiency Coach bias
-├─ 4-7: Intermediate → Project Manager bias
-└─ 8-10: Beginner → Technical Mentor bias
-    ↓
-Apply adaptations (verbosity, confirmations, suggestions)
-```
-
----
-
-## Override Mechanisms
-
-**User keywords override detection**:
-- "quick", "fast" → Force Expert mode
-- "explain", "how", "why" → Force Beginner mode
-- `/alfred:*` commands → Force Project Manager (Intermediate)
-
-**Example**:
-- Detected: Expert (score 2)
-- User says: "explain @TAG system"
-- Override: Beginner mode (verbose explanation)
-
----
-
-## Signal Examples
-
-### Beginner Signal Pattern
-
-```
-User: "How do I create a SPEC?"
-Alfred detects:
-  - Question keyword: "How" (+2)
-  - Documentation unfamiliarity (+2)
-  - No direct command usage (+2)
-  
-Score: 6 → Beginner
-
-Response: Verbose explanation with Skill("moai-foundation-specs")
-```
-
-### Expert Signal Pattern
-
-```
-User: "/alfred:2-run SPEC-AUTH-001"
-Alfred detects:
-  - Direct command with correct syntax (0)
-  - No questions (0)
-  - Knows SPEC ID format (0)
-  
-Score: 0 → Expert
-
-Response: Execute immediately, minimal output
-```
-
----
-
-## Integration Hooks
-
-**Called by**:
-- Every Alfred request (implicit)
-- `moai-alfred-persona-roles` (role selection)
-- `moai-alfred-proactive-suggestions` (suggestion threshold)
-
-**Calls**:
-- None (standalone signal analysis)
-
----
-
-**End of Reference** | 2025-11-02

moai_adk/templates/.claude/skills/moai-alfred-git-workflow/SKILL.md

@@ -1,122 +0,0 @@
----
-name: moai-alfred-git-workflow
-version: 2.0.0
-created: 2025-10-22
-updated: 2025-10-22
-status: active
-description: GitFlow automation with feature branches, TDD commits, Draft PR, and PR Ready transitions.
-keywords: ['git', 'gitflow', 'pr', 'commits']
-allowed-tools:
-  - Read
-  - Bash
----
-
-# Alfred Git Workflow Skill
-
-## Skill Metadata
-
-| Field | Value |
-| ----- | ----- |
-| **Skill Name** | moai-alfred-git-workflow |
-| **Version** | 2.0.0 (2025-10-22) |
-| **Allowed tools** | Read (read_file), Bash (terminal) |
-| **Auto-load** | On demand when keywords detected |
-| **Tier** | Alfred |
-
----
-
-## What It Does
-
-GitFlow automation with feature branches, TDD commits, Draft PR, and PR Ready transitions.
-
-**Key capabilities**:
-- ✅ Best practices enforcement for alfred domain
-- ✅ TRUST 5 principles integration
-- ✅ Latest tool versions (2025-10-22)
-- ✅ TDD workflow support
-
----
-
-## When to Use
-
-**Automatic triggers**:
-- Related code discussions and file patterns
-- SPEC implementation (`/alfred:2-run`)
-- Code review requests
-
-**Manual invocation**:
-- Review code for TRUST 5 compliance
-- Design new features
-- Troubleshoot issues
-
----
-
-## Tool Version Matrix (2025-10-22)
-
-| Tool | Version | Purpose | Status |
-|------|---------|---------|--------|
-| **Git** | 2.47.0 | Primary | ✅ Current |
-| **GitHub CLI** | 2.63.0 | Primary | ✅ Current |
-
----
-
-## Inputs
-
-- Language-specific source directories
-- Configuration files
-- Test suites and sample data
-
-## Outputs
-
-- Test/lint execution plan
-- TRUST 5 review checkpoints
-- Migration guidance
-
-## Failure Modes
-
-- When required tools are not installed
-- When dependencies are missing
-- When test coverage falls below 85%
-
-## Dependencies
-
-- Access to project files via Read/Bash tools
-- Integration with `moai-foundation-langs` for language detection
-- Integration with `moai-foundation-trust` for quality gates
-
----
-
-## References (Latest Documentation)
-
-_Documentation links updated 2025-10-22_
-
----
-
-## Changelog
-
-- **v2.0.0** (2025-10-22): Major update with latest tool versions, comprehensive best practices, TRUST 5 integration
-- **v1.0.0** (2025-03-29): Initial Skill release
-
----
-
-## Works Well With
-
-- `moai-foundation-trust` (quality gates)
-- `moai-alfred-code-reviewer` (code review)
-- `moai-essentials-debug` (debugging support)
-
----
-
-## Best Practices
-
-✅ **DO**:
-- Follow alfred best practices
-- Use latest stable tool versions
-- Maintain test coverage ≥85%
-- Document all public APIs
-
-❌ **DON'T**:
-- Skip quality gates
-- Use deprecated tools
-- Ignore security warnings
-- Mix testing frameworks

moai_adk/templates/.claude/skills/moai-alfred-git-workflow/examples.md

@@ -1,29 +0,0 @@
-# moai-alfred-git-workflow - Working Examples
-
-_Last updated: 2025-10-22_
-
-## Example 1: Basic Setup
-
-```bash
-# Setup commands
-# ...
-```
-
-## Example 2: TDD Workflow
-
-```bash
-# RED: Write failing test
-# GREEN: Implement feature
-# REFACTOR: Improve code
-```
-
-## Example 3: Quality Gate
-
-```bash
-# Run quality checks
-# Verify coverage ≥85%
-```
-
----
-
-_For more examples, see SKILL.md reference section_

moai_adk/templates/.claude/skills/moai-alfred-git-workflow/reference.md

@@ -1,29 +0,0 @@
-# moai-alfred-git-workflow - CLI Reference
-
-_Last updated: 2025-10-22_
-
-## Quick Reference
-
-### Installation
-
-```bash
-# Installation commands
-```
-
-### Common Commands
-
-```bash
-# Test
-# Lint
-# Format
-# Build
-```
-
-## Tool Versions (2025-10-22)
-
-- **Git**: 2.47.0
-- **GitHub CLI**: 2.63.0
-
----
-
-_For detailed usage, see SKILL.md_

moai_adk/templates/.claude/skills/moai-alfred-gitflow-policy/SKILL.md

@@ -1,74 +0,0 @@
----
-name: "Managing GitFlow Branch Strategy"
-description: "Enforces MoAI-ADK GitFlow workflow for team and personal modes. Covers branch protection, PR creation rules, release process, and conflict resolution. Essential for /alfred:1-plan (feature branch creation), /alfred:3-sync (PR targeting), and git-manager agent validation. Prevents direct main pushes, enforces develop-based workflow, and ensures code quality."
-allowed-tools: "Bash(git:*), Read, Edit"
----
-
-# GitFlow Protection Policy Skill
-
-## Enforced Workflow
-
-```
-feature/SPEC-XXX → develop → main
-   (your work)   (integration) (release)
-       ↓              ↓           ↓
-   [commit]      [merge PR]   [auto-deploy]
-   [PR to dev]   [code review] [tag release]
-```
-
-## Core Rules (Enforced)
-
-### 1. Main Branch Protection
-- ❌ **Direct push blocked** – All changes require PR
-- ❌ **Force push blocked** – Ensures linear history
-- ✅ **PR required** – Code review + approval needed
-- ✅ **CI/CD validation** – All checks must pass
-
-### 2. Feature Branch Creation
-```bash
-# CORRECT: Start from develop
-git checkout develop
-git pull origin develop
-git checkout -b feature/SPEC-{ID}
-
-# WRONG: Starting from main (blocked by rules)
-git checkout -b feature/something main  # ❌ Will fail on PR
-```
-
-### 3. Pull Request Rules
-```
-Feature Branch → develop (✅ CORRECT)
-Example: feature/SPEC-AUTH-001 → develop
-
-Feature Branch → main (❌ BLOCKED)
-Git-manager validates and rejects this pattern
-```
-
-### 4. Release Process
-```
-1. Work on feature/SPEC-{ID}
-2. Create PR → develop
-3. Code review + merge
-4. When develop stable: PR develop → main
-5. Release manager merges + creates tag
-6. CI/CD auto-deploys package
-```
-
-## Common Patterns
-
-| Scenario | Action |
-|----------|--------|
-| Start feature | Create feature/SPEC-{ID} from develop |
-| Push changes | git push origin feature/SPEC-{ID} |
-| Create PR | gh pr create --base develop |
-| Merge to develop | gh pr merge --squash --delete-branch |
-| Release to main | Merge develop → main (when ready) |
-| Fix merge conflict | Resolve + rebase, keep clean history |
-
-## Troubleshooting
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| "PR to main blocked" | Base branch = main | Close PR, create new with base=develop |
-| "Force push rejected" | Attempted force push | Use normal commit + push |
-| "Branch out of sync" | Develop changed | git pull origin develop, rebase |

moai_adk/templates/.claude/skills/moai-alfred-gitflow-policy/examples.md

@@ -1,4 +0,0 @@
-# Examples
-
-See `reference.md` for practical examples and usage patterns.
-

moai_adk/templates/.claude/skills/moai-alfred-gitflow-policy/reference.md

@@ -1,269 +0,0 @@
-# GitFlow Protection Policy - Reference
-
-## GitHub Branch Protection Configuration
-
-### Main Branch Rules (Enforced)
-
-```
-Settings → Branches → Branch protection rules
-├── Require a pull request before merging
-│   └── Require approvals: 1
-├── Require status checks to pass
-│   └── Require branches to be up to date before merging
-├── Require conversation resolution before merging
-├── Require signed commits
-└── Restrict who can push to matching branches
-    └── Allows: [maintainers only]
-```
-
-### Develop Branch Rules (Advisory)
-
-```
-Settings → Branches → Branch protection rules
-├── Require a pull request before merging
-│   └── Require approvals: 0 (flexible)
-├── Require status checks to pass
-│   └── Both: Linting + Tests
-└── Dismiss stale pull request approvals when new commits are pushed
-```
-
-## Feature Branch Workflow
-
-### 1. Create Feature Branch
-
-```bash
-# Always start from develop
-git checkout develop
-git pull origin develop
-git checkout -b feature/SPEC-AUTH-001
-
-# Naming convention: feature/SPEC-{DOMAIN}-{NUMBER}
-# Examples: feature/SPEC-AUTH-001, feature/SPEC-CACHE-FIX-002
-```
-
-### 2. Make Commits
-
-```bash
-# Follow conventional commit format
-git commit -m "feat(auth): Implement email verification
-
-- Add email validation logic
-- Create verification token system
-- Update user model with verification status
-
-@CODE:AUTH-001"
-```
-
-### 3. Push and Create PR
-
-```bash
-# Push to remote
-git push origin feature/SPEC-AUTH-001
-
-# Create PR (gh cli)
-gh pr create \
-  --base develop \
-  --head feature/SPEC-AUTH-001 \
-  --title "[FEAT] Implement Email Verification" \
-  --body "$(cat <<'EOF'
-## Summary
-Implements email verification system as per SPEC-AUTH-001
-
-## Test Plan
-- [ ] Unit tests pass (npm run test)
-- [ ] Email sending verified in dev
-- [ ] Verification flow tested end-to-end
-
-@TEST:AUTH-001
-@CODE:AUTH-001
-EOF
-)"
-```
-
-### 4. Code Review and Merge
-
-```bash
-# After approval
-gh pr merge <PR_NUMBER> \
-  --squash \
-  --delete-branch \
-  -m "Merge: Email verification system (SPEC-AUTH-001)"
-
-# Auto-deletes feature branch after merge
-```
-
-## Release Process (develop → main)
-
-### When Develop is Stable
-
-```bash
-# 1. Ensure develop is fully tested
-git checkout develop
-git pull origin develop
-
-# 2. Run complete test suite
-npm run test
-npm run lint
-npm run type-check
-
-# 3. Create release PR to main
-gh pr create \
-  --base main \
-  --head develop \
-  --title "Release: v0.2.0" \
-  --body "$(cat <<'EOF'
-## Release v0.2.0
-
-### Features
-- EMAIL: Email verification system (SPEC-AUTH-001)
-- CACHE: Redis caching (SPEC-CACHE-FIX-001)
-
-### Bug Fixes
-- AUTH: Session expiration logic
-- API: Rate limiting edge cases
-
-### Breaking Changes
-None
-
-## Checklist
-- [x] All tests passing
-- [x] Documentation updated
-- [x] Changelog generated
-- [x] Version bumped
-- [x] No security vulnerabilities
-EOF
-)"
-
-# 4. After approval, merge to main
-gh pr merge <RELEASE_PR_NUMBER> \
-  --merge \
-  --delete-branch \
-  -m "Release: v0.2.0 - Email verification and caching"
-
-# 5. Create git tag
-git tag -a v0.2.0 -m "Release v0.2.0"
-git push origin v0.2.0
-
-# 6. CI/CD auto-deploys to PyPI
-```
-
-## Conflict Resolution
-
-### When Develop Changed After Feature Branch Created
-
-```bash
-# 1. Fetch latest develop
-git fetch origin develop
-
-# 2. Rebase (preferred) or merge
-git rebase origin/develop
-
-# 3. If conflicts exist, resolve manually
-git status  # See conflicted files
-
-# Edit conflicted files, keep desired changes
-
-# 4. Continue rebase
-git add .
-git rebase --continue
-
-# 5. Force push (safe, rebasing your own branch)
-git push origin feature/SPEC-AUTH-001 --force-with-lease
-```
-
-### When PR Has Merge Conflicts
-
-```bash
-# If CI shows merge conflicts:
-# 1. Update local develop
-git checkout develop
-git pull origin develop
-
-# 2. Rebase feature branch
-git checkout feature/SPEC-AUTH-001
-git rebase develop
-
-# 3. Resolve conflicts manually
-# (same as above)
-
-# 4. Push resolved version
-git push origin feature/SPEC-AUTH-001 --force-with-lease
-
-# GitHub PR automatically updates
-```
-
-## Error Handling
-
-### PR to Main Blocked
-
-**Error Message**:
-```
-❌ GitFlow Violation Detected
-Base branch: main (forbidden)
-Expected: develop
-
-Feature branches must target develop, not main.
-```
-
-**Fix**:
-```bash
-# 1. Close the incorrect PR
-gh pr close <PR_NUMBER>
-
-# 2. Create correct PR
-gh pr create --base develop --head feature/SPEC-AUTH-001
-```
-
-### Force Push to Main Rejected
-
-**Error Message**:
-```
-❌ [remote rejected] main (protected branch hook declined)
-fatal: Could not read from remote repository.
-```
-
-**Fix**:
-```bash
-# Cannot force push to main (by design)
-# Create PR instead
-gh pr create --base main --head develop
-```
-
-### Branch Out of Sync (Behind Develop)
-
-**Error Message**:
-```
-⚠️ This branch is out-of-date with the base branch
-Consider updating your branch before merging.
-```
-
-**Fix**:
-```bash
-# Update from latest develop
-git fetch origin
-git rebase origin/develop
-git push origin feature/SPEC-AUTH-001 --force-with-lease
-```
-
-## Checklist: Before Merging to Develop
-
-- [ ] Feature branch created from latest develop
-- [ ] All commits follow conventional commit format
-- [ ] Code passes linting and type checking
-- [ ] Tests pass locally and in CI
-- [ ] PR description includes @SPEC:ID and @TEST:ID
-- [ ] Code review approved by at least 1 maintainer
-- [ ] All conversations resolved
-- [ ] Branch is up-to-date with develop
-- [ ] Commits are squashed (optional but recommended)
-
-## Checklist: Before Merging to Main
-
-- [ ] All features merged and tested in develop
-- [ ] Complete test suite passes
-- [ ] Documentation is current
-- [ ] Changelog is generated
-- [ ] Version is bumped (semver)
-- [ ] Security review completed
-- [ ] Release notes drafted
-- [ ] No regressions detected