moai-adk 0.4.5__py3-none-any.whl → 0.20.1__py3-none-any.whl

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

@@ -1,100 +0,0 @@
----
-
-name: moai-lang-haskell
-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
----
-
-# 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
-
-- 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-run`)
-
-## How it works
-
-**TDD Framework**:
-- **HUnit**: Unit testing framework
-- **QuickCheck**: Property-based testing
-- **Hspec**: BDD-style testing
-- Test coverage with hpc
-
-**Build Tools**:
-- **Stack**: Reproducible builds, dependency resolution
-- **Cabal**: Haskell package system
-- **hpack**: Alternative package description
-
-**Code Quality**:
-- **hlint**: Haskell linter
-- **stylish-haskell**: Code formatting
-- **GHC warnings**: Compiler-level checks
-
-**Functional Programming**:
-- **Pure functions**: No side effects
-- **Monads**: IO, Maybe, Either, State
-- **Functors/Applicatives**: Abstraction patterns
-- **Type classes**: Polymorphism
-- **Lazy evaluation**: Infinite data structures
-
-**Best Practices**:
-- File ≤300 LOC, function ≤50 LOC
-- Prefer total functions (avoid partial)
-- Type-driven development
-- Point-free style (when readable)
-- 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.
-
-## Failure Modes
-- When the language runtime or package manager is not installed.
-- When the main language cannot be determined in a multilingual project.
-
-## 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-julia/SKILL.md

@@ -1,98 +0,0 @@
----
-
-name: moai-lang-julia
-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
----
-
-# 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
-
-- 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-run`)
-
-## How it works
-
-**TDD Framework**:
-- **Test**: Built-in testing library (@test, @testset)
-- **Coverage.jl**: Test coverage analysis
-- **BenchmarkTools.jl**: Performance benchmarking
-
-**Package Management**:
-- **Pkg**: Built-in package manager
-- **Project.toml**: Package configuration
-- **Manifest.toml**: Dependency lock file
-
-**Code Quality**:
-- **JuliaFormatter.jl**: Code formatting
-- **Lint.jl**: Static analysis
-- **JET.jl**: Type inference analysis
-
-**Scientific Computing**:
-- **Multiple dispatch**: Method specialization on argument types
-- **Type stability**: Performance optimization
-- **Broadcasting**: Element-wise operations (. syntax)
-- **Linear algebra**: Built-in BLAS/LAPACK
-
-**Best Practices**:
-- File ≤300 LOC, function ≤50 LOC
-- Type annotations for performance-critical code
-- Prefer abstract types for function arguments
-- Use @inbounds for performance (after bounds checking)
-- 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.
-
-## Failure Modes
-- When the language runtime or package manager is not installed.
-- When the main language cannot be determined in a multilingual project.
-
-## 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-lua/SKILL.md

@@ -1,98 +0,0 @@
----
-
-name: moai-lang-lua
-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
----
-
-# 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
-
-- 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-run`)
-
-## How it works
-
-**TDD Framework**:
-- **busted**: Elegant Lua testing framework
-- **luassert**: Assertion library
-- **lua-coveralls**: Coverage reporting
-- BDD-style test writing
-
-**Code Quality**:
-- **luacheck**: Lua linter and static analyzer
-- **StyLua**: Code formatting
-- **luadoc**: Documentation generation
-
-**Package Management**:
-- **LuaRocks**: Package manager
-- **rockspec**: Package specification
-
-**Lua Patterns**:
-- **Tables**: Versatile data structure
-- **Metatables**: Operator overloading
-- **Closures**: Function factories
-- **Coroutines**: Cooperative multitasking
-
-**Best Practices**:
-- File ≤300 LOC, function ≤50 LOC
-- Use `local` for all variables
-- Prefer tables over multiple return values
-- Document public APIs
-- 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.
-
-## Failure Modes
-- When the language runtime or package manager is not installed.
-- When the main language cannot be determined in a multilingual project.
-
-## 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/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,69 +0,0 @@
-# MoAI-ADK GitFlow PR
-
-> 🗿 Full GitFlow Transparency — the agent auto-fills information
-
-## 📝 SPEC Info
-
-- Related SPEC: `SPEC-AUTH-001` (e.g., JWT authentication system)
-- Directory: `.moai/specs/SPEC-AUTH-001/`
-- @TAG Links: @SPEC:AUTH-001 @CODE:AUTH-001 (auto-tagging)
-
-## ✅ SPEC Quality Checks
-
-- [ ] YAML Front Matter: 7 required fields (id, version, status, created, updated, author, priority)
-- [ ] HISTORY Section: Record versioned change log (include v0.0.1 INITIAL)
-- [ ] EARS Requirements: Ubiquitous, Event-driven, State-driven, Optional, Constraints
-- [ ] @SPEC:ID TAG: Include TAG in doc and check duplicates (`rg "@SPEC:<ID>" -n`)
-
-## 🤖 Automated Validation Status
-
-<!-- The checklist below is auto-updated by the agent -->
-<!-- /alfred:1-plan → create feature branch → Draft PR -->
-<!-- /alfred:2-run → implement via TDD → auto-check checkboxes -->
-<!-- /alfred:3-sync → synchronize documents → Ready for Review -->
-
-- [ ] spec-builder: Complete EARS spec and create feature branch
-- [ ] code-builder: Finish TDD RED-GREEN-REFACTOR
-- [ ] doc-syncer: Sync Living Documents and mark PR Ready
-
-## 📊 Quality Metrics (auto-calculated)
-
-- TRUST 5 Principles: ✅ Compliant
-- Test Coverage: XX% (target ≥ 85%)
-- @TAG Traceability: 100%
-
-## 🌍 Locale Settings
-
-- Project Language: <!-- ko/en/ja/zh -->
-- Commit Messages: <!-- generated automatically according to locale -->
-
-## 🎯 Changes
-
-<!-- code-builder auto-fills TDD results -->
-
-### 🔴 RED (Test Authoring)
-- Test File: `tests/auth/service.test.ts`
-- Test Description: [describe the failing test]
-
-### 🟢 GREEN (Implementation)
-- Implementation File: `src/auth/service.ts`
-- Implementation Done: [describe functionality]
-
-### ♻️ REFACTOR (Improvements)
-- Refactoring Details: [code quality improvements]
-
-## 📚 Documentation Sync
-
-<!-- auto-filled by doc-syncer -->
-
-- [ ] Update README
-- [ ] Sync API docs
-- [ ] Update TAG index
-- [ ] Update HISTORY section (SPEC docs)
-
----
-
-🚀 MoAI-ADK: Professional development without Git commands via a 3-stage pipeline!
-
-Reviewers: Check TRUST 5 compliance and SPEC metadata completeness only.
-