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

moai_adk/templates/.claude/skills/moai-alfred-refactoring-coach/SKILL.md

@@ -0,0 +1,97 @@
+---
+
+name: moai-alfred-refactoring-coach
+description: Refactoring guidance with design patterns, code smells detection, and step-by-step improvement plans. Use when outlining refactor steps that preserve functionality.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - TodoWrite
+---
+
+# Alfred Refactoring Coach
+
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | /alfred:2-run refactor lane |
+| Trigger cues | Refactoring retros, duplication cleanup, code health follow-ups inside Alfred. |
+
+## What it does
+
+Refactoring guidance with design pattern recommendations, code smell detection, and step-by-step improvement plans.
+
+## When to use
+
+- Activates when Alfred is asked to plan or stage refactoring work.
+- “Help with refactoring”, “How can I improve this code?”, “Apply design patterns” 
+- “Code organization”, “Remove duplication”, “Separate functions”
+
+## How it works
+
+**Refactoring Techniques**:
+- **Extract Method**: Separate long methods
+- **Replace Conditional with Polymorphism**: Remove conditional statements
+- **Introduce Parameter Object**: Group parameters
+- **Extract Class**: Massive class separation
+
+**Design Pattern Recommendations**:
+- Complex object creation → **Builder Pattern**
+- Type-specific behavior → **Strategy Pattern**
+- Global state → **Singleton Pattern**
+- Incompatible interfaces → **Adapter Pattern**
+- Delayed object creation → **Factory Pattern**
+
+**3-Strike Rule**:
+```
+1st occurrence: Just implement
+2nd occurrence: Notice similarity (leave as-is)
+3rd occurrence: Pattern confirmed → Refactor! 🔧
+```
+
+**Refactoring Checklist**:
+- [ ] All tests passing before refactoring
+- [ ] Code smells identified
+- [ ] Refactoring goal clear
+- [ ] Change one thing at a time
+- [ ] Run tests after each change
+- [ ] Commit frequently
+
+## Best Practices
+- The text shown to the user is written using TUI/report expressions.
+- When running the tool, a summary of commands and results are recorded.
+
+## Examples
+```markdown
+- Call this skill inside the /alfred command to generate a report.
+- Add summary to Completion Report.
+```
+
+## Inputs
+- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
+- Parameters passed from user commands or higher commands.
+
+## Outputs
+- Reports, checklists or recommendations for your Alfred workflow.
+- Structured data for subsequent subagent calls.
+
+## Failure Modes
+- When required input documents are missing or permissions are limited.
+- When disruptive changes are required without user approval.
+
+## Dependencies
+- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+
+## References
+- Fowler, Martin. "Refactoring: Improving the Design of Existing Code." Addison-Wesley, 2018.
+- IEEE Software. "Managing Technical Debt." IEEE Software, 2021.
+
+## Changelog
+- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
+
+## Works well with
+
+- alfred-code-reviewer
+- alfred-trust-validation

moai_adk/templates/.claude/skills/moai-alfred-spec-metadata-validation/SKILL.md

@@ -0,0 +1,97 @@
+---
+
+name: moai-alfred-spec-metadata-validation
+description: Validates SPEC YAML frontmatter (7 required fields) and HISTORY section compliance. Use when validating SPEC metadata for consistency.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - 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 | /alfred:1-plan spec validation |
+| Trigger cues | SPEC frontmatter checks, history table enforcement, metadata guardrails. |
+
+## What it does
+
+Validates SPEC document structure including YAML frontmatter (7 required fields) and HISTORY section compliance.
+
+## When to use
+
+- Activates when Alfred validates SPEC templates or enforces metadata standards.
+- "SPEC verification", "Metadata check", "SPEC structure check"
+- Automatically invoked by `/alfred:1-plan`
+- Before creating SPEC document
+
+## How it works
+
+**YAML Frontmatter Validation (7 required fields)**:
+- `id`: SPEC ID (e.g., AUTH-001)
+- `version`: Semantic Version (e.g., 0.0.1)
+- `status`: draft|active|completed|deprecated
+- `created`: YYYY-MM-DD format
+- `updated`: YYYY-MM-DD format
+- `author`: @{GitHub ID} format
+- `priority`: low|medium|high|critical
+
+**HISTORY Section Validation**:
+- Checks existence of HISTORY section
+- Verifies version history (INITIAL/ADDED/CHANGED/FIXED tags)
+- Validates author and date consistency
+
+**Format Validation**:
+```bash
+# Check required fields
+rg "^(id|version|status|created|updated|author|priority):" .moai/specs/SPEC-*/spec.md
+
+# Verify HISTORY section
+rg "^## HISTORY" .moai/specs/SPEC-*/spec.md
+```
+
+## Best Practices
+- The text shown to the user is written using TUI/report expressions.
+- When running the tool, a summary of commands and results are recorded.
+
+## Examples
+```markdown
+- Call this skill inside the /alfred command to generate a report.
+- Add summary to Completion Report.
+```
+
+## Inputs
+- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
+- Parameters passed from user commands or higher commands.
+
+## Outputs
+- Reports, checklists or recommendations for your Alfred workflow.
+- Structured data for subsequent subagent calls.
+
+## Failure Modes
+- When required input documents are missing or permissions are limited.
+- When disruptive changes are required without user approval.
+
+## Dependencies
+- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+
+## References
+- IEEE. "Software Requirements Specification Standard." IEEE 830-1998.
+- NASA. "Systems Engineering Handbook." https://www.nasa.gov/seh/ (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
+
+## Works well with
+
+- alfred-ears-authoring (SPEC writing guide)
+- alfred-tag-scanning (SPEC ID duplication check)
+
+## Reference
+
+SSOT (Single Source of Truth): `.moai/memory/spec-metadata.md`

moai_adk/templates/.claude/skills/moai-alfred-tag-scanning/SKILL.md

@@ -0,0 +1,90 @@
+---
+
+name: moai-alfred-tag-scanning
+description: Scans all @TAG markers directly from code and generates TAG inventory (CODE-FIRST principle - no intermediate cache). Use when rebuilding the TAG inventory from live code.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - 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 | /alfred:3-sync traceability gate |
+| Trigger cues | Traceability scans, orphan TAG cleanup, TAG chain verification in Alfred. |
+
+## 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
+
+- Activates when Alfred needs TAG inventories or chain verification.
+- "TAG Scan", "TAG List", "TAG Inventory"
+- Automatically invoked by `/alfred:3-sync`
+- “Find orphan TAG”, “Check TAG chain”
+
+## How it works
+
+**CODE-FIRST Scanning**:
+```bash
+# Direct code scan without intermediate cache
+rg '@(SPEC|TEST|CODE|DOC):' -n .moai/specs/ tests/ src/ docs/
+```
+
+**TAG Inventory Generation**:
+- Lists all TAGs with file locations
+- Detects orphaned TAGs (no corresponding SPEC/TEST/CODE)
+- Identifies broken links in TAG chain
+- Reports duplicate IDs
+
+**TAG Chain Verification**:
+- @SPEC → @TEST → @CODE → @DOC connection check
+- Ensures traceability across all artifacts
+
+## Best Practices
+- The text shown to the user is written using TUI/report expressions.
+- When running the tool, a summary of commands and results are recorded.
+
+## Examples
+```markdown
+- Call this skill inside the /alfred command to generate a report.
+- Add summary to Completion Report.
+```
+
+## Inputs
+- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
+- Parameters passed from user commands or higher commands.
+
+## Outputs
+- Reports, checklists or recommendations for your Alfred workflow.
+- Structured data for subsequent subagent calls.
+
+## Failure Modes
+- When required input documents are missing or permissions are limited.
+- When disruptive changes are required without user approval.
+
+## Dependencies
+- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+
+## 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: Added input/output/failure response to Alfred-specific skills.
+
+## Works well with
+
+- alfred-trust-validation (TAG traceability verification)
+- alfred-spec-metadata-validation (SPEC ID validation)
+
+## Files included
+
+- templates/tag-inventory-template.md

moai_adk/templates/.claude/skills/moai-alfred-trust-validation/SKILL.md

@@ -0,0 +1,99 @@
+---
+
+name: moai-alfred-trust-validation
+description: Validates TRUST 5-principles compliance (Test coverage 85%+, Code constraints, Architecture unity, Security, TAG trackability). Use when enforcing TRUST checkpoints before progression.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - TodoWrite
+---
+
+# Alfred TRUST Validation
+
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
+| Auto-load | /alfred:3-sync quality gate |
+| Trigger cues | TRUST checklist enforcement, release readiness scoring, risk gating. |
+
+## What it does
+
+Validates MoAI-ADK's TRUST 5-principles compliance to ensure code quality, testability, security, and traceability.
+
+## When to use
+
+- Activates when Alfred evaluates TRUST compliance before handoff.
+- "Check the TRUST principle", "Quality verification", "Check code quality"
+- Automatically invoked by `/alfred:3-sync`
+- Before merging PR or releasing
+
+## How it works
+
+**T - Test First**:
+- Checks test coverage ≥85% (pytest, vitest, go test, cargo test, etc.)
+- Verifies TDD cycle compliance (RED → GREEN → REFACTOR)
+
+**R - Readable**:
+- File ≤300 LOC
+- Function ≤50 LOC
+- Parameters ≤5
+- Cyclomatic complexity ≤10
+
+**U - Unified**:
+- SPEC-driven architecture consistency
+- Clear module boundaries
+- Language-specific standard structures
+
+**S - Secured**:
+- Input validation implementation
+- No hardcoded secrets
+- Access control applied
+
+**T - Trackable**:
+- TAG chain integrity (@SPEC → @TEST → @CODE → @DOC)
+- No orphaned TAGs
+- No duplicate SPEC IDs
+
+## Best Practices
+- The text shown to the user is written using TUI/report expressions.
+- When running the tool, a summary of commands and results are recorded.
+
+## Examples
+```markdown
+- Call this skill inside the /alfred command to generate a report.
+- Add summary to Completion Report.
+```
+
+## Inputs
+- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
+- Parameters passed from user commands or higher commands.
+
+## Outputs
+- Reports, checklists or recommendations for your Alfred workflow.
+- Structured data for subsequent subagent calls.
+
+## Failure Modes
+- When required input documents are missing or permissions are limited.
+- When disruptive changes are required without user approval.
+
+## Dependencies
+- Cooperation with higher-level agents such as cc-manager and project-manager is required.
+
+## 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: Added input/output/failure response to Alfred-specific skills.
+
+## Works well with
+
+- alfred-tag-scanning (TAG traceability)
+- alfred-code-reviewer (code quality analysis)
+
+## Files included
+
+- templates/trust-report-template.md

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

@@ -0,0 +1,87 @@
+---
+
+name: moai-alfred-tui-survey
+description: Standardizes Claude Code Tools AskUserQuestion TUI menus for surveys, branching approvals, and option picking across Alfred workflows. Use when gathering approvals or decisions via Alfred’s TUI menus.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - TodoWrite
+---
+
+# Alfred TUI Survey Skill
+
+## Skill Metadata
+| Field | Value |
+| ----- | ----- |
+| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), TodoWrite (todo_write) |
+| Auto-load | On demand when AskUserQuestion menus are built |
+| Trigger cues | Branch approvals, survey menus, decision gating via AskUserQuestion. |
+
+## What it does
+
+Provides ready-to-use patterns for Claude Code's AskUserQuestion TUI selector so Alfred agents can gather user choices, approvals, or survey answers with structured menus instead of ad-hoc text prompts.
+
+## When to use
+
+- Activates when Alfred needs to gather structured choices through the TUI selector.
+- Need confirmation before advancing to a risky/destructive step.
+- Choosing between alternative implementation paths or automation levels.
+- Collecting survey-like answers (persona, tech stack, priority, risk level).
+- Any time a branched workflow depends on user-selected options rather than free-form text.
+
+## How it works
+
+1. **Detect gate** – Pause at steps that require explicit user choice.
+2. **Shape options** – Offer 2–5 focused choices with concise labels.
+3. **Render menu** – Emit the `AskUserQuestion({...})` block for the selector.
+4. **Map follow-ups** – Note how each option alters the next action/agent.
+5. **Fallback** – Provide plain-text instructions when the UI cannot render.
+
+### Templates & examples
+
+- [Single-select deployment decision](examples.md#single-select-template)
+- [Multi-select diagnostics checklist](examples.md#multi-select-variation)
+- [Follow-up drill-down prompt](examples.md#follow-up-prompt-for-deeper-detail)
+
+## Best Practices
+- Reduce context switching by putting questions, options, and follow-up actions on one screen.
+- Options are sorted according to comparison criteria such as risk and priority.
+- If safety measures are required, such as approval/suspension/cancellation, attach a warning message.
+- Submission results are recorded for reuse in the Sync step or reports.
+
+## Inputs
+- Decision scenarios and candidate options collected by Alfred workflows.
+- Definition of follow-up actions for each option (next command, subagent, TODO, etc.).
+
+## Outputs
+- AskUserQuestion block and choice → follow-up action mapping.
+- Summary of selection results and TODO items that require further confirmation.
+
+## Failure Modes
+- Ambiguous or duplicate options cause selection delays.
+- It is difficult to judge priorities when all options look the same.
+- AskUserQuestion does not work in a TUI-inactive environment, so plan B is needed.
+
+## Dependencies
+- Works with the main `/alfred:*` command and schedules follow-up actions with TodoWrite when necessary.
+- When combined with moai-foundation-ears · moai-foundation-tags, requirements → options → TAG records are connected.
+
+## References
+- Jakubovic, J. "Designing Effective CLI Dialogs." ACM Queue, 2021.
+- NCurses. "Programming Guide." https://invisible-island.net/ncurses/man/ncurses.3x.html (accessed 2025-03-29).
+
+## Changelog
+- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
+
+## Works well with
+
+- `moai-foundation-ears` – Combine structured requirement patterns with menu-driven confirmations.
+- `moai-alfred-git-workflow` – Use menus to choose branch/worktree strategies.
+- `moai-alfred-code-reviewer` – Capture reviewer focus areas through guided selection.
+
+## Examples
+```markdown
+- In the `/alfred:1-plan` step, user priorities are collected and the results are written to the PLAN board.
+- Check user approval before high-risk operations while running `/alfred:2-run`.
+```

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

@@ -0,0 +1,62 @@
+# 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,67 +1,94 @@
 ---
+
 name: moai-claude-code
-description: Claude Code 5가지 컴포넌트 생성 및 관리 - Agent, Command, Skill, Plugin, Settings
-  템플릿 기반 정확한 파일 생성
+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
+  - Read
+  - Write
+  - Edit
 ---
 
 # MoAI Claude Code Manager
 
-Claude Code의 5가지 핵심 컴포넌트를 공식 표준에 맞게 생성하고 관리합니다.
+## 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.
 
-1. **Agent** (.claude/agents/) - 전문 에이전트
-2. **Command** (.claude/commands/) - 슬래시 커맨드
-3. **Skill** (.claude/skills/) - 재사용 기능 모듈
-4. **Plugin** (settings.json의 mcpServers) - MCP 서버 통합
-5. **Settings** (.claude/settings.json) - 권한 및 훅 설정
+## 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
 
-MoAI-ADK 통합 프로덕션급 템플릿 (5개)
+## Reference files
 
-- 완전 상세 (완전하고 실무 사용 가능)
-- MoAI-ADK 워크플로우 통합
-- 복사-붙여넣기 즉시 사용
-- 검증 및 트러블슈팅 가이드 포함
+- `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
 
-### Agent 생성
-"spec-builder Agent를 생성해주세요"
+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.
 
-### Settings 최적화
-"Python 프로젝트용 settings.json을 생성해주세요"
+## Guardrails
 
-### 전체 검증
-"모든 Claude Code 설정을 검증해주세요"
+- 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
 
-- **reference.md**: 컴포넌트별 작성 가이드
-- **examples.md**: 실전 예제 모음
-- **templates/**: 5개 프로덕션급 템플릿
-- **scripts/**: Python 검증 스크립트 (선택적)
+## 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.
 
-1. 사용자 요청 분석 → 컴포넌트 유형 파악
-2. 적절한 템플릿 선택 (templates/ 디렉토리)
-3. 플레이스홀더 치환 및 파일 생성
-4. 자동 검증 (선택적, scripts/ 실행)
+## 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.
 
-- **공식 표준 준수**: Anthropic 가이드라인 완벽 준수
-- **할루시네이션 방지**: 검증된 템플릿만 사용
-- **최소 권한**: 필요한 도구만 명시
-- **보안 우선**: 민감 정보 환경변수 관리
+## 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).
 
-**공식 문서**: https://docs.claude.com/en/docs/claude-code/skills
-**버전**: 1.0.0
+## Changelog
+- 2025-03-29: Added best practice structure to Claude code formatting skill.