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

moai_adk/templates/.claude/skills/moai-foundation-git/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-foundation-git
-description: Git workflow automation (branching, TDD commits, PR management)
+description: Git workflow automation (branching, TDD commits, PR management). Use when standardizing Git practices across the project.
 allowed-tools:
-- Read
-- Bash
-- Write
-- Edit
-- TodoWrite
+  - Read
+  - Bash
+  - Write
+  - Edit
+  - TodoWrite
 ---
 
 # Alfred Git Workflow
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | SessionStart (foundation bootstrap) |
+| Trigger cues | Branch creation, commit convention, PR readiness, and release gating requests. |
+
 ## What it does
 
 Automates Git operations following MoAI-ADK conventions: branch creation, locale-based TDD commits, Draft PR creation, and PR Ready transition.
 
 ## When to use
 
-- "브랜치 생성", "PR 만들어줘", "커밋 생성"
+- Activates when Git workflow automation is needed for branching, commits, or PR promotion.
+- “Create branch”, “Create PR”, “Create commit”
 - Automatically invoked by `/alfred:1-plan`, `/alfred:2-run`, `/alfred:3-sync`
 - Git workflow automation needed
 
@@ -30,7 +39,7 @@ git checkout -b feature/SPEC-AUTH-001
 ```
 
 **2. Locale-based TDD Commits**:
-- **Korean (ko)**: 🔴 RED: [테스트 설명]
+- **Korean (ko)**: 🔴 RED: [Test Description]
 - **English (en)**: 🔴 RED: [Test description]
 - **Japanese (ja)**: 🔴 RED: [テスト説明]
 - **Chinese (zh)**: 🔴 RED: [测试说明]
@@ -49,15 +58,33 @@ Creates Draft PR with SPEC reference and test checklist.
 - Verifies TRUST 5-principles
 
 ## Examples
+```markdown
+- Scan standard documents and report missing sections.
+- Changed regulations are reflected in CLAUDE.md.
+```
+
+## Best Practices
+- When changing standards, the reason for change and supporting documents are recorded.
+- Follow the single source principle and avoid modifying the same item in multiple places.
+
+## Inputs
+- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
+- Latest printouts from relevant sub-agents.
+
+## Outputs
+- Templates or policy summaries conforming to the MoAI-ADK standard.
+- Reusable rules/checklists.
+
+## Failure Modes
+- When required standard files are missing or have limited access rights.
+- When conflicting policies are detected and coordination is required.
 
-### Example 1: Create feature branch
-User: "/alfred:1-plan JWT 인증"
-Claude: (creates `feature/SPEC-AUTH-001` branch and Draft PR)
+## Dependencies
+- There is great synergy when called together with cc-manager.
 
-### Example 2: TDD commit
-User: "/alfred:2-run AUTH-001"
-Claude: (commits with locale-specific format: 🔴 RED, 🟢 GREEN, ♻️ REFACTOR)
+## References
+- Vincent Driessen. "A successful Git branching model." https://nvie.com/posts/a-successful-git-branching-model/ (accessed 2025-03-29).
+- GitHub Docs. "GitHub Flow." https://docs.github.com/en/get-started/using-github/github-flow (accessed 2025-03-29).
 
-### Example 3: Finalize PR
-User: "/alfred:3-sync"
-Claude: (transitions PR to Ready state with quality report)
+## Changelog
+- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.

moai_adk/templates/.claude/skills/moai-foundation-langs/SKILL.md

@@ -1,24 +1,32 @@
 ---
+
 name: moai-foundation-langs
-description: Auto-detects project language and framework (package.json, pyproject.toml,
-  etc)
+description: Auto-detects project language and framework (package.json, pyproject.toml, etc). Use when referencing multi-language conventions.
 allowed-tools:
-- Read
-- Bash
-- Write
-- Edit
-- TodoWrite
+  - Read
+  - Bash
+  - Write
+  - Edit
+  - TodoWrite
 ---
 
 # Alfred Language Detection
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | SessionStart (foundation bootstrap) |
+| Trigger cues | Project language detection, toolchain hints, multi-language repository setup questions. |
+
 ## What it does
 
 Automatically detects project's primary language and framework by scanning configuration files, then recommends appropriate testing tools and linters.
 
 ## When to use
 
-- "언어 감지", "프로젝트 언어 확인", "테스트 도구 추천"
+- Activates when the conversation needs to detect project languages or recommend toolchains.
+- "Detect language", "Check project language", "Recommend testing tools"
 - Automatically invoked by `/alfred:0-project`, `/alfred:2-run`
 - Setting up new project
 
@@ -54,11 +62,33 @@ Automatically detects project's primary language and framework by scanning confi
 **Supported Languages**: Python, TypeScript, Java, Go, Rust, Ruby, Dart, Swift, Kotlin, PHP, C#, C++, Elixir, Scala, Clojure (20+ languages)
 
 ## Examples
+```markdown
+- Scan standard documents and report missing sections.
+- Changed regulations are reflected in CLAUDE.md.
+```
+
+## Best Practices
+- When changing standards, the reason for change and supporting documents are recorded.
+- Follow the single source principle and avoid modifying the same item in multiple places.
+
+## Inputs
+- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
+- Latest printouts from relevant sub-agents.
+
+## Outputs
+- Templates or policy summaries conforming to the MoAI-ADK standard.
+- Reusable rules/checklists.
+
+## Failure Modes
+- When required standard files are missing or have limited access rights.
+- When conflicting policies are detected and coordination is required.
+
+## Dependencies
+- There is great synergy when called together with cc-manager.
 
-### Example 1: Auto-detect project language
-User: "/alfred:0-project"
-Claude: (scans config files, detects Python, recommends pytest + ruff + black)
+## References
+- JetBrains. "Multi-language project organization." https://www.jetbrains.com/help/idea/project-tool-window.html (accessed 2025-03-29).
+- Stack Overflow. "Multi-language repository patterns." https://stackoverflow.blog/2020/04/20/the-developer's-guide-to-multi-language-repos/ (accessed 2025-03-29).
 
-### Example 2: Manual detection
-User: "이 프로젝트는 무슨 언어?"
-Claude: (analyzes config files and reports language + framework)
+## Changelog
+- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.

moai_adk/templates/.claude/skills/moai-foundation-specs/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-foundation-specs
-description: Validates SPEC YAML frontmatter (7 required fields) and HISTORY section
+description: Validates SPEC YAML frontmatter (7 required fields) and HISTORY section. Use when enforcing SPEC documentation standards.
 allowed-tools:
-- Read
-- Bash
-- Write
-- Edit
-- TodoWrite
+  - Read
+  - Bash
+  - Write
+  - Edit
+  - TodoWrite
 ---
 
 # Alfred SPEC Metadata Validation
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | SessionStart (foundation bootstrap) |
+| Trigger cues | SPEC metadata validation, frontmatter completeness, specification readiness checks. |
+
 ## What it does
 
 Validates SPEC document structure including YAML frontmatter (7 required fields) and HISTORY section compliance.
 
 ## When to use
 
-- "SPEC 검증", "메타데이터 확인", "SPEC 구조 체크"
+- Activates when verifying SPEC frontmatter or preparing new specification templates.
+- "SPEC verification", "Metadata check", "SPEC structure check"
 - Automatically invoked by `/alfred:1-plan`
 - Before creating SPEC document
 
@@ -47,15 +56,38 @@ rg "^## HISTORY" .moai/specs/SPEC-*/spec.md
 ```
 
 ## Examples
+```markdown
+- Scan standard documents and report missing sections.
+- Changed regulations are reflected in CLAUDE.md.
+```
+
+## Inputs
+- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
+- Latest printouts from relevant sub-agents.
+
+## Outputs
+- Templates or policy summaries conforming to the MoAI-ADK standard.
+- Reusable rules/checklists.
 
-### Example 1: Validate SPEC structure
-User: "SPEC-AUTH-001 메타데이터 확인해줘"
-Claude: (validates YAML frontmatter and HISTORY section, reports issues)
+## Failure Modes
+- When required standard files are missing or have limited access rights.
+- When conflicting policies are detected and coordination is required.
+
+## Dependencies
+- There is great synergy when called together with cc-manager.
+
+## References
+- INCOSE. "Guide for Writing Requirements." INCOSE-TP-2010-006-02 (accessed 2025-03-29).
+- IEEE. "Software Requirements Specification Standard." IEEE 830-1998.
+
+## Changelog
+- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.
 
-### Example 2: Batch validation
-User: "모든 SPEC 메타데이터 검증"
-Claude: (validates all SPEC documents and generates report)
 ## Works well with
 
 - moai-foundation-ears
 - moai-foundation-tags
+
+## Best Practices
+- When changing standards, the reason for change and supporting documents are recorded.
+- Follow the single source principle and avoid modifying the same item in multiple places.

moai_adk/templates/.claude/skills/moai-foundation-tags/SKILL.md

@@ -1,25 +1,34 @@
 ---
+
 name: moai-foundation-tags
-description: Scans @TAG markers directly from code and generates inventory (CODE-FIRST)
+description: Scans @TAG markers directly from code and generates inventory (CODE-FIRST). Use when establishing or auditing TAG conventions.
 allowed-tools:
-- Read
-- Bash
-- Write
-- Edit
-- TodoWrite
+  - Read
+  - Bash
+  - Write
+  - Edit
+  - TodoWrite
 ---
 
 # Alfred TAG Scanning
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | SessionStart (foundation bootstrap) |
+| Trigger cues | TAG scanning, traceability audits, orphan TAG remediation requests. |
+
 ## What it does
 
 Scans all @TAG markers (SPEC/TEST/CODE/DOC) directly from codebase and generates TAG inventory without intermediate caching (CODE-FIRST principle).
 
 ## When to use
 
-- "TAG 스캔", "TAG 목록", "TAG 인벤토리"
+- Activates when scanning or auditing TAG chains or locating orphaned tags.
+- "TAG Scan", "TAG List", "TAG Inventory"
 - Automatically invoked by `/alfred:3-sync`
-- "고아 TAG 찾아줘", "TAG 체인 확인"
+- “Find orphan TAG”, “Check TAG chain”
 
 ## How it works
 
@@ -40,15 +49,38 @@ rg '@(SPEC|TEST|CODE|DOC):' -n .moai/specs/ tests/ src/ docs/
 - Ensures traceability across all artifacts
 
 ## Examples
+```markdown
+- Scan standard documents and report missing sections.
+- Changed regulations are reflected in CLAUDE.md.
+```
+
+## Inputs
+- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
+- Latest printouts from relevant sub-agents.
+
+## Outputs
+- Templates or policy summaries conforming to the MoAI-ADK standard.
+- Reusable rules/checklists.
 
-### Example 1: Full TAG scan
-User: "TAG 전체 스캔해줘"
-Claude: (scans all files and generates TAG inventory report)
+## Failure Modes
+- When required standard files are missing or have limited access rights.
+- When conflicting policies are detected and coordination is required.
+
+## Dependencies
+- There is great synergy when called together with cc-manager.
+
+## References
+- BurntSushi. "ripgrep User Guide." https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md (accessed 2025-03-29).
+- ReqView. "Requirements Traceability Matrix Guide." https://www.reqview.com/doc/requirements-traceability-matrix/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.
 
-### Example 2: Find orphaned TAGs
-User: "고아 TAG 찾아줘"
-Claude: (identifies TAGs without complete chain)
 ## Works well with
 
 - moai-foundation-trust
 - moai-foundation-specs
+
+## Best Practices
+- When changing standards, the reason for change and supporting documents are recorded.
+- Follow the single source principle and avoid modifying the same item in multiple places.

moai_adk/templates/.claude/skills/moai-foundation-trust/SKILL.md

@@ -1,24 +1,32 @@
 ---
+
 name: moai-foundation-trust
-description: Validates TRUST 5-principles (Test 85%+, Readable, Unified, Secured,
-  Trackable)
+description: Validates TRUST 5-principles (Test 85%+, Readable, Unified, Secured, Trackable). Use when aligning with TRUST governance.
 allowed-tools:
-- Read
-- Write
-- Edit
-- Bash
-- TodoWrite
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - TodoWrite
 ---
 
 # Foundation: TRUST Validation
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | SessionStart (foundation bootstrap) |
+| Trigger cues | TRUST compliance checks, release readiness reviews, quality gate enforcement. |
+
 ## What it does
 
 Validates MoAI-ADK's TRUST 5-principles compliance to ensure code quality, testability, security, and traceability.
 
 ## When to use
 
-- "TRUST 원칙 확인", "품질 검증", "코드 품질 체크"
+- Activates when TRUST compliance or release readiness needs to be evaluated.
+- "Check the TRUST principle", "Quality verification", "Check code quality"
 - Automatically invoked by `/alfred:3-sync`
 - Before merging PR or releasing
 
@@ -40,7 +48,39 @@ Validates MoAI-ADK's TRUST 5-principles compliance to ensure code quality, testa
 **T - Trackable**:
 - TAG chain integrity (@SPEC → @TEST → @CODE → @DOC)
 
+## Inputs
+- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
+- Latest printouts from relevant sub-agents.
+
+## Outputs
+- Templates or policy summaries conforming to the MoAI-ADK standard.
+- Reusable rules/checklists.
+
+## Failure Modes
+- When required standard files are missing or have limited access rights.
+- When conflicting policies are detected and coordination is required.
+
+## Dependencies
+- There is great synergy when called together with cc-manager.
+
+## References
+- SonarSource. "Quality Gate: Developer's Guide." https://www.sonarsource.com/company/newsroom/white-papers/quality-gate/ (accessed 2025-03-29).
+- ISO/IEC 25010. "Systems and software quality models." (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.
+
 ## Works well with
 
 - moai-foundation-tags (TAG traceability)
 - moai-foundation-specs (SPEC validation)
+
+## Examples
+```markdown
+- Scan standard documents and report missing sections.
+- Changed regulations are reflected in CLAUDE.md.
+```
+
+## Best Practices
+- When changing standards, the reason for change and supporting documents are recorded.
+- Follow the single source principle and avoid modifying the same item in multiple places.

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

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-c
-description: C best practices with Unity test framework, cppcheck, and Make build
-  system
+description: C best practices with Unity test framework, cppcheck, and Make build system. 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 .c/.h. |
+| Tier | 3 |
+
 ## What it does
 
 Provides C-specific expertise for TDD development, including Unity test framework, cppcheck static analysis, and Make build system for system programming.
 
 ## When to use
 
-- "C 테스트 작성", "Unity 테스트 프레임워크", "임베디드 C"
+- Engages when the conversation references C work, frameworks, or files like .c/.h.
+- "Writing C tests", "Unity test framework", "Embedded C"
 - Automatically invoked when working with C projects
-- C SPEC implementation (`/alfred:2-build`)
+- C SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -52,17 +61,40 @@ Provides C-specific expertise for TDD development, including Unity test framewor
 - Initialize all variables
 
 ## Examples
+```bash
+make test && cppcheck 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 Unity
-User: "/alfred:2-build DRIVER-001"
-Claude: (creates RED test with Unity, 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: Memory leak check
-User: "Valgrind 메모리 체크"
-Claude: (runs valgrind --leak-check=full and reports leaks)
+## 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 9899:2018 Programming Languages — C." (accessed 2025-03-29).
+- Cppcheck. "Cppcheck Manual." http://cppcheck.sourceforge.net/manual.pdf (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-debugger-pro (C 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-clojure/SKILL.md

@@ -1,23 +1,32 @@
 ---
+
 name: moai-lang-clojure
-description: Clojure best practices with clojure.test, Leiningen, and immutable data
-  structures
+description: Clojure best practices with clojure.test, Leiningen, and immutable data structures. Use when writing or reviewing Clojure code in project workflows.
 allowed-tools:
-- Read
-- Bash
+  - Read
+  - Bash
 ---
 
 # Clojure Expert
 
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Bash (terminal) |
+| Auto-load | On demand when language keywords are detected |
+| Trigger cues | Clojure code discussions, framework guidance, or file extensions such as .clj/.cljc. |
+| Tier | 3 |
+
 ## What it does
 
 Provides Clojure-specific expertise for TDD development, including clojure.test framework, Leiningen build tool, and immutable data structures with functional programming.
 
 ## When to use
 
-- "Clojure 테스트 작성", "clojure.test 사용법", "불변 데이터 구조"
+- Engages when the conversation references Clojure work, frameworks, or files like .clj/.cljc.
+- "Writing Clojure tests", "How to use clojure.test", "Immutable data structures"
 - Automatically invoked when working with Clojure projects
-- Clojure SPEC implementation (`/alfred:2-build`)
+- Clojure SPEC implementation (`/alfred:2-run`)
 
 ## How it works
 
@@ -52,17 +61,40 @@ Provides Clojure-specific expertise for TDD development, including clojure.test
 - Avoid mutable state
 
 ## Examples
+```bash
+lein test && clj-kondo --lint 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 clojure.test
-User: "/alfred:2-build TRANSFORM-001"
-Claude: (creates RED test with clojure.test, GREEN implementation with threading macros, 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: "test.check 속성 테스트"
-Claude: (creates generative tests with test.check)
+## 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
+- Clojure.org. "Clojure Documentation." https://clojure.org/guides/getting_started (accessed 2025-03-29).
+- clj-kondo. "User Guide." https://github.com/clj-kondo/clj-kondo/blob/master/doc/usage.md (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 (Clojure-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.