moai-adk 0.4.4__py3-none-any.whl → 0.4.7__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-alfred-code-reviewer/SKILL.md

@@ -1,112 +1,113 @@
 ---
-
 name: moai-alfred-code-reviewer
-description: Automated code review with language-specific best practices, SOLID principles, and actionable improvement suggestions. Use when reviewing code changes for issues and strengths.
+version: 2.0.0
+created: 2025-10-22
+updated: 2025-10-22
+status: active
+description: Automated code review with language-specific best practices, SOLID principles, and actionable improvements.
+keywords: ['code-review', 'solid', 'best-practices', 'refactor']
 allowed-tools:
   - Read
-  - Write
-  - Edit
   - Bash
-  - TodoWrite
 ---
 
-# Alfred Code Reviewer
+# Alfred Code Reviewer Skill
 
 ## Skill Metadata
+
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | /alfred:3-sync review phase |
-| Trigger cues | Alfred-driven review summaries, diff inspection, merge gate decisions. |
+| **Skill Name** | moai-alfred-code-reviewer |
+| **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
+---
 
-Automated code review with language-specific best practices, SOLID principles verification, and code smell detection.
+## What It Does
 
-## When to use
+Automated code review with language-specific best practices, SOLID principles, and actionable improvements.
 
-- Activates when Alfred needs to summarize diffs or prepare merge feedback.
-- “Please review the code”, “How can this code be improved?”, “Check the code quality”
-- Optionally invoked after `/alfred:3-sync`
-- Before merging PR
+**Key capabilities**:
+- ✅ Best practices enforcement for alfred domain
+- ✅ TRUST 5 principles integration
+- ✅ Latest tool versions (2025-10-22)
+- ✅ TDD workflow support
 
-## How it works
+---
 
-**Code Constraints Check**:
-- File ≤300 LOC
-- Function ≤50 LOC
-- Parameters ≤5
-- Cyclomatic complexity ≤10
+## When to Use
 
-**SOLID Principles**:
-- Single Responsibility
-- Open/Closed
-- Liskov Substitution
-- Interface Segregation
-- Dependency Inversion
+**Automatic triggers**:
+- Related code discussions and file patterns
+- SPEC implementation (`/alfred:2-run`)
+- Code review requests
 
-**Code Smell Detection**:
-- Long Method
-- Large Class
-- Duplicate Code
-- Dead Code
-- Magic Numbers
+**Manual invocation**:
+- Review code for TRUST 5 compliance
+- Design new features
+- Troubleshoot issues
 
-**Language-specific Best Practices**:
-- Python: List comprehension, type hints, PEP 8
-- TypeScript: Strict typing, async/await, error handling
-- Java: Streams API, Optional, Design patterns
+---
 
-**Review Report**:
-```markdown
-## Code Review Report
+## Inputs
 
-### 🔴 Critical Issues (3)
-1. **src/auth/service.py:45** - Function too long (85 > 50 LOC)
-2. **src/api/handler.ts:120** - Missing error handling
-3. **src/db/repository.java:200** - Magic number
+- Language-specific source directories
+- Configuration files
+- Test suites and sample data
 
-### ⚠️ Warnings (5)
-1. **src/utils/helper.py:30** - Unused import
+## Outputs
 
-### ✅ Good Practices Found
-- Test coverage: 92%
-- Consistent naming
-```
+- Test/lint execution plan
+- TRUST 5 review checkpoints
+- Migration guidance
 
-## Best Practices
-- The text shown to the user is written using TUI/report expressions.
-- When running the tool, a summary of commands and results are recorded.
+## Failure Modes
 
-## Examples
-```markdown
-- Call this skill inside the /alfred command to generate a report.
-- Add summary to Completion Report.
-```
+- When required tools are not installed
+- When dependencies are missing
+- When test coverage falls below 85%
 
-## Inputs
-- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
-- Parameters passed from user commands or higher commands.
+## Dependencies
 
-## Outputs
-- Reports, checklists or recommendations for your Alfred workflow.
-- Structured data for subsequent subagent calls.
+- Access to project files via Read/Bash tools
+- Integration with `moai-foundation-langs` for language detection
+- Integration with `moai-foundation-trust` for quality gates
 
-## Failure Modes
-- When required input documents are missing or permissions are limited.
-- When disruptive changes are required without user approval.
+---
 
-## Dependencies
-- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+## References (Latest Documentation)
+
+_Documentation links updated 2025-10-22_
 
-## References
-- Google. "Code Review Developer Guide." https://google.github.io/eng-practices/review/ (accessed 2025-03-29).
-- IEEE. "Code Review Best Practices." IEEE Software, 2022.
+---
 
 ## Changelog
-- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
 
-## Works well with
+- **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
 
-- alfred-trust-validation
-- alfred-refactoring-coach
+✅ **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-code-reviewer/examples.md

@@ -0,0 +1,29 @@
+# moai-alfred-code-reviewer - 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-code-reviewer/reference.md

@@ -0,0 +1,28 @@
+# moai-alfred-code-reviewer - 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)
+
+_No specific tool versions (workflow/process Skill)_
+
+---
+
+_For detailed usage, see SKILL.md_

moai_adk/templates/.claude/skills/moai-alfred-debugger-pro/SKILL.md

@@ -1,103 +1,113 @@
 ---
-
 name: moai-alfred-debugger-pro
-description: Advanced debugging support with stack trace analysis, error pattern detection, and fix suggestions. Use when unraveling complex runtime errors or stack traces.
+version: 2.0.0
+created: 2025-10-22
+updated: 2025-10-22
+status: active
+description: Advanced debugging strategies with stack trace analysis, error pattern detection, and fix suggestions.
+keywords: ['debugging', 'stack-trace', 'errors', 'diagnosis']
 allowed-tools:
   - Read
-  - Write
-  - Edit
   - Bash
-  - TodoWrite
 ---
 
-# Alfred Debugger Pro
+# Alfred Debugger Pro Skill
 
 ## Skill Metadata
+
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | Triggered by Alfred debug-helper |
-| Trigger cues | Runtime failures surfaced in Alfred runs, stack trace walkthroughs, hotfix triage. |
-
-## What it does
-
-Advanced debugging support with stack trace analysis, common error pattern detection, and actionable fix suggestions.
-
-## When to use
-
-- Activates when Alfred encounters runtime errors and needs guided debugging steps.
-- “Resolve the error”, “What is the cause of this error?”, “Stack trace analysis”
-- Automatically invoked on runtime errors (via debug-helper sub-agent)
-- "Why not?", "Solving NullPointerException"
-
-## How it works
-
-**Stack Trace Analysis**:
-```python
-# Error example
-jwt.exceptions.ExpiredSignatureError: Signature has expired
-
-# Alfred Analysis
-📍 Error Location: src/auth/service.py:142
-🔍 Root Cause: JWT token has expired
-💡 Fix Suggestion:
-   1. Implement token refresh logic
-   2. Check expiration before validation
-   3. Handle ExpiredSignatureError gracefully
-```
-
-**Common Error Patterns**:
-- `NullPointerException` → Optional usage, guard clauses
-- `IndexError` → Boundary checks
-- `KeyError` → `.get()` with defaults
-- `TypeError` → Type hints, input validation
-- `ConnectionError` → Retry logic, timeouts
-
-**Debugging Checklist**:
-- [ ] Reproducible?
-- [ ] Log messages?
-- [ ] Input data?
-- [ ] Recent changes?
-- [ ] Dependency versions?
-
-**Language-specific Tips**:
-- **Python**: Logging, type guards
-- **TypeScript**: Type guards, null checks
-- **Java**: Optional, try-with-resources
+| **Skill Name** | moai-alfred-debugger-pro |
+| **Version** | 2.0.0 (2025-10-22) |
+| **Allowed tools** | Read (read_file), Bash (terminal) |
+| **Auto-load** | On demand when keywords detected |
+| **Tier** | Alfred |
 
-## Best Practices
-- The text shown to the user is written using TUI/report expressions.
-- When running the tool, a summary of commands and results are recorded.
+---
 
-## Examples
-```markdown
-- Call this skill inside the /alfred command to generate a report.
-- Add summary to Completion Report.
-```
+## What It Does
+
+Advanced debugging strategies with stack trace analysis, error pattern detection, and fix suggestions.
+
+**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
+
+---
 
 ## Inputs
-- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
-- Parameters passed from user commands or higher commands.
+
+- Language-specific source directories
+- Configuration files
+- Test suites and sample data
 
 ## Outputs
-- Reports, checklists or recommendations for your Alfred workflow.
-- Structured data for subsequent subagent calls.
+
+- Test/lint execution plan
+- TRUST 5 review checkpoints
+- Migration guidance
 
 ## Failure Modes
-- When required input documents are missing or permissions are limited.
-- When disruptive changes are required without user approval.
+
+- When required tools are not installed
+- When dependencies are missing
+- When test coverage falls below 85%
 
 ## Dependencies
-- Cooperation with higher-level agents such as cc-manager and project-manager is required.
 
-## References
-- Microsoft. "Debugging Techniques." https://learn.microsoft.com/visualstudio/debugger/ (accessed 2025-03-29).
-- JetBrains. "Debugging Code." https://www.jetbrains.com/help/idea/debugging-code.html (accessed 2025-03-29).
+- 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
-- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
 
-## Works well with
+- **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
 
-- alfred-code-reviewer
-- alfred-trust-validation
+✅ **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-debugger-pro/examples.md

@@ -0,0 +1,29 @@
+# moai-alfred-debugger-pro - 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-debugger-pro/reference.md

@@ -0,0 +1,28 @@
+# moai-alfred-debugger-pro - 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)
+
+_No specific tool versions (workflow/process Skill)_
+
+---
+
+_For detailed usage, see SKILL.md_

moai_adk/templates/.claude/skills/moai-alfred-ears-authoring/SKILL.md

@@ -1,103 +1,113 @@
 ---
-
 name: moai-alfred-ears-authoring
-description: EARS (Easy Approach to Requirements Syntax) authoring guide with 5 statement patterns for clear, testable requirements. Use when generating EARS-style requirement sentences.
+version: 2.0.0
+created: 2025-10-22
+updated: 2025-10-22
+status: active
+description: EARS (Easy Approach to Requirements Syntax) authoring with 5 statement patterns for clear requirements.
+keywords: ['ears', 'requirements', 'specs', 'authoring']
 allowed-tools:
   - Read
-  - Write
-  - Edit
   - Bash
-  - TodoWrite
 ---
 
-# Alfred EARS Authoring Guide
+# Alfred Ears Authoring Skill
 
 ## Skill Metadata
+
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | /alfred:1-plan requirements phase |
-| Trigger cues | Plan board EARS drafting, requirement interviews, structured SPEC authoring. |
+| **Skill Name** | moai-alfred-ears-authoring |
+| **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
+---
 
-EARS (Easy Approach to Requirements Syntax) authoring guide for writing clear, testable requirements using 5 statement patterns.
+## What It Does
 
-## When to use
+EARS (Easy Approach to Requirements Syntax) authoring with 5 statement patterns for clear requirements.
 
-- Activates when Alfred is asked to capture requirements using the EARS patterns.
-- “Writing SPEC”, “Requirements summary”, “EARS syntax”
-- Automatically invoked by `/alfred:1-plan`
-- When writing or refining SPEC documents
+**Key capabilities**:
+- ✅ Best practices enforcement for alfred domain
+- ✅ TRUST 5 principles integration
+- ✅ Latest tool versions (2025-10-22)
+- ✅ TDD workflow support
 
-## How it works
+---
 
-EARS provides 5 statement patterns for structured requirements:
+## When to Use
 
-### 1. Ubiquitous (Basic Requirements)
-**Format**: The system must provide [function]
-**Example**: The system must provide user authentication function
+**Automatic triggers**:
+- Related code discussions and file patterns
+- SPEC implementation (`/alfred:2-run`)
+- Code review requests
 
-### 2. Event-driven (event-based)
-**Format**: WHEN If [condition], the system must [operate]
-**Example**: WHEN When the user logs in, the system must issue a JWT token
+**Manual invocation**:
+- Review code for TRUST 5 compliance
+- Design new features
+- Troubleshoot issues
 
-### 3. State-driven
-**Format**: WHILE When in [state], the system must [operate]
-**Example**: WHILE When the user is authenticated, the system must allow access to protected resources
+---
 
-### 4. Optional (Optional function)
-**Format**: If WHERE [condition], the system can [operate]
-**Example**: If WHERE refresh token is provided, the system can issue a new access token
+## Inputs
 
-### 5. Constraints
-**Format**: IF [condition], the system SHOULD [constrain]
-**Example**: IF an invalid token is provided, the system SHOULD deny access
+- Language-specific source directories
+- Configuration files
+- Test suites and sample data
 
-## Writing Tips
+## Outputs
 
-✅ Be specific and measurable
-✅ Avoid vague terms (“adequate”, “sufficient”, “fast”)
-✅ One requirement per statement
-✅ Make it testable
+- Test/lint execution plan
+- TRUST 5 review checkpoints
+- Migration guidance
 
-## Best Practices
-- The text shown to the user is written using TUI/report expressions.
-- When running the tool, a summary of commands and results are recorded.
+## Failure Modes
 
-## Examples
-```markdown
-- Call this skill inside the /alfred command to generate a report.
-- Add summary to Completion Report.
-```
+- When required tools are not installed
+- When dependencies are missing
+- When test coverage falls below 85%
 
-## Inputs
-- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
-- Parameters passed from user commands or higher commands.
+## Dependencies
 
-## Outputs
-- Reports, checklists or recommendations for your Alfred workflow.
-- Structured data for subsequent subagent calls.
+- Access to project files via Read/Bash tools
+- Integration with `moai-foundation-langs` for language detection
+- Integration with `moai-foundation-trust` for quality gates
 
-## Failure Modes
-- When required input documents are missing or permissions are limited.
-- When disruptive changes are required without user approval.
+---
 
-## Dependencies
-- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+## References (Latest Documentation)
 
-## References
-- Mavin, A., et al. "Easy Approach to Requirements Syntax (EARS)." IEEE RE, 2009.
-- INCOSE. "Guide for Writing Requirements." INCOSE-TP-2010-006-02 (accessed 2025-03-29).
+_Documentation links updated 2025-10-22_
+
+---
 
 ## Changelog
-- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
 
-## Works well with
+- **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
 
-- alfred-spec-metadata-validation
-- alfred-trust-validation
+---
 
-## Reference
+## Works Well With
+
+- `moai-foundation-trust` (quality gates)
+- `moai-alfred-code-reviewer` (code review)
+- `moai-essentials-debug` (debugging support)
+
+---
+
+## Best Practices
 
-`.moai/memory/development-guide.md#ears-requirements-how-to`
+✅ **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