moai-adk 0.3.12__py3-none-any.whl → 0.4.0__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-lang-python/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: moai-lang-python
+description: Python best practices with pytest, mypy, ruff, black, and uv package
+  management
+allowed-tools:
+- Read
+- Bash
+---
+
+# Python Expert
+
+## What it does
+
+Provides Python-specific expertise for TDD development, including pytest testing, mypy type checking, ruff linting, black formatting, and modern uv package management.
+
+## When to use
+
+- "Python 테스트 작성", "pytest 사용법", "Python 타입 힌트"
+- Automatically invoked when working with Python projects
+- Python SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **pytest**: Test discovery, fixtures, parametrize, markers
+- **coverage.py**: Test coverage ≥85% enforcement
+- **pytest-mock**: Mocking and patching
+
+**Type Safety**:
+- **mypy**: Static type checking with strict mode
+- Type hints for function signatures, return types
+- Generic types, Protocols, TypedDict
+
+**Code Quality**:
+- **ruff**: Fast Python linter (replaces flake8, isort, pylint)
+- **black**: Opinionated code formatter
+- Complexity checks (≤10), line length (≤88)
+
+**Package Management**:
+- **uv**: Modern, fast package installer
+- `pyproject.toml` for project configuration
+- Virtual environment management
+
+**Best Practices**:
+- File ≤300 LOC, function ≤50 LOC
+- Meaningful variable names (no single letters except loops)
+- Guard clauses over nested conditions
+- Docstrings for public APIs
+
+## Examples
+
+### Example 1: TDD with pytest
+User: "/alfred:2-build AUTH-001"
+Claude: (creates RED test with pytest, GREEN implementation, REFACTOR with type hints)
+
+### Example 2: Type checking validation
+User: "mypy 타입 체크 실행"
+Claude: (runs mypy --strict and reports type errors)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Python-specific review)
+- alfred-debugger-pro (Python debugging)

moai_adk/templates/.claude/skills/moai-lang-r/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: moai-lang-r
+description: R best practices with testthat, lintr, and data analysis patterns
+allowed-tools:
+- Read
+- Bash
+---
+
+# R Expert
+
+## What it does
+
+Provides R-specific expertise for TDD development, including testthat testing framework, lintr code linting, and statistical data analysis patterns.
+
+## When to use
+
+- "R 테스트 작성", "testthat 사용법", "데이터 분석 패턴"
+- Automatically invoked when working with R projects
+- R SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **testthat**: Unit testing framework
+- **covr**: Test coverage tool
+- **mockery**: Mocking library
+- Test coverage ≥85% enforcement
+
+**Code Quality**:
+- **lintr**: Static code analysis
+- **styler**: Code formatting
+- **goodpractice**: R package best practices
+
+**Package Management**:
+- **devtools**: Package development tools
+- **usethis**: Workflow automation
+- **CRAN**: Official package repository
+
+**Data Analysis Patterns**:
+- **tidyverse**: Data manipulation (dplyr, ggplot2)
+- **data.table**: High-performance data manipulation
+- **Vectorization** over loops
+- **Pipes** (%>%) for readable code
+
+**Best Practices**:
+- File ≤300 LOC, function ≤50 LOC
+- Document functions with roxygen2
+- Use meaningful variable names
+- Avoid global variables
+- Prefer functional programming
+
+## Examples
+
+### Example 1: TDD with testthat
+User: "/alfred:2-build ANALYSIS-001"
+Claude: (creates RED test with testthat, GREEN implementation, REFACTOR with tidyverse)
+
+### Example 2: Linting check
+User: "lintr 실행"
+Claude: (runs lintr::lint_package() and reports style issues)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (R-specific review)
+- data-science-expert (statistical analysis)

moai_adk/templates/.claude/skills/moai-lang-ruby/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: moai-lang-ruby
+description: Ruby best practices with RSpec, RuboCop, Bundler, and Rails patterns
+allowed-tools:
+- Read
+- Bash
+---
+
+# Ruby Expert
+
+## What it does
+
+Provides Ruby-specific expertise for TDD development, including RSpec BDD testing, RuboCop linting, Bundler package management, and Rails framework patterns.
+
+## When to use
+
+- "Ruby 테스트 작성", "RSpec 사용법", "Rails 패턴"
+- Automatically invoked when working with Ruby/Rails projects
+- Ruby SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **RSpec**: Behavior-driven development (describe, context, it)
+- **FactoryBot**: Test data factories
+- **Capybara**: Integration testing for web apps
+- Test coverage ≥85% with SimpleCov
+
+**Code Quality**:
+- **RuboCop**: Ruby linter and formatter
+- **Reek**: Code smell detection
+- **Brakeman**: Security vulnerability scanner (Rails)
+
+**Package Management**:
+- **Bundler**: Dependency management with Gemfile
+- **RubyGems**: Package distribution
+- Semantic versioning in gemspec
+
+**Rails Patterns**:
+- MVC architecture (Model-View-Controller)
+- ActiveRecord for database interactions
+- RESTful routing conventions
+- Service objects for business logic
+- Strong parameters for security
+
+**Best Practices**:
+- File ≤300 LOC, method ≤50 LOC
+- Prefer symbols over strings for hash keys
+- Use blocks and yielding for abstraction
+- Duck typing over explicit type checking
+
+## Examples
+
+### Example 1: TDD with RSpec
+User: "/alfred:2-build USER-001"
+Claude: (creates RED test with RSpec BDD style, GREEN implementation, REFACTOR)
+
+### Example 2: RuboCop check
+User: "RuboCop 실행"
+Claude: (runs rubocop and reports style violations)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Ruby-specific review)
+- web-api-expert (Rails API development)

moai_adk/templates/.claude/skills/moai-lang-rust/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: moai-lang-rust
+description: Rust best practices with cargo test, clippy, rustfmt, and ownership/borrow
+  checker mastery
+allowed-tools:
+- Read
+- Bash
+---
+
+# Rust Expert
+
+## What it does
+
+Provides Rust-specific expertise for TDD development, including cargo test, clippy linting, rustfmt formatting, and ownership/borrow checker compliance.
+
+## When to use
+
+- "Rust 테스트 작성", "cargo test 사용법", "소유권 규칙"
+- Automatically invoked when working with Rust projects
+- Rust SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **cargo test**: Built-in test framework
+- **proptest**: Property-based testing
+- **criterion**: Benchmarking
+- Test coverage with `cargo tarpaulin` or `cargo llvm-cov`
+
+**Code Quality**:
+- **clippy**: Rust linter with 500+ lint rules
+- **rustfmt**: Automatic code formatting
+- **cargo check**: Fast compilation check
+- **cargo audit**: Security vulnerability scanning
+
+**Memory Safety**:
+- **Ownership**: One owner per value
+- **Borrowing**: Immutable (&T) or mutable (&mut T) references
+- **Lifetimes**: Explicit lifetime annotations when needed
+- **Move semantics**: Understanding Copy vs Clone
+
+**Rust Patterns**:
+- Result<T, E> for error handling (no exceptions)
+- Option<T> for nullable values
+- Traits for polymorphism
+- Match expressions for exhaustive handling
+
+**Best Practices**:
+- File ≤300 LOC, function ≤50 LOC
+- Prefer immutable bindings (let vs let mut)
+- Use iterators over manual loops
+- Avoid `unwrap()` in production code, use proper error handling
+
+## Examples
+
+### Example 1: TDD with cargo test
+User: "/alfred:2-build PARSER-001"
+Claude: (creates RED test, GREEN implementation with Result<T, E>, REFACTOR with lifetimes)
+
+### Example 2: Clippy check
+User: "clippy 린트 실행"
+Claude: (runs cargo clippy -- -D warnings and reports issues)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Rust-specific review)
+- alfred-performance-optimizer (Rust benchmarking)

moai_adk/templates/.claude/skills/moai-lang-scala/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: moai-lang-scala
+description: Scala best practices with ScalaTest, sbt, and functional programming
+  patterns
+allowed-tools:
+- Read
+- Bash
+---
+
+# Scala Expert
+
+## What it does
+
+Provides Scala-specific expertise for TDD development, including ScalaTest framework, sbt build tool, and functional programming patterns.
+
+## When to use
+
+- "Scala 테스트 작성", "ScalaTest 사용법", "함수형 프로그래밍"
+- Automatically invoked when working with Scala projects
+- Scala SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **ScalaTest**: Flexible testing framework
+- **specs2**: BDD-style testing
+- **ScalaCheck**: Property-based testing
+- Test coverage with sbt-scoverage
+
+**Build Tools**:
+- **sbt**: Scala build tool
+- **build.sbt**: Build configuration
+- Multi-project builds
+
+**Code Quality**:
+- **Scalafmt**: Code formatting
+- **Scalafix**: Linting and refactoring
+- **WartRemover**: Code linting
+
+**Functional Programming**:
+- **Immutable data structures**
+- **Higher-order functions**
+- **Pattern matching**
+- **For-comprehensions**
+- **Monads (Option, Either, Try)**
+
+**Best Practices**:
+- File ≤300 LOC, method ≤50 LOC
+- Prefer immutable vals over mutable vars
+- Case classes for data modeling
+- Tail recursion for loops
+- Avoid null, use Option
+
+## Examples
+
+### Example 1: TDD with ScalaTest
+User: "/alfred:2-build PARSER-001"
+Claude: (creates RED test with ScalaTest, GREEN implementation with immutability, REFACTOR)
+
+### Example 2: Property testing
+User: "ScalaCheck 속성 테스트 작성"
+Claude: (creates property-based tests for edge cases)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Scala-specific review)
+- alfred-refactoring-coach (functional refactoring)

moai_adk/templates/.claude/skills/moai-lang-shell/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: moai-lang-shell
+description: Shell scripting best practices with bats, shellcheck, and POSIX compliance
+allowed-tools:
+- Read
+- Bash
+---
+
+# Shell Expert
+
+## What it does
+
+Provides shell scripting expertise for TDD development, including bats testing framework, shellcheck linting, and POSIX compliance for portable scripts.
+
+## When to use
+
+- "Shell 스크립트 작성", "bats 테스트", "POSIX 호환성"
+- Automatically invoked when working with shell script projects
+- Shell SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **bats**: Bash Automated Testing System
+- **shunit2**: xUnit-style shell testing
+- **assert.sh**: Shell assertion library
+- Test-driven shell development
+
+**Code Quality**:
+- **shellcheck**: Static analysis for shell scripts
+- **shfmt**: Shell script formatting
+- **bashate**: Style checker
+
+**POSIX Compliance**:
+- Portable shell features (sh vs bash)
+- Avoid bashisms for portability
+- Use `[ ]` instead of `[[ ]]` for POSIX
+- Standard utilities (no GNU extensions)
+
+**Shell Patterns**:
+- **Error handling**: set -e, set -u, set -o pipefail
+- **Exit codes**: Proper use of 0 (success) and non-zero
+- **Quoting**: Always quote variables ("$var")
+- **Functions**: Modular script organization
+
+**Best Practices**:
+- File ≤300 LOC, function ≤50 LOC
+- Use `#!/bin/sh` for POSIX, `#!/bin/bash` for Bash
+- Check command existence with `command -v`
+- Use `$()` over backticks
+- Validate input arguments
+
+## Examples
+
+### Example 1: TDD with bats
+User: "/alfred:2-build DEPLOY-001"
+Claude: (creates RED test with bats, GREEN implementation, REFACTOR with error handling)
+
+### Example 2: Shellcheck validation
+User: "shellcheck 실행"
+Claude: (runs shellcheck *.sh and reports issues)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Shell-specific review)
+- devops-expert (Deployment scripts)

moai_adk/templates/.claude/skills/moai-lang-sql/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: moai-lang-sql
+description: SQL best practices with testing frameworks, query optimization, and migration
+  management
+allowed-tools:
+- Read
+- Bash
+---
+
+# SQL Expert
+
+## What it does
+
+Provides SQL-specific expertise for database development, including SQL testing strategies, query optimization techniques, and migration management best practices.
+
+## When to use
+
+- "SQL 테스트 작성", "쿼리 최적화", "마이그레이션 관리"
+- Automatically invoked when working with database projects
+- SQL SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**Testing Strategies**:
+- **pgTAP**: PostgreSQL testing framework
+- **DbUnit**: Database testing for JVM
+- **SQLTest**: SQL unit testing
+- Integration tests with test databases
+
+**Query Optimization**:
+- **EXPLAIN/EXPLAIN ANALYZE**: Execution plan analysis
+- **Index optimization**: B-tree, Hash, GiST indices
+- **Query rewriting**: JOIN optimization
+- **Avoiding N+1 queries**: Eager loading
+
+**Migration Management**:
+- **Flyway**: Version-based migrations
+- **Liquibase**: Changelog-based migrations
+- **Alembic**: Python database migrations
+- **Rails migrations**: Ruby on Rails approach
+
+**SQL Best Practices**:
+- **Normalization**: 3NF compliance
+- **Constraints**: Foreign keys, NOT NULL, CHECK
+- **Transactions**: ACID properties
+- **Prepared statements**: SQL injection prevention
+
+**Database Patterns**:
+- Use CTEs (Common Table Expressions) for readability
+- Window functions over self-joins
+- Avoid SELECT * in production code
+- Use parameterized queries
+
+## Examples
+
+### Example 1: TDD with pgTAP
+User: "/alfred:2-build SCHEMA-001"
+Claude: (creates RED test with pgTAP, GREEN schema implementation, REFACTOR with indices)
+
+### Example 2: Query optimization
+User: "쿼리 성능 분석"
+Claude: (runs EXPLAIN ANALYZE and suggests optimization)
+
+## Works well with
+
+- alfred-trust-validation (migration validation)
+- alfred-code-reviewer (SQL review)
+- database-expert (database design)

moai_adk/templates/.claude/skills/moai-lang-swift/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: moai-lang-swift
+description: Swift best practices with XCTest, SwiftLint, and iOS/macOS development
+  patterns
+allowed-tools:
+- Read
+- Bash
+---
+
+# Swift Expert
+
+## What it does
+
+Provides Swift-specific expertise for TDD development, including XCTest framework, SwiftLint linting, Swift Package Manager, and iOS/macOS platform patterns.
+
+## When to use
+
+- "Swift 테스트 작성", "XCTest 사용법", "iOS 패턴"
+- Automatically invoked when working with Swift/iOS projects
+- Swift SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **XCTest**: Apple's native testing framework
+- **Quick/Nimble**: BDD-style testing (alternative)
+- **XCUITest**: UI testing for iOS/macOS apps
+- Test coverage with Xcode Code Coverage
+
+**Code Quality**:
+- **SwiftLint**: Swift linter and style checker
+- **SwiftFormat**: Code formatting tool
+- **Xcode Analyzer**: Static code analysis
+
+**Package Management**:
+- **Swift Package Manager (SPM)**: Dependency management
+- **CocoaPods**: Alternative package manager (legacy)
+- **Carthage**: Decentralized dependency manager
+
+**Swift Patterns**:
+- **Optionals**: Safe handling of nil values (?, !)
+- **Guard statements**: Early exit patterns
+- **Protocol-oriented programming**: Protocols over inheritance
+- **Value types**: Prefer structs over classes
+- **Closures**: First-class functions
+
+**iOS/macOS Patterns**:
+- **SwiftUI**: Declarative UI framework
+- **Combine**: Reactive programming
+- **UIKit/AppKit**: Traditional UI frameworks
+- **MVVM/MVC**: Architecture patterns
+
+## Examples
+
+### Example 1: TDD with XCTest
+User: "/alfred:2-build AUTH-001"
+Claude: (creates RED test with XCTest, GREEN implementation with optionals, REFACTOR)
+
+### Example 2: SwiftLint check
+User: "SwiftLint 실행"
+Claude: (runs swiftlint and reports style violations)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (Swift-specific review)
+- mobile-app-expert (iOS app development)

moai_adk/templates/.claude/skills/moai-lang-typescript/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: moai-lang-typescript
+description: TypeScript best practices with Vitest, Biome, strict typing, and npm/pnpm
+  package management
+allowed-tools:
+- Read
+- Bash
+---
+
+# TypeScript Expert
+
+## What it does
+
+Provides TypeScript-specific expertise for TDD development, including Vitest testing, Biome linting/formatting, strict type checking, and modern npm/pnpm package management.
+
+## When to use
+
+- "TypeScript 테스트 작성", "Vitest 사용법", "타입 안전성"
+- Automatically invoked when working with TypeScript projects
+- TypeScript SPEC implementation (`/alfred:2-build`)
+
+## How it works
+
+**TDD Framework**:
+- **Vitest**: Fast unit testing (Jest-compatible API)
+- **@testing-library**: Component testing for React/Vue
+- Test coverage ≥85% with c8/istanbul
+
+**Type Safety**:
+- **strict: true** in tsconfig.json
+- **noImplicitAny**, **strictNullChecks**, **strictFunctionTypes**
+- Interface definitions, Generics, Type guards
+
+**Code Quality**:
+- **Biome**: Fast linter + formatter (replaces ESLint + Prettier)
+- Type-safe configurations
+- Import organization, unused variable detection
+
+**Package Management**:
+- **pnpm**: Fast, disk-efficient package manager (preferred)
+- **npm**: Fallback option
+- `package.json` + `tsconfig.json` configuration
+
+**Best Practices**:
+- File ≤300 LOC, function ≤50 LOC
+- Prefer interfaces over types for public APIs
+- Use const assertions for literal types
+- Avoid `any`, prefer `unknown` or proper types
+
+## Examples
+
+### Example 1: TDD with Vitest
+User: "/alfred:2-build USER-001"
+Claude: (creates RED test with Vitest, GREEN implementation with strict types, REFACTOR)
+
+### Example 2: Type checking
+User: "TypeScript 타입 오류 확인"
+Claude: (runs tsc --noEmit and reports type errors)
+
+## Works well with
+
+- alfred-trust-validation (coverage verification)
+- alfred-code-reviewer (TypeScript-specific review)
+- alfred-refactoring-coach (type-safe refactoring)