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

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

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-ruby
-description: Ruby best practices with RSpec, RuboCop, Bundler, and Rails patterns
+description: Ruby best practices with RSpec, RuboCop, Bundler, and Rails patterns. Use when writing or reviewing Ruby code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Ruby Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Ruby code discussions, framework guidance, or file extensions such as .rb. |
+| Tier | 3 |
+
 ## 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 패턴"
+- Engages when the conversation references Ruby work, frameworks, or files like .rb.
+- “Writing Ruby tests”, “How to use RSpec”, “Rails patterns”
 - Automatically invoked when working with Ruby/Rails projects
-- Ruby SPEC implementation (`/alfred:2-build`)
+- Ruby SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +60,40 @@ Provides Ruby-specific expertise for TDD development, including RSpec BDD testin
 - Duck typing over explicit type checking
 
 ## Examples
+```bash
+bundle exec rubocop && bundle exec rspec
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with RSpec
-User: "/alfred:2-build USER-001"
-Claude: (creates RED test with RSpec BDD style, GREEN implementation, REFACTOR)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: RuboCop check
-User: "RuboCop 실행"
-Claude: (runs rubocop and reports style violations)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- Ruby Lang. "Ruby Programming Language." https://www.ruby-lang.org/en/documentation/ (accessed 2025-03-29).
+- RuboCop. "RuboCop Documentation." https://docs.rubocop.org/rubocop/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (Ruby-specific review)
 - web-api-expert (Rails API development)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-rust
-description: Rust best practices with cargo test, clippy, rustfmt, and ownership/borrow
-  checker mastery
+description: Rust best practices with cargo test, clippy, rustfmt, and ownership/borrow checker mastery. Use when writing or reviewing Rust code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Rust Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Rust code discussions, framework guidance, or file extensions such as .rs. |
+| Tier | 3 |
+
 ## 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 사용법", "소유권 규칙"
+- Engages when the conversation references Rust work, frameworks, or files like .rs.
+- “Writing Rust tests”, “How to use cargo tests”, “Ownership rules”
 - Automatically invoked when working with Rust projects
-- Rust SPEC implementation (`/alfred:2-build`)
+- Rust SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -52,17 +61,40 @@ Provides Rust-specific expertise for TDD development, including cargo test, clip
 - Avoid `unwrap()` in production code, use proper error handling
 
 ## Examples
+```bash
+cargo test && cargo clippy -- -D warnings
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### 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)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: Clippy check
-User: "clippy 린트 실행"
-Claude: (runs cargo clippy -- -D warnings and reports issues)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- Rust Project Developers. "The Rust Programming Language." https://doc.rust-lang.org/book/ (accessed 2025-03-29).
+- Rust Project Developers. "Clippy." https://doc.rust-lang.org/clippy/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (Rust-specific review)
 - alfred-performance-optimizer (Rust benchmarking)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-scala
-description: Scala best practices with ScalaTest, sbt, and functional programming
-  patterns
+description: Scala best practices with ScalaTest, sbt, and functional programming patterns. Use when writing or reviewing Scala code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Scala Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Scala code discussions, framework guidance, or file extensions such as .scala. |
+| Tier | 3 |
+
 ## 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 사용법", "함수형 프로그래밍"
+- Engages when the conversation references Scala work, frameworks, or files like .scala.
+- “Writing Scala tests”, “How to use ScalaTest”, “Functional programming”
 - Automatically invoked when working with Scala projects
-- Scala SPEC implementation (`/alfred:2-build`)
+- Scala SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -52,17 +61,40 @@ Provides Scala-specific expertise for TDD development, including ScalaTest frame
 - Avoid null, use Option
 
 ## Examples
+```bash
+sbt test && sbt scalafmtCheck
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with ScalaTest
-User: "/alfred:2-build PARSER-001"
-Claude: (creates RED test with ScalaTest, GREEN implementation with immutability, REFACTOR)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: Property testing
-User: "ScalaCheck 속성 테스트 작성"
-Claude: (creates property-based tests for edge cases)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- Lightbend. "Scala Documentation." https://docs.scala-lang.org/ (accessed 2025-03-29).
+- Scalameta. "scalafmt." https://scalameta.org/scalafmt/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (Scala-specific review)
 - alfred-refactoring-coach (functional refactoring)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-shell
-description: Shell scripting best practices with bats, shellcheck, and POSIX compliance
+description: Shell scripting best practices with bats, shellcheck, and POSIX compliance. Use when writing or reviewing Shell scripts code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Shell Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Shell code discussions, framework guidance, or file extensions such as .sh/.bash. |
+| Tier | 3 |
+
 ## 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 호환성"
+- Engages when the conversation references Shell work, frameworks, or files like .sh/.bash.
+- "Writing shell scripts", "bats testing", "POSIX compatibility"
 - Automatically invoked when working with shell script projects
-- Shell SPEC implementation (`/alfred:2-build`)
+- Shell SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +61,40 @@ Provides shell scripting expertise for TDD development, including bats testing f
 - Validate input arguments
 
 ## Examples
+```bash
+bats tests && shellcheck scripts/*.sh
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with bats
-User: "/alfred:2-build DEPLOY-001"
-Claude: (creates RED test with bats, GREEN implementation, REFACTOR with error handling)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: Shellcheck validation
-User: "shellcheck 실행"
-Claude: (runs shellcheck *.sh and reports issues)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- GNU. "Bash Reference Manual." https://www.gnu.org/software/bash/manual/bash.html (accessed 2025-03-29).
+- koalaman. "ShellCheck." https://www.shellcheck.net/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (Shell-specific review)
 - devops-expert (Deployment scripts)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-sql
-description: SQL best practices with testing frameworks, query optimization, and migration
-  management
+description: SQL best practices with testing frameworks, query optimization, and migration management. Use when writing or reviewing SQL code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # SQL Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | SQL code discussions, framework guidance, or file extensions such as .sql. |
+| Tier | 3 |
+
 ## 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 테스트 작성", "쿼리 최적화", "마이그레이션 관리"
+- Engages when the conversation references SQL work, frameworks, or files like .sql.
+- “Writing SQL tests”, “Query optimization”, “Migration management”
 - Automatically invoked when working with database projects
-- SQL SPEC implementation (`/alfred:2-build`)
+- SQL SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -52,17 +61,40 @@ Provides SQL-specific expertise for database development, including SQL testing
 - Use parameterized queries
 
 ## Examples
+```bash
+sqlfluff lint sql/ && sqlfluff fix sql/
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with pgTAP
-User: "/alfred:2-build SCHEMA-001"
-Claude: (creates RED test with pgTAP, GREEN schema implementation, REFACTOR with indices)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: Query optimization
-User: "쿼리 성능 분석"
-Claude: (runs EXPLAIN ANALYZE and suggests optimization)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- PostgreSQL Global Development Group. "PostgreSQL Documentation." https://www.postgresql.org/docs/ (accessed 2025-03-29).
+- SQLFluff. "SQLFluff Documentation." https://docs.sqlfluff.com/en/stable/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (migration validation)
 - alfred-code-reviewer (SQL review)
 - database-expert (database design)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-swift
-description: Swift best practices with XCTest, SwiftLint, and iOS/macOS development
-  patterns
+description: Swift best practices with XCTest, SwiftLint, and iOS/macOS development patterns. Use when writing or reviewing Swift code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Swift Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Swift code discussions, framework guidance, or file extensions such as .swift. |
+| Tier | 3 |
+
 ## 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 패턴"
+- Engages when the conversation references Swift work, frameworks, or files like .swift.
+- “Writing Swift tests”, “How to use XCTest”, “iOS patterns”
 - Automatically invoked when working with Swift/iOS projects
-- Swift SPEC implementation (`/alfred:2-build`)
+- Swift SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +60,40 @@ Provides Swift-specific expertise for TDD development, including XCTest framewor
 - **MVVM/MVC**: Architecture patterns
 
 ## Examples
+```bash
+swift test && swift-format --lint --recursive Sources
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with XCTest
-User: "/alfred:2-build AUTH-001"
-Claude: (creates RED test with XCTest, GREEN implementation with optionals, REFACTOR)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: SwiftLint check
-User: "SwiftLint 실행"
-Claude: (runs swiftlint and reports style violations)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- Apple. "Swift Programming Language Guide." https://docs.swift.org/swift-book/ (accessed 2025-03-29).
+- Apple. "Swift Package Manager." https://developer.apple.com/documentation/swift_packages (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (Swift-specific review)
 - mobile-app-expert (iOS app development)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-typescript
-description: TypeScript best practices with Vitest, Biome, strict typing, and npm/pnpm
-  package management
+description: TypeScript best practices with Vitest, Biome, strict typing, and npm/pnpm package management. Use when writing or reviewing TypeScript code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # TypeScript Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | TypeScript code discussions, framework guidance, or file extensions such as .ts/.tsx. |
+| Tier | 3 |
+
 ## 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 사용법", "타입 안전성"
+- Engages when the conversation references TypeScript work, frameworks, or files like .ts/.tsx.
+- "Writing TypeScript tests", "How to use Vitest", "Type safety"
 - Automatically invoked when working with TypeScript projects
-- TypeScript SPEC implementation (`/alfred:2-build`)
+- TypeScript SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -48,17 +57,40 @@ Provides TypeScript-specific expertise for TDD development, including Vitest tes
 - Avoid `any`, prefer `unknown` or proper types
 
 ## Examples
+```bash
+npm run lint && npm test
+```
+
+## Inputs
+- Language-specific source directories (e.g. `src/`, `app/`).
+- Language-specific build/test configuration files (e.g. `package.json`, `pyproject.toml`, `go.mod`).
+- Relevant test suites and sample data.
+
+## Outputs
+- Test/lint execution plan tailored to the selected language.
+- List of key language idioms and review checkpoints.
 
-### Example 1: TDD with Vitest
-User: "/alfred:2-build USER-001"
-Claude: (creates RED test with Vitest, GREEN implementation with strict types, REFACTOR)
+## Failure Modes
+- When the language runtime or package manager is not installed.
+- When the main language cannot be determined in a multilingual project.
 
-### Example 2: Type checking
-User: "TypeScript 타입 오류 확인"
-Claude: (runs tsc --noEmit and reports type errors)
+## Dependencies
+- Access to the project file is required using the Read/Grep tool.
+- When used with `Skill("moai-foundation-langs")`, it is easy to share cross-language conventions.
+
+## References
+- Microsoft. "TypeScript Handbook." https://www.typescriptlang.org/docs/ (accessed 2025-03-29).
+- OpenJS Foundation. "ESLint User Guide." https://eslint.org/docs/latest/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Input/output/failure response/reference information for each language has been specified.
 
 ## Works well with
 
 - alfred-trust-validation (coverage verification)
 - alfred-code-reviewer (TypeScript-specific review)
 - alfred-refactoring-coach (type-safe refactoring)
+
+## Best Practices
+- Enable automatic validation by matching your linter with the language's official style guide.
+- Fix test/build pipelines with reproducible commands in CI.