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

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

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-cpp
-description: C++ best practices with Google Test, clang-format, and modern C++ (C++17/20)
+description: C++ best practices with Google Test, clang-format, and modern C++ (C++17/20). Use when writing or reviewing C++ code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # C++ Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | C++ code discussions, framework guidance, or file extensions such as .cpp/.hpp. |
+| Tier | 3 |
+
 ## What it does
 
 Provides C++-specific expertise for TDD development, including Google Test framework, clang-format formatting, and modern C++ (C++17/20) features.
 
 ## When to use
 
-- "C++ 테스트 작성", "Google Test 사용법", "모던 C++"
+- Engages when the conversation references C++ work, frameworks, or files like .cpp/.hpp.
+- "Writing C++ tests", "How to use Google Test", "Modern C++"
 - Automatically invoked when working with C++ projects
-- C++ SPEC implementation (`/alfred:2-build`)
+- C++ SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -53,17 +63,40 @@ Provides C++-specific expertise for TDD development, including Google Test frame
 - Const correctness
 
 ## Examples
+```bash
+cmake --build build --target test && clang-tidy src/*.cpp
+```
+
+## 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 Google Test
-User: "/alfred:2-build CACHE-001"
-Claude: (creates RED test with gtest, GREEN implementation with smart pointers, 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: Modern C++ refactoring
-User: "C++17 기능으로 리팩토링"
-Claude: (refactors code to use std::optional, structured bindings)
+## 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
+- ISO. "ISO/IEC 14882:2020(E) Programming Language C++." (accessed 2025-03-29).
+- LLVM Project. "clang-tidy Documentation." https://clang.llvm.org/extra/clang-tidy/ (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 (C++-specific review)
 - alfred-performance-optimizer (C++ 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-csharp/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-csharp
-description: C# best practices with xUnit, .NET tooling, LINQ, and async/await patterns
+description: C# best practices with xUnit, .NET tooling, LINQ, and async/await patterns. Use when writing or reviewing C# code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # C# Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | C# code discussions, framework guidance, or file extensions such as .cs. |
+| Tier | 3 |
+
 ## What it does
 
 Provides C#-specific expertise for TDD development, including xUnit testing, .NET CLI tooling, LINQ query expressions, and async/await patterns.
 
 ## When to use
 
-- "C# 테스트 작성", "xUnit 사용법", "LINQ 쿼리"
+- Engages when the conversation references C# work, frameworks, or files like .cs.
+- "Writing C# tests", "How to use xUnit", "LINQ queries"
 - Automatically invoked when working with .NET projects
-- C# SPEC implementation (`/alfred:2-build`)
+- C# SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +61,40 @@ Provides C#-specific expertise for TDD development, including xUnit testing, .NE
 - Use string interpolation ($"") over concatenation
 
 ## Examples
+```bash
+dotnet test && dotnet format --verify-no-changes
+```
+
+## 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 xUnit
-User: "/alfred:2-build SERVICE-001"
-Claude: (creates RED test with xUnit, GREEN implementation with async/await, 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: LINQ query optimization
-User: "LINQ 쿼리 최적화"
-Claude: (analyzes LINQ queries and suggests IEnumerable vs IQueryable optimizations)
+## 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. "C# Programming Guide." https://learn.microsoft.com/dotnet/csharp/ (accessed 2025-03-29).
+- Microsoft. ".NET Testing with dotnet test." https://learn.microsoft.com/dotnet/core/testing/ (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 (C#-specific review)
 - web-api-expert (ASP.NET Core 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-dart/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-dart
-description: Dart best practices with flutter test, dart analyze, and Flutter widget
-  patterns
+description: Dart best practices with flutter test, dart analyze, and Flutter widget patterns. Use when writing or reviewing Dart/Flutter code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Dart Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Dart code discussions, framework guidance, or file extensions such as .dart. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Dart-specific expertise for TDD development, including flutter test framework, dart analyze linting, and Flutter widget patterns for cross-platform app development.
 
 ## When to use
 
-- "Dart 테스트 작성", "Flutter 위젯 패턴", "flutter test 사용법"
+- Engages when the conversation references Dart work, frameworks, or files like .dart.
+- “Writing Dart tests”, “Flutter widget patterns”, “How to use flutter tests”
 - Automatically invoked when working with Dart/Flutter projects
-- Dart SPEC implementation (`/alfred:2-build`)
+- Dart SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +59,40 @@ Provides Dart-specific expertise for TDD development, including flutter test fra
 - Widget composition over inheritance
 
 ## Examples
+```bash
+dart test && dart analyze
+```
+
+## 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 flutter test
-User: "/alfred:2-build UI-001"
-Claude: (creates RED widget test, GREEN implementation, REFACTOR with const)
+## 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: Static analysis
-User: "dart analyze 실행"
-Claude: (runs dart analyze 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
+- Google. "Dart Language Tour." https://dart.dev/guides/language/language-tour (accessed 2025-03-29).
+- Flutter. "Testing." https://docs.flutter.dev/testing (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 (Dart-specific review)
 - mobile-app-expert (Flutter 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-elixir/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-elixir
-description: Elixir best practices with ExUnit, Mix, and OTP patterns
+description: Elixir best practices with ExUnit, Mix, and OTP patterns. Use when writing or reviewing Elixir code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Elixir Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Elixir code discussions, framework guidance, or file extensions such as .ex/.exs. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Elixir-specific expertise for TDD development, including ExUnit testing, Mix build tool, and OTP (Open Telecom Platform) patterns for concurrent systems.
 
 ## When to use
 
-- "Elixir 테스트 작성", "ExUnit 사용법", "OTP 패턴"
+- Engages when the conversation references Elixir work, frameworks, or files like .ex/.exs.
+- "Writing Elixir tests", "How to use ExUnit", "OTP patterns"
 - Automatically invoked when working with Elixir/Phoenix projects
-- Elixir SPEC implementation (`/alfred:2-build`)
+- Elixir SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +60,40 @@ Provides Elixir-specific expertise for TDD development, including ExUnit testing
 - "Let it crash" philosophy with supervisors
 
 ## Examples
+```bash
+mix test && mix credo --strict
+```
+
+## 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 ExUnit
-User: "/alfred:2-build SERVER-001"
-Claude: (creates RED test with ExUnit, GREEN GenServer 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: Credo analysis
-User: "Credo 분석 실행"
-Claude: (runs mix credo --strict 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
+- Elixir Lang. "Getting Started." https://elixir-lang.org/getting-started/introduction.html (accessed 2025-03-29).
+- Credo. "Credo — The Elixir Linter." https://hexdocs.pm/credo/ (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 (Elixir-specific review)
 - web-api-expert (Phoenix 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-go/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-go
-description: Go best practices with go test, golint, gofmt, and standard library utilization
+description: Go best practices with go test, golint, gofmt, and standard library utilization. Use when writing or reviewing Go code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Go Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Go code discussions, framework guidance, or file extensions such as .go. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Go-specific expertise for TDD development, including go test framework, golint/staticcheck, gofmt formatting, and effective standard library usage.
 
 ## When to use
 
-- "Go 테스트 작성", "go test 사용법", "Go 표준 라이브러리"
+- Engages when the conversation references Go work, frameworks, or files like .go.
+- “Writing Go tests”, “How to use go tests”, “Go standard library”
 - Automatically invoked when working with Go projects
-- Go SPEC implementation (`/alfred:2-build`)
+- Go SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +61,40 @@ Provides Go-specific expertise for TDD development, including go test framework,
 - Avoid naked returns in large functions
 
 ## Examples
+```bash
+go test ./... && golangci-lint run
+```
+
+## 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 table-driven tests
-User: "/alfred:2-build PARSE-001"
-Claude: (creates RED test with table-driven approach, 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: Coverage check
-User: "go test 커버리지 확인"
-Claude: (runs go test -cover ./... and reports coverage)
+## 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
+- The Go Authors. "Effective Go." https://go.dev/doc/effective_go (accessed 2025-03-29).
+- GolangCI. "golangci-lint Documentation." https://golangci-lint.run/usage/quick-start/ (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 (Go-specific review)
 - alfred-performance-optimizer (Go 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-haskell/SKILL.md

@@ -1,22 +1,32 @@
 ---
+
 name: moai-lang-haskell
-description: Haskell best practices with HUnit, Stack/Cabal, and pure functional programming
+description: Haskell best practices with HUnit, Stack/Cabal, and pure functional programming. Use when writing or reviewing Haskell code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Haskell Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Haskell code discussions, framework guidance, or file extensions such as .hs. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Haskell-specific expertise for TDD development, including HUnit testing, Stack/Cabal build tools, and pure functional programming with strong type safety.
 
 ## When to use
 
-- "Haskell 테스트 작성", "HUnit 사용법", "순수 함수형 프로그래밍"
+- Engages when the conversation references Haskell work, frameworks, or files like .hs.
+- “Writing Haskell tests”, “How to use HUnit”, “Pure functional programming”
 - Automatically invoked when working with Haskell projects
-- Haskell SPEC implementation (`/alfred:2-build`)
+- Haskell SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -51,17 +61,40 @@ Provides Haskell-specific expertise for TDD development, including HUnit testing
 - Avoid do-notation overuse
 
 ## Examples
+```bash
+cabal test && hlint src
+```
+
+## 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 HUnit
-User: "/alfred:2-build PARSE-001"
-Claude: (creates RED test with HUnit, GREEN implementation with pure 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: Property testing
-User: "QuickCheck 속성 테스트"
-Claude: (creates property-based tests for invariants)
+## 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
+- Haskell.org. "Haskell Language Documentation." https://www.haskell.org/documentation/ (accessed 2025-03-29).
+- GitHub. "HLint." https://github.com/ndmitchell/hlint (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 (Haskell-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-java/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-java
-description: Java best practices with JUnit, Maven/Gradle, Checkstyle, and Spring
-  Boot patterns
+description: Java best practices with JUnit, Maven/Gradle, Checkstyle, and Spring Boot patterns. Use when writing or reviewing Java code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Java Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Java code discussions, framework guidance, or file extensions such as .java. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Java-specific expertise for TDD development, including JUnit testing, Maven/Gradle build tools, Checkstyle linting, and Spring Boot patterns.
 
 ## When to use
 
-- "Java 테스트 작성", "JUnit 사용법", "Spring Boot 패턴"
+- Engages when the conversation references Java work, frameworks, or files like .java.
+- “Writing Java tests”, “How to use JUnit”, “Spring Boot patterns”
 - Automatically invoked when working with Java projects
-- Java SPEC implementation (`/alfred:2-build`)
+- Java SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -50,17 +59,40 @@ Provides Java-specific expertise for TDD development, including JUnit testing, M
 - Exception handling with custom exceptions
 
 ## Examples
+```bash
+./mvnw test && ./mvnw checkstyle: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 JUnit
-User: "/alfred:2-build SERVICE-001"
-Claude: (creates RED test with JUnit 5, GREEN implementation, REFACTOR with interfaces)
+## 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: Build execution
-User: "Maven 빌드 실행"
-Claude: (runs mvn clean test and reports results)
+## 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
+- Oracle. "Java Language Specification." https://docs.oracle.com/javase/specs/ (accessed 2025-03-29).
+- JUnit. "JUnit 5 User Guide." https://junit.org/junit5/docs/current/user-guide/ (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 (Java-specific review)
 - database-expert (JPA/Hibernate patterns)
+
+## 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.