moai-adk 0.8.0__py3-none-any.whl → 1.1.0__py3-none-any.whl

moai_adk/templates/.moai/memory/SKILLS-DESCRIPTION-POLICY.md

@@ -1,218 +0,0 @@
-# Skills Description 개선 정책
-
-> MoAI-ADK의 모든 Skills에 적용되는 description 작성 표준
-
----
-
-## 🎯 설명 (Description) 작성 원칙
-
-### 1. 기본 구조
-
-모든 Skill의 description은 다음 3가지를 포함해야 합니다:
-
-```
-[What it does]: 간단한 기능 설명 (8-12 단어)
-[Key capabilities]: 핵심 기능 목록 (2-3개)
-[When to use]: 사용 시점 (3-5개 트리거 키워드, "Use when" 사용)
-```
-
-### 2. 작성 템플릿
-
-**기본 템플릿**:
-```
-description: [기능 설명]. [핵심 기능]. Use when [트리거1], [트리거2], or [트리거3].
-```
-
-**확장 템플릿** (필요 시):
-```
-description: [기능 설명]. [핵심 기능1], [핵심 기능2]. Use when [트리거1], [트리거2], [트리거3], or [트리거4]. Automatically activates [연관 Skills] for [목적].
-```
-
-### 3. Skills 카테고리별 템플릿
-
-#### Foundation Skills (moai-foundation-*)
-```
-description: [기능]. [핵심 기능 (예: validation, authoring)]. Use when [작업1], [작업2], [작업3], or [작업4].
-```
-**예시**:
-- ✅ "Validates SPEC YAML frontmatter (7 required fields) and HISTORY section. Use when creating SPEC documents, validating SPEC metadata, checking SPEC structure, or authoring specifications."
-- ❌ "SPEC metadata validation" (너무 짧음)
-
-#### Alfred Skills (moai-alfred-*)
-```
-description: [기능]. [핵심 능력]. Use when [검증/분석/관리 대상], [조건], or [상황]. Automatically activates [연관 Skills] for [목적].
-```
-**예시**:
-- ✅ "Validates TRUST 5-principles (Test 85%+, Code constraints, Architecture unity, Security, TAG trackability). Use when validating code quality, checking TRUST compliance, verifying test coverage, or analyzing security patterns. Automatically activates moai-foundation-trust and language-specific skills for comprehensive validation."
-- ❌ "TRUST validation" (너무 짧고 트리거 키워드 없음)
-
-#### Language Skills (moai-lang-*)
-```
-description: [언어] best practices with [주요 도구]. Use when [개발 활동], [패턴], or [특수 케이스].
-```
-**예시**:
-- ✅ "Python best practices with pytest, mypy, ruff, black. Use when writing Python code, implementing tests, type-checking, formatting code, or following PEP standards."
-- ❌ "Python best practices" (너무 일반적)
-
-#### Domain Skills (moai-domain-*)
-```
-description: [도메인] development with [주요 기술/패턴]. Use when [도메인 활동1], [도메인 활동2], or [특수 상황].
-```
-**예시**:
-- ✅ "Backend API development with REST patterns, authentication, error handling. Use when designing REST APIs, implementing authentication, or building backend services."
-- ❌ "Backend development" (구체성 부족)
-
-### 4. 트리거 키워드 가이드
-
-#### 작업 중심 키워드
-- "creating [artifact]", "writing [code/docs]", "implementing [feature]"
-- "validating [aspect]", "checking [quality]", "verifying [compliance]"
-- "analyzing [code/data]", "debugging [issue]", "diagnosing [problem]"
-
-#### 조건 중심 키워드
-- "when working with [file type/framework]"
-- "when developing [feature/component]"
-- "when applying [pattern/practice]"
-
-#### 상황 중심 키워드
-- "for [workflow/process]", "during [phase/stage]"
-- "to [achieve goal/outcome]"
-
-### 5. 금지 사항 (Anti-patterns)
-
-❌ **너무 짧음**:
-```
-description: Helps with documents
-```
-
-❌ **트리거 키워드 없음**:
-```
-description: PDF processing tool
-```
-
-❌ **"I can", "You can" 사용** (첫 인칭 회피):
-```
-description: I help you process Excel files
-```
-
-❌ **기술적 세부사항만**:
-```
-description: Uses pdfplumber library
-```
-
----
-
-## 📊 Skills 목록별 개선 체크리스트
-
-### Priority 1: Foundation Skills (7개)
-- [ ] moai-foundation-specs ✅ 완료
-- [ ] moai-foundation-ears ✅ 완료
-- [ ] moai-foundation-tags
-- [ ] moai-foundation-trust
-- [ ] moai-foundation-langs
-- [ ] moai-claude-code
-- [ ] moai-foundation-git
-
-### Priority 2: Alfred Skills (10개)
-- [ ] moai-alfred-tag-scanning
-- [ ] moai-alfred-trust-validation
-- [ ] moai-alfred-spec-metadata-validation
-- [ ] moai-alfred-code-reviewer
-- [ ] moai-alfred-git-workflow
-- [ ] moai-alfred-ears-authoring
-- [ ] moai-alfred-debugger-pro
-- [ ] moai-alfred-language-detection
-- [ ] moai-alfred-performance-optimizer
-- [ ] moai-alfred-refactoring-coach
-
-### Priority 3: Language Skills (20개)
-- moai-lang-typescript
-- moai-lang-python
-- moai-lang-go
-- moai-lang-rust
-- moai-lang-java
-- ... (14개 더)
-
-### Priority 4: Domain Skills (12개)
-- moai-domain-backend
-- moai-domain-frontend
-- moai-domain-web-api
-- moai-domain-database
-- ... (8개 더)
-
-### Priority 5: Essentials Skills (4개)
-- moai-essentials-debug
-- moai-essentials-review
-- moai-essentials-refactor
-- moai-essentials-perf
-
----
-
-## 🔧 개선 방법
-
-### 방법 1: 개별 Edit (고품질)
-각 Skill의 `description` 필드를 수작업 Edit
-- 이점: 각 Skill에 최적화된 description
-- 단점: 시간이 오래 걸림 (60+ Skills)
-
-### 방법 2: 정책 기반 일괄 개선 (효율성)
-템플릿을 기반으로 Pattern matching으로 우선순위별 개선
-1. Priority 1-2: 개별 Edit (가장 중요)
-2. Priority 3-5: 템플릿 기반 일괄 적용
-
-### 현재 진행 상태
-- ✅ moai-foundation-specs (Priority 1)
-- ✅ moai-foundation-ears (Priority 1)
-- ⏳ 나머지 50+ Skills (Priority 2-5)
-
----
-
-## 📝 작성 예시
-
-### 좋은 예시
-
-#### Foundation Skill
-```yaml
-description: Validates SPEC YAML frontmatter (7 required fields id, version, status, created, updated, author, priority) and HISTORY section. Use when creating SPEC documents, validating SPEC metadata, checking SPEC structure, or authoring specifications.
-```
-
-#### Alfred Skill
-```yaml
-description: Generates descriptive commit messages by analyzing git diffs. Use when writing commit messages, reviewing staged changes, or summarizing code modifications. Automatically activates git-workflow skill for advanced patterns.
-```
-
-#### Language Skill
-```yaml
-description: TypeScript best practices with Vitest, Biome, strict typing. Use when implementing TypeScript code, writing tests, checking code quality, or applying type safety patterns.
-```
-
-#### Domain Skill
-```yaml
-description: REST API design patterns with authentication, versioning, error handling. Use when designing REST APIs, implementing authentication, building backend services, or managing API versions.
-```
-
-### 수정 전 vs 수정 후
-
-| Skill | Before | After |
-|-------|--------|-------|
-| moai-foundation-specs | "Validates SPEC YAML frontmatter (7 required fields) and HISTORY section" | "Validates SPEC YAML frontmatter (7 required fields id, version, status, created, updated, author, priority) and HISTORY section. Use when creating SPEC documents, validating SPEC metadata, checking SPEC structure, or authoring specifications." |
-| moai-foundation-ears | "EARS requirement authoring guide (Ubiquitous/Event/State/Optional/Constraints)" | "EARS requirement authoring guide covering Ubiquitous/Event/State/Optional/Constraints syntax patterns. Use when writing requirements, authoring specifications, defining system behavior, or creating functional requirements." |
-
----
-
-## ✅ 최종 검증 체크리스트
-
-각 Skill의 description이 다음을 만족하는지 확인:
-
-- [ ] **"What it does"**: 명확한 기능 설명 (명사 + 동사)
-- [ ] **"Use when"**: 3~5개 구체적 트리거 키워드 포함
-- [ ] **길이**: 한 줄 (150-200 자 권장)
-- [ ] **관계**: 연관된 Skills 명시 (선택)
-- [ ] **발견성**: 검색 키워드 포함 (sub-agent가 발견 가능)
-- [ ] **첫 인칭 회피**: "I", "You", "Our" 사용 안 함
-- [ ] **기술 중심성 회피**: 라이브러리/도구명보다 기능/목적 우선
-
----
-
-**작성일**: 2025-10-20
-**최종 업데이트**: Phase 2 진행 중

moai_adk/templates/.moai/memory/SPEC-METADATA.md

@@ -1,356 +0,0 @@
-# SPEC Metadata Structure Guide
-
-> **MoAI-ADK SPEC Metadata Standard**
->
-> Every SPEC document must follow this structure.
-
----
-
-## 📋 Metadata Overview
-
-SPEC metadata contains **7 required fields** and **9 optional fields**.
-
-### Full Example
-
-```yaml
----
-# Required Fields (7)
-id: AUTH-001                    # Unique SPEC ID
-version: 0.0.1                  # Semantic version (v0.0.1 = INITIAL, draft start)
-status: draft                   # draft|active|completed|deprecated
-created: 2025-09-15             # Creation date (YYYY-MM-DD)
-updated: 2025-09-15             # Last updated (YYYY-MM-DD; initially same as created)
-author: @Goos                   # Author (single GitHub handle)
-priority: high                  # low|medium|high|critical
-
-# Optional Fields – Classification/Meta
-category: security              # feature|bugfix|refactor|security|docs|perf
-labels:                         # Tags for search and grouping
-  - authentication
-  - jwt
-
-# Optional Fields – Relationships (Dependency Graph)
-depends_on:                     # SPECs this one depends on (optional)
-  - USER-001
-blocks:                         # SPECs blocked by this one (optional)
-  - AUTH-002
-related_specs:                  # Related SPECs (optional)
-  - TOKEN-002
-related_issue: "https://github.com/modu-ai/moai-adk/issues/123"
-
-# Optional Fields – Scope/Impact
-scope:
-  packages:                     # Impacted packages
-    - src/core/auth
-  files:                        # Key files (optional)
-    - auth-service.ts
-    - jwt-manager.ts
----
-```
-
----
-
-## Required Fields
-
-### 1. `id` – Unique SPEC Identifier
-- **Type**: string
-- **Format**: `<DOMAIN>-<NUMBER>`
-- **Examples**: `AUTH-001`, `INSTALLER-SEC-001`
-- **Rules**:
-  - Immutable once assigned
-  - Use three digits (001–999)
-  - Domain in uppercase; hyphens allowed
-  - Directory name: `.moai/specs/SPEC-{ID}/` (e.g., `.moai/specs/SPEC-AUTH-001/`)
-
-### 2. `version` – Semantic Version
-- **Type**: string (`MAJOR.MINOR.PATCH`)
-- **Default**: `0.0.1` (all SPECs start here, status: draft)
-- **Version Lifecycle**:
-  - **v0.0.1**: INITIAL – SPEC first draft (status: draft)
-  - **v0.0.x**: Draft refinements (increment PATCH when editing the SPEC)
-  - **v0.1.0**: TDD implementation complete (status: completed, updated via `/alfred:3-sync`)
-  - **v0.1.x**: Bug fixes or doc improvements (PATCH increment)
-  - **v0.x.0**: Feature additions or major enhancements (MINOR increment)
-  - **v1.0.0**: Stable release (production ready, explicit stakeholder approval required)
-
-### 3. `status` – Progress State
-- **Type**: enum
-- **Values**:
-  - `draft`: Authoring in progress
-  - `active`: Implementation underway
-  - `completed`: Implementation finished
-  - `deprecated`: Planned for retirement
-
-### 4. `created` – Creation Date
-- **Type**: date string
-- **Format**: `YYYY-MM-DD`
-- **Example**: `2025-10-06`
-
-### 5. `updated` – Last Modified Date
-- **Type**: date string
-- **Format**: `YYYY-MM-DD`
-- **Rule**: Update whenever the SPEC content changes.
-
-### 6. `author` – Primary Author
-- **Type**: string
-- **Format**: `@{GitHub ID}`
-- **Example**: `@Goos`
-- **Rules**:
-  - Single value only (no `authors` array)
-  - Prefix the GitHub handle with `@`
-  - Additional contributors belong in the HISTORY section
-
-### 7. `priority` – Work Priority
-- **Type**: enum
-- **Values**:
-  - `critical`: Immediate attention (security, severe defects)
-  - `high`: Major feature work
-  - `medium`: Enhancements
-  - `low`: Optimizations or documentation
-
----
-
-## Optional Fields
-
-### Classification / Meta
-
-#### 8. `category` – Change Type
-- **Type**: enum
-- **Values**:
-  - `feature`: New functionality
-  - `bugfix`: Defect resolution
-  - `refactor`: Structural improvements
-  - `security`: Security enhancements
-  - `docs`: Documentation updates
-  - `perf`: Performance optimizations
-
-#### 9. `labels` – Classification Tags
-- **Type**: array of strings
-- **Purpose**: Search, filtering, grouping
-- **Example**:
-  ```yaml
-  labels:
-    - installer
-    - template
-    - security
-  ```
-
-### Relationship Fields (Dependency Graph)
-
-#### 10. `depends_on` – Required SPECs
-- **Type**: array of strings
-- **Meaning**: SPECs that must be completed first
-- **Example**:
-  ```yaml
-  depends_on:
-    - USER-001
-    - AUTH-001
-  ```
-- **Use Case**: Determines execution order and parallelization.
-
-#### 11. `blocks` – Blocked SPECs
-- **Type**: array of strings
-- **Meaning**: SPECs that cannot proceed until this one is resolved
-- **Example**:
-  ```yaml
-  blocks:
-    - PAYMENT-003
-  ```
-
-#### 12. `related_specs` – Associated SPECs
-- **Type**: array of strings
-- **Meaning**: Related items without direct dependencies
-- **Example**:
-  ```yaml
-  related_specs:
-    - TOKEN-002
-    - SESSION-001
-  ```
-
-#### 13. `related_issue` – Linked GitHub Issue
-- **Type**: string (URL)
-- **Format**: Full GitHub issue URL
-- **Example**:
-  ```yaml
-  related_issue: "https://github.com/modu-ai/moai-adk/issues/123"
-  ```
-
-### Scope Fields (Impact Analysis)
-
-#### 14. `scope.packages` – Impacted Packages
-- **Type**: array of strings
-- **Meaning**: Packages or modules touched by the SPEC
-- **Example**:
-  ```yaml
-  scope:
-    packages:
-      - moai-adk-ts/src/core/installer
-      - moai-adk-ts/src/core/git
-  ```
-
-#### 15. `scope.files` – Key Files
-- **Type**: array of strings
-- **Meaning**: Primary files involved (for reference)
-- **Example**:
-  ```yaml
-  scope:
-    files:
-      - template-processor.ts
-      - template-security.ts
-  ```
-
----
-
-## Metadata Validation
-
-### Required Field Checks
-```bash
-# Verify that every SPEC includes the required fields
-rg "^(id|version|status|created|updated|author|priority):" .moai/specs/SPEC-*/spec.md
-
-# Identify SPECs missing the priority field
-rg -L "^priority:" .moai/specs/SPEC-*/spec.md
-```
-
-### Format Checks
-```bash
-# Ensure the author field uses @Handle format
-rg "^author: @[A-Z]" .moai/specs/SPEC-*/spec.md
-
-# Ensure the version field follows 0.x.y
-rg "^version: 0\.\d+\.\d+" .moai/specs/SPEC-*/spec.md
-```
-
----
-
-## Migration Guide
-
-### Updating Existing SPECs
-
-#### 1. Add the `priority` Field
-Add it if missing:
-```yaml
-priority: medium  # or low|high|critical
-```
-
-#### 2. Normalize the `author` Field
-- `authors: ["@goos"]` → `author: @Goos`
-- Convert lowercase handles to the canonical casing.
-
-#### 3. Add Optional Fields (Recommended)
-```yaml
-category: refactor
-labels:
-  - code-quality
-  - maintenance
-```
-
-### Updating config.json for Language Support (v0.4.2+)
-
-**Background**: MoAI-ADK v0.4.2 introduces conversation language selection in `/alfred:0-project`. Existing projects need to add language metadata to `.moai/config.json`.
-
-#### Migration Steps
-
-**For Existing Projects** (before v0.4.2):
-
-Current config.json structure:
-```json
-{
-  "project": {
-    "locale": "en",
-    "mode": "personal",
-    "language": "python"
-  }
-}
-```
-
-**Updated Structure** (v0.4.2+):
-```json
-{
-  "project": {
-    "locale": "en",
-    "mode": "personal",
-    "language": "python",
-    "conversation_language": "en",
-    "conversation_language_name": "English",
-    "codebase_languages": ["python"]
-  }
-}
-```
-
-#### New Fields
-
-| Field | Type | Required | Description | Example |
-|-------|------|----------|-------------|---------|
-| `conversation_language` | string (ISO 639-1 code) | ✅ Yes | Two-letter language code for Alfred dialogs | `"ko"`, `"en"`, `"ja"`, `"zh"` |
-| `conversation_language_name` | string | ✅ Yes | Display name of conversation language | `"Korean"`, `"English"` |
-| `codebase_languages` | array of strings | ✅ Yes | List of programming languages detected | `["python"]`, `["typescript", "python"]` |
-
-#### Manual Update Process
-
-1. Open `.moai/config.json`
-2. Add the three new fields under `project`:
-   ```json
-   "conversation_language": "en",
-   "conversation_language_name": "English",
-   "codebase_languages": ["python"]
-   ```
-3. Save and commit:
-   ```bash
-   git add .moai/config.json
-   git commit -m "chore: add language metadata to config.json for v0.4.2+"
-   ```
-
-#### Automated Update (via `/alfred:0-project`)
-
-Running `/alfred:0-project` on an existing project will:
-1. Detect current language settings
-2. Add new fields automatically
-3. Preserve existing values
-
-**No manual action required if running `/alfred:0-project` after upgrade.**
-
-#### Field Mapping (Legacy → New)
-
-| Old Field | New Field | Migration Rule |
-|-----------|-----------|-----------------|
-| `locale` | `conversation_language` | Keep as-is (or run `/alfred:0-project` to re-select) |
-| (none) | `conversation_language_name` | Auto-populate from locale mapping |
-| `language` | `codebase_languages` | Wrap in array: `"python"` → `["python"]` |
-
-#### Backward Compatibility
-
-- ✅ Projects without new fields will continue working
-- ⚠️ New language features (multilingual documentation) unavailable without migration
-- ✅ `/alfred:0-project` automatically migrates on next run
-- ✅ Auto-detection will prefer new fields if present
-
----
-
-## Design Principles
-
-### 1. DRY (Don't Repeat Yourself)
-- ❌ **Remove**: the `reference` field (every SPEC referenced the same master plan)
-- ✅ **Instead**: document project-level resources in README.md
-
-### 2. Context-Aware
-- Include only the necessary context.
-- Use optional fields only when they add value.
-
-### 3. Traceable
-- Use `depends_on`, `blocks`, and `related_specs` to map dependencies.
-- Automated tooling can detect cyclic references.
-
-### 4. Maintainable
-- Every field must be machine-verifiable.
-- Maintain consistent formatting for easy parsing.
-
-### 5. Simple First
-- Keep complexity low.
-- Limit to 7 required + 9 optional fields.
-- Expand gradually when justified.
-
----
-
-**Last Updated**: 2025-10-06  
-**Author**: @Alfred