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

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-javascript
-description: JavaScript best practices with Jest, ESLint, Prettier, and npm package
-  management
+description: JavaScript best practices with Jest, ESLint, Prettier, and npm package management. Use when writing or reviewing JavaScript code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # JavaScript Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | JavaScript code discussions, framework guidance, or file extensions such as .js. |
+| Tier | 3 |
+
 ## What it does
 
 Provides JavaScript-specific expertise for TDD development, including Jest testing, ESLint linting, Prettier formatting, and npm package management.
 
 ## When to use
 
-- "JavaScript 테스트 작성", "Jest 사용법", "ES6+ 문법"
+- Engages when the conversation references JavaScript work, frameworks, or files like .js.
+- "Writing JavaScript tests", "How to use Jest", "ES6+ grammar"
 - Automatically invoked when working with JavaScript projects
-- JavaScript SPEC implementation (`/alfred:2-build`)
+- JavaScript SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -48,17 +57,40 @@ Provides JavaScript-specific expertise for TDD development, including Jest testi
 - Meaningful names, avoid abbreviations
 
 ## Examples
+```bash
+npm run test && npm run lint
+```
+
+## 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 Jest
-User: "/alfred:2-build API-001"
-Claude: (creates RED test with Jest, GREEN implementation, REFACTOR with JSDoc)
+## 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: Linting
-User: "ESLint 실행"
-Claude: (runs eslint . and reports linting 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
+- MDN Web Docs. "JavaScript Guide." https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide (accessed 2025-03-29).
+- Jest. "Getting Started." https://jestjs.io/docs/getting-started (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 (JavaScript-specific review)
 - alfred-debugger-pro (JavaScript debugging)
+
+## 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-julia/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-julia
-description: Julia best practices with Test stdlib, Pkg manager, and scientific computing
-  patterns
+description: Julia best practices with Test stdlib, Pkg manager, and scientific computing patterns. Use when writing or reviewing Julia code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Julia Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Julia code discussions, framework guidance, or file extensions such as .jl. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Julia-specific expertise for TDD development, including Test standard library, Pkg package manager, and high-performance scientific computing patterns.
 
 ## When to use
 
-- "Julia 테스트 작성", "Test stdlib 사용법", "과학 컴퓨팅"
+- Engages when the conversation references Julia work, frameworks, or files like .jl.
+- "Writing Julia tests", "How to use Test stdlib", "Scientific computing"
 - Automatically invoked when working with Julia projects
-- Julia SPEC implementation (`/alfred:2-build`)
+- Julia SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +59,40 @@ Provides Julia-specific expertise for TDD development, including Test standard l
 - Profile before optimizing
 
 ## Examples
+```bash
+julia --project -e 'using Pkg; Pkg.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 Test stdlib
-User: "/alfred:2-build COMPUTE-001"
-Claude: (creates RED test with @testset, GREEN implementation with type stability, 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: Performance optimization
-User: "Julia 성능 최적화"
-Claude: (profiles code and suggests type-stable refactoring)
+## 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
+- Julia Language. "Documentation." https://docs.julialang.org/en/v1/ (accessed 2025-03-29).
+- JuliaFormatter.jl. "JuliaFormatter Documentation." https://domluna.github.io/JuliaFormatter.jl/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 (coverage verification)
 - alfred-code-reviewer (Julia-specific review)
 - alfred-performance-optimizer (Julia profiling)
+
+## 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-kotlin/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-kotlin
-description: Kotlin best practices with JUnit, Gradle, ktlint, coroutines, and extension
-  functions
+description: Kotlin best practices with JUnit, Gradle, ktlint, coroutines, and extension functions. Use when writing or reviewing Kotlin code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Kotlin Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Kotlin code discussions, framework guidance, or file extensions such as .kt/.kts. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Kotlin-specific expertise for TDD development, including JUnit testing, Gradle build system, ktlint linting, coroutines for concurrency, and extension functions.
 
 ## When to use
 
-- "Kotlin 테스트 작성", "코루틴 사용법", "Android 패턴"
+- Engages when the conversation references Kotlin work, frameworks, or files like .kt/.kts.
+- “Writing Kotlin tests”, “How to use coroutines”, “Android patterns”
 - Automatically invoked when working with Kotlin/Android projects
-- Kotlin SPEC implementation (`/alfred:2-build`)
+- Kotlin SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +60,40 @@ Provides Kotlin-specific expertise for TDD development, including JUnit testing,
 - **Retrofit**: Network requests
 
 ## Examples
+```bash
+./gradlew test && ./gradlew ktlintCheck
+```
+
+## 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 coroutines
-User: "/alfred:2-build API-001"
-Claude: (creates RED test with runTest, GREEN implementation with suspend functions, 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: ktlint check
-User: "ktlint 실행"
-Claude: (runs ktlint 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
+- JetBrains. "Kotlin Language Documentation." https://kotlinlang.org/docs/home.html (accessed 2025-03-29).
+- Pinterest. "ktlint." https://pinterest.github.io/ktlint/ (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 (Kotlin-specific review)
 - mobile-app-expert (Android 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-lua/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-lua
-description: Lua best practices with busted, luacheck, and embedded scripting patterns
+description: Lua best practices with busted, luacheck, and embedded scripting patterns. Use when writing or reviewing Lua code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Lua Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Lua code discussions, framework guidance, or file extensions such as .lua. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Lua-specific expertise for TDD development, including busted testing framework, luacheck linting, and embedded scripting patterns for game development and system configuration.
 
 ## When to use
 
-- "Lua 테스트 작성", "busted 사용법", "임베디드 스크립팅"
+- Engages when the conversation references Lua work, frameworks, or files like .lua.
+- "Writing Lua tests", "How to use busted", "Embedded scripting"
 - Automatically invoked when working with Lua projects
-- Lua SPEC implementation (`/alfred:2-build`)
+- Lua SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -49,17 +59,40 @@ Provides Lua-specific expertise for TDD development, including busted testing fr
 - Avoid global variables
 
 ## Examples
+```bash
+luacheck src && busted
+```
+
+## 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 busted
-User: "/alfred:2-build CONFIG-001"
-Claude: (creates RED test with busted, GREEN implementation, REFACTOR with metatables)
+## 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: Linting check
-User: "luacheck 실행"
-Claude: (runs luacheck 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
+- Lua.org. "Programming in Lua." https://www.lua.org/pil/contents.html (accessed 2025-03-29).
+- Olivine Labs. "busted." https://olivinelabs.com/busted/ (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 (Lua-specific review)
 - cli-tool-expert (Lua scripting utilities)
+
+## 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-php/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-php
-description: PHP best practices with PHPUnit, Composer, and PSR standards
+description: PHP best practices with PHPUnit, Composer, and PSR standards. Use when writing or reviewing PHP code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # PHP Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | PHP code discussions, framework guidance, or file extensions such as .php. |
+| Tier | 3 |
+
 ## What it does
 
 Provides PHP-specific expertise for TDD development, including PHPUnit testing, Composer package management, and PSR (PHP Standards Recommendations) compliance.
 
 ## When to use
 
-- "PHP 테스트 작성", "PHPUnit 사용법", "PSR 표준"
+- Engages when the conversation references PHP work, frameworks, or files like .php.
+- "Writing PHP tests", "How to use PHPUnit", "PSR standard"
 - Automatically invoked when working with PHP projects
-- PHP SPEC implementation (`/alfred:2-build`)
+- PHP SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -49,17 +59,40 @@ Provides PHP-specific expertise for TDD development, including PHPUnit testing,
 - Dependency injection over global state
 
 ## Examples
+```bash
+vendor/bin/phpunit && vendor/bin/phpstan analyse
+```
+
+## 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 PHPUnit
-User: "/alfred:2-build SERVICE-001"
-Claude: (creates RED test with PHPUnit, GREEN implementation, REFACTOR with types)
+## 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: PSR compliance
-User: "PSR 표준 확인"
-Claude: (runs phpcs --standard=PSR12 and reports 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
+- PHP Manual. "PHP Documentation." https://www.php.net/manual/en/ (accessed 2025-03-29).
+- PHPUnit. "PHPUnit Manual." https://phpunit.de/documentation.html (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 (PHP-specific review)
 - web-api-expert (Laravel/Symfony 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-python/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-python
-description: Python best practices with pytest, mypy, ruff, black, and uv package
-  management
+description: Python best practices with pytest, mypy, ruff, black, and uv package management. Use when writing or reviewing Python code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Python Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Python code discussions, framework guidance, or file extensions such as .py. |
+| Tier | 3 |
+
 ## 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 타입 힌트"
+- Engages when the conversation references Python work, frameworks, or files like .py.
+- “Writing Python tests”, “How to use pytest”, “Python type hints”
 - Automatically invoked when working with Python projects
-- Python SPEC implementation (`/alfred:2-build`)
+- Python SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -48,17 +57,40 @@ Provides Python-specific expertise for TDD development, including pytest testing
 - Docstrings for public APIs
 
 ## Examples
+```bash
+python -m pytest && ruff check . && black --check .
+```
+
+## 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 pytest
-User: "/alfred:2-build AUTH-001"
-Claude: (creates RED test with pytest, GREEN implementation, REFACTOR with type hints)
+## 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 validation
-User: "mypy 타입 체크 실행"
-Claude: (runs mypy --strict 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
+- Python Software Foundation. "Python Developer's Guide." https://docs.python.org/3/ (accessed 2025-03-29).
+- Pytest. "pytest Documentation." https://docs.pytest.org/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 (coverage verification)
 - alfred-code-reviewer (Python-specific review)
 - alfred-debugger-pro (Python debugging)
+
+## 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-r/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-r
-description: R best practices with testthat, lintr, and data analysis patterns
+description: R best practices with testthat, lintr, and data analysis patterns. Use when writing or reviewing R code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # R Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | R code discussions, framework guidance, or file extensions such as .r. |
+| Tier | 3 |
+
 ## 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 사용법", "데이터 분석 패턴"
+- Engages when the conversation references R work, frameworks, or files like .r.
+- “Writing R tests”, “How to use testthat”, “Data analysis patterns”
 - Automatically invoked when working with R projects
-- R SPEC implementation (`/alfred:2-build`)
+- R SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +60,40 @@ Provides R-specific expertise for TDD development, including testthat testing fr
 - Prefer functional programming
 
 ## Examples
+```bash
+Rscript -e 'devtools::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 testthat
-User: "/alfred:2-build ANALYSIS-001"
-Claude: (creates RED test with testthat, GREEN implementation, REFACTOR with tidyverse)
+## 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: Linting check
-User: "lintr 실행"
-Claude: (runs lintr::lint_package() and reports style 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
+- R Core Team. "R Language Definition." https://cran.r-project.org/manuals.html (accessed 2025-03-29).
+- RStudio. "testthat Reference." https://testthat.r-lib.org/ (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 (R-specific review)
 - data-science-expert (statistical analysis)
+
+## 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.