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

moai_adk/templates/.claude/skills/moai-alfred-tui-survey/examples.md

@@ -1,62 +0,0 @@
-# Alfred TUI Survey Examples
-
-## Single-select template
-
-```typescript
-AskUserQuestion({
-  questions: [{
-    header: "Decision point: Deployment Strategy",
-    question: "How should we roll out the new release?",
-    options: [
-      {
-        label: "Canary release",
-        description: "Gradually roll out to a small user segment; monitor metrics first."
-      },
-      {
-        label: "Blue/Green",
-        description: "Keep the current version live while preparing the new stack in parallel."
-      },
-      {
-        label: "Full deploy",
-        description: "Immediate production rollout after smoke tests succeed."
-      }
-    ],
-    multiSelect: false
-  }]
-})
-```
-
-## Multi-select variation
-
-```typescript
-AskUserQuestion({
-  questions: [{
-    header: "Select diagnostics to run",
-    question: "Which checks should run before proceeding?",
-    options: [
-      { label: "Unit tests", description: "Fast verification for core modules." },
-      { label: "Integration tests", description: "Service-level interactions and DB calls." },
-      { label: "Security scan", description: "Dependency vulnerability audit." }
-    ],
-    multiSelect: true
-  }]
-})
-```
-
-## Follow-up prompt for deeper detail
-
-```typescript
-if (selection.includes("Integration tests")) {
-  AskUserQuestion({
-    questions: [{
-      header: "Integration test scope",
-      question: "Which environment should host integration tests?",
-      options: [
-        { label: "Staging", description: "Use the shared staging cluster." },
-        { label: "Ephemeral env", description: "Provision a one-off test environment." }
-      ],
-      multiSelect: false
-    }]
-  })
-}
-```

moai_adk/templates/.claude/skills/moai-claude-code/SKILL.md

@@ -1,94 +0,0 @@
----
-
-name: moai-claude-code
-description: Scaffolds and audits Claude Code agents, commands, skills, plugins, and settings with production templates. Use when configuring or reviewing Claude Code automation inside MoAI workflows.
-allowed-tools:
-  - Read
-  - Write
-  - Edit
----
-
-# MoAI Claude Code Manager
-
-## Skill Metadata
-| Field | Value |
-| ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file) |
-| Auto-load | SessionStart (Claude Code bootstrap) |
-| Trigger cues | Agent/command/skill/plugin/settings authoring, Claude Code environment setup. |
-
-Create and manage Claude Code's five core components according to official standards.
-
-## Components covered
-
-- **Agents** `.claude/agents/` — Persona, tools, and workflow definition
-- **Commands** `.claude/commands/` — Slash command entry points
-- **Skills** `.claude/skills/` — Reusable instruction capsules
-- **Plugins** `settings.json › mcpServers` — MCP integrations
-- **Settings** `.claude/settings.json` — Tool permissions, hooks, session defaults
-
-## Reference files
-
-- `reference.md` — Writing guide and checklist
-- `examples.md` — Sample completed artifacts
-- `templates/` — Markdown/JSON skeleton for five components
-- `scripts/` — settings validation and template integrity check scripts
-
-## Workflow
-
-1. Analyze user requests to determine required components (Agent/Command/Skill/Plugin/Settings).
-2. Copy the stub from `templates/` and replace the placeholders to suit your project context.
-3. If necessary, run the `scripts/` verifier to check required fields, permissions, and follow-up links.
-
-## Guardrails
-
-- Maintain minimum privileges and progressive disclosure in line with Anthropic official guidelines.
-- Rather than modifying the template directly, only update the hook/field guided by reference.md.
-- The created files and settings.json are included in Git version management and a change history is left.
-
-**Official documentation**: https://docs.claude.com/en/docs/claude-code/skills  
-**Version**: 1.0.0
-
-## Examples
-```markdown
-- Create a spec-builder agent and the /alfred command set in a new project.
-- Review existing settings.json to update allowable tools and hook configurations.
-```
-
-## Best Practices
-- The output template is designed to be idempotent so that it is safe even when reapplied.
-- Detailed procedures are separated into reference.md (writing guide) and examples.md (sample artifacts) and loaded only when necessary.
-
-## When to use
-- Activates when someone asks to scaffold or audit Claude Code components.
-- When bootstrapping a Claude Code configuration to a new project.
-- When reexamining existing agents/commands/skills/plug-ins to meet standards.
-- When verification of settings is required in initialization workflows such as `/alfred:0-project`.
-
-## What it does
-- Create and update the five core components as official templates.
-- Verify accepted tools, model selection, and progressive disclosure links.
-- Provides reusable stubs and verification procedures through templates/·scripts/ resources.
-
-## Inputs
-- User configuration requests (e.g. “add new command”, “review settings.json”) and current `.claude/` directory state.
-- Project-specific template requirements or security/permissions policies.
-
-## Outputs
-- Official Markdown definition file under `.claude/agents|commands|skills/`.
-- A summary of `.claude/settings.json` that reflects the latest settings and allowed tools and follow-up TODOs.
-
-## Failure Modes
-- If the template path or placeholder is different from the latest version, the result may be damaged.
-- The settings.json permission policy may conflict with project rules or may block verification script execution.
-
-## Dependencies
-- When used with cc-manager, doc-syncer, and moai-foundation-git, the creation → verification → distribution flow is completed.
-- You must have versioned resources in the templates/ and scripts/ directories for automation to work properly.
-
-## References
-- Anthropic. "Claude Code Style Guide." https://docs.claude.com/ (accessed 2025-03-29).
-- Prettier. "Opinionated Code Formatter." https://prettier.io/docs/en/ (accessed 2025-03-29).
-
-## Changelog
-- 2025-03-29: Added best practice structure to Claude code formatting skill.

moai_adk/templates/.claude/skills/moai-claude-code/examples.md

@@ -1,513 +0,0 @@
-# Claude Code collection of practical examples
-
-> **Actual working example code**
->
-> Proven examples that can be copied and used immediately
-
----
-
-## 📋 Table of Contents
-
-1. [Agent example](#1-agent-example)
-2. [Command example](#2-command-example)
-3. [Skill example](#3-skill-example)
-4. [Plugin example](#4-plugin-example)
-5. [Settings example](#5-settings-example)
-
----
-
-## 1. Agent example
-
-### Example 1: spec-builder (MoAI-ADK)
-
-**File**: `.claude/agents/alfred/spec-builder.md`
-
-```markdown
----
-name: spec-builder
-description: "Use when: When writing SPEC, EARS specification, and requirements analysis are necessary."
-tools: Read, Write, Edit, MultiEdit, Grep, Glob, Bash, TodoWrite
-model: sonnet
----
-
-# SPEC Builder 🏗️ - System Architect
-
-**MoAI-ADK SPEC writing expert**
-
-## 🎭 Agent Persona
-
-**Icon**: 🏗️
-**Job**: System Architect
-**Area of ​​Expertise**: SPEC writing, EARS specification, requirements analysis
-**Role**: Convert business requirements into structured SPECs
-**Goal**: Create clear and testable SPEC documents.
-
-## 🎯 Key Role
-
-### 1. Create SPEC document
-- Apply EARS 5 syntax
-- YAML Front Matter 7 required fields
-- HISTORY section management
-
-### 2. Auto-execution conditions
-- When executing the `/alfred:1-plan` command
-- When a new function requirement occurs
-- When requesting improvement of the existing SPEC
-
-## 📐 Workflow
-
-### STEP 1: Project document analysis
-\`\`\`bash
-# read product.md
-Read .moai/project/product.md
-
-# Check existing SPEC
-ls .moai/specs/SPEC-*/spec.md
-\`\`\`
-
-### STEP 2: Draft SPEC
-\`\`\`bash
-Write .moai/specs/SPEC-{ID}/spec.md
-\`\`\`
-
-## 💡 User Guide
-\`\`\`bash
-@agent-spec-builder "Create a user authentication function SPEC"
-\`\`\`
-```
-
-### Example 2: code-analyzer (simple analysis agent)
-
-**File**: `.claude/agents/code-analyzer.md`
-
-```markdown
----
-name: code-analyzer
-description: Use when: code quality analysis is needed
-tools: Read, Grep, Bash(rg:*)
-model: haiku
----
-
-# Code Analyzer 🔍 - Quality Manager
-
-Analyze code quality metrics and provide improvement suggestions.
-
-## 🎭 Agent Persona
-
-**Icon**: 🔍
-**Job**: Quality Manager
-**Area of ​​Expertise**: Code quality analysis, linting, test coverage
-**Role**: Measure code quality metrics and suggest improvements
-**Goal**: Maintain high code quality
-
-## 🎯 Key Role
-
-### 1. Collect quality indicators
-- Check test coverage
-- Detect linting errors
-- Complexity analysis
-
-### 2. Conditions for automatic execution
-- When quality verification is requested before commit
-- Automatic verification before creating PR
-
-## 📐 Workflow
-
-### STEP 1: Scan code
-\`\`\`bash
-rg "@TEST:" -n tests/
-pytest --cov
-\`\`\`
-
-### STEP 2: Generate report
-- Coverage: {percentage}%
-- Linting errors: {count}
-
-## 💡 User Guide
-\`\`\`bash
-@agent-code-analyzer "Analyze current project quality"
-\`\`\`
-```
-
----
-
-## 2. Command example
-
-### Example 1: /alfred:1-plan (MoAI-ADK)
-
-**File**: `.claude/commands/alfred/1-spec.md`
-
-```markdown
----
-name: alfred:1-spec
-description: Project document analysis and SPEC creation (EARS method)
-argument-hint: [feature-description]
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Task
-  - Grep
-  - Glob
-  - TodoWrite
-  - Bash(git:*)
----
-
-# 📋 MoAI-ADK Step 1: Write SPEC
-
-## 🎯 Command Purpose
-
-Analyze project documents, create SPEC documents using the EARS method, and create Git branches.
-
-## 💡 Example of use
-\`\`\`bash
-/alfred:1-plan "User authentication function"
-\`\`\`
-
-## 📋 Execution flow
-
-1. **Phase 1**: Analyze project document
- - Read product.md
- - Check existing SPEC
-
-2. **Phase 2**: SPEC creation
- - EARS method specification
- - Git branch creation
-
-## 🔗 Associated Agent
-
-- **Primary**: spec-builder (🏗️ System Architect)
-- **Secondary**: git-manager (🚀 Release Engineer)
-
-## ⚠️ Precautions
-
-- SPEC ID duplication check required
-- Compliance with EARS 5 phrases
-
-## 📋 Next steps
-
-- `/alfred:2-run SPEC-{ID}` - Start TDD implementation
-```
-
-### Example 2: /deploy-api (deploy command)
-
-**File**: `.claude/commands/deploy-api.md`
-
-```markdown
----
-name: deploy-api
-description: Deploy API server to production environment
-argument-hint: [environment]
-allowed-tools:
-  - Read
-  - Bash(git:*)
-  - Bash(npm:*)
----
-
-# 🚀 API deployment command
-
-Deploys the API server to the specified environment.
-
-## 🎯 Command Purpose
-
-Automate Git tag creation and deployment by environment
-
-## 💡 Example of use
-\`\`\`bash
-/deploy-api production
-/deploy-api staging
-\`\`\`
-
-## 📋 Execution flow
-
-1. **Phase 1**: Check Git status
- - Check current branch (main required)
- - Create version tag
-
-2. **Phase 2**: Deployment execution
-   - npm run build
-- Execute deployment script for each environment
-
-## ⚠️ Precautions
-
-- Can only be run from the main branch
-- Must pass all tests
-```
-
----
-
-## 3. Skill example
-
-### Example 1: moai-alfred-tag-scanning
-
-**File**: `.claude/skills/moai-alfred-tag-scanning/SKILL.md`
-
-```markdown
----
-name: moai-alfred-tag-scanning
-description: Directly scan TAG markers and create inventory (CODE-FIRST principle)
-model: haiku
-allowed-tools:
-  - Grep
-  - Read
----
-
-# TAG scanner
-
-> CODE-FIRST principle: scan code directly without intermediate cache
-
-## 🎯 Purpose
-
-Scan `@SPEC`, `@TEST`, `@CODE`, and `@DOC` TAGs directly from your code.
-
-## 💡 How to use
-
-“Check AUTH domain TAG list”
-
-## 📋 How to scan
-
-\`\`\`bash
-rg '@(SPEC|TEST|CODE|DOC):' -n .moai/specs/ tests/ src/ docs/
-\`\`\`
-
-## ✅ Verification
-
-- Does every `@CODE` TAG have a corresponding `@SPEC`?
-- No orphan TAGs
-```
-
-### Example 2: moai-alfred-feature-selector
-
-**File**: `.claude/skills/moai-alfred-feature-selector/SKILL.md`
-
-```markdown
----
-name: moai-alfred-feature-selector
-description: Select optimal functions for each project type (37 skills → automatically filter 3 to 5)
-model: haiku
-allowed-tools:
-  - Read
----
-
-# MoAI Alfred Feature Selector
-
-> Automatic selection of MoAI-ADK functions suitable for project characteristics
-
-## 🎯 Purpose
-
-Analyze your project type and select only the features you need.
-
-## 📋 Project classification
-
-### By language
-- **Python**: pytest, mypy, ruff
-- **TypeScript**: Vitest, Biome
-
-### Domain-specific
-- **CLI Tool**: Argument parsing, POSIX compliance
-- **Web API**: REST/GraphQL, authentication
-
-## 💡 How to use
-
-"Automatically called when running /alfred:0-project"
-```
-
----
-
-## 4. Plugin example
-
-### Example 1: GitHub + Filesystem (default)
-
-**FILE**: `.claude/settings.json` (mcpServers section)
-
-```json
-{
-  "mcpServers": {
-    "github": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_TOKEN": "${GITHUB_TOKEN}"
-      }
-    },
-    "filesystem": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-filesystem",
-        "${CLAUDE_PROJECT_DIR}/src",
-        "${CLAUDE_PROJECT_DIR}/tests"
-      ]
-    }
-  }
-}
-```
-
-### Example 2: Fully configured MoAI-ADK
-
-```json
-{
-  "mcpServers": {
-    "github": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_TOKEN": "${GITHUB_TOKEN}"
-      }
-    },
-    "moai-filesystem": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-filesystem",
-        "${CLAUDE_PROJECT_DIR}/.moai",
-        "${CLAUDE_PROJECT_DIR}/src",
-        "${CLAUDE_PROJECT_DIR}/tests",
-        "${CLAUDE_PROJECT_DIR}/docs"
-      ]
-    },
-    "brave-search": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-brave-search"],
-      "env": {
-        "BRAVE_API_KEY": "${BRAVE_API_KEY}"
-      }
-    }
-  }
-}
-```
-
----
-
-## 5. Settings example
-
-### Example 1: Python project
-
-**File**: `.claude/settings.json`
-
-```json
-{
-  "permissions": {
-    "defaultMode": "default",
-    "allow": [
-      "Read",
-      "Write",
-      "Edit",
-      "Grep",
-      "Glob",
-      "Bash(git:*)",
-      "Bash(python:*)",
-      "Bash(pytest:*)",
-      "Bash(mypy:*)",
-      "Bash(ruff:*)"
-    ],
-    "ask": [
-      "Bash(pip install:*)",
-      "Bash(git push:*)"
-    ],
-    "deny": [
-      "Read(./.env)",
-      "Bash(sudo:*)",
-      "Bash(rm -rf:*)"
-    ]
-  }
-}
-```
-
-### Example 2: TypeScript project
-
-```json
-{
-  "permissions": {
-    "defaultMode": "default",
-    "allow": [
-      "Read",
-      "Write",
-      "Edit",
-      "Grep",
-      "Glob",
-      "Bash(git:*)",
-      "Bash(node:*)",
-      "Bash(npm:*)",
-      "Bash(pnpm:*)"
-    ],
-    "ask": [
-      "Bash(npm install:*)",
-      "Bash(pnpm install:*)",
-      "Bash(git push:*)"
-    ],
-    "deny": [
-      "Read(./.env)",
-      "Read(./secrets/**)",
-      "Bash(sudo:*)",
-      "Bash(rm -rf:*)"
-    ]
-  }
-}
-```
-
-### Example 3: MoAI-ADK project (with hooks)
-
-```json
-{
-  "permissions": {
-    "defaultMode": "default",
-    "allow": [
-      "Task",
-      "Read",
-      "Write",
-      "Edit",
-      "MultiEdit",
-      "Grep",
-      "Glob",
-      "TodoWrite",
-      "Bash(git:*)",
-      "Bash(python:*)",
-      "Bash(pytest:*)",
-      "Bash(mypy:*)",
-      "Bash(ruff:*)",
-      "Bash(moai-adk:*)",
-      "Bash(alfred:*)"
-    ],
-    "ask": [
-      "Bash(git push:*)",
-      "Bash(pip install:*)"
-    ],
-    "deny": [
-      "Read(./.env)",
-      "Read(./secrets/**)",
-      "Bash(sudo:*)",
-      "Bash(rm -rf:*)"
-    ]
-  },
-  "hooks": {
-    "SessionStart": [
-      {
-        "hooks": [
-          {
-            "command": "node $CLAUDE_PROJECT_DIR/.claude/hooks/alfred/session-notice.cjs",
-            "type": "command"
-          }
-        ],
-        "matcher": "*"
-      }
-    ],
-    "PreToolUse": [
-      {
-        "hooks": [
-          {
-            "command": "node $CLAUDE_PROJECT_DIR/.claude/hooks/alfred/pre-write-guard.cjs",
-            "type": "command"
-          }
-        ],
-        "matcher": "Edit|Write|MultiEdit"
-      }
-    ]
-  }
-}
-```
-
----
-
-**Last update**: 2025-10-19
-**Author**: @Alfred