create-ai-project 1.14.0 → 1.14.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/agents-en/acceptance-test-generator.md +1 -1
- package/.claude/agents-en/code-reviewer.md +1 -1
- package/.claude/agents-en/code-verifier.md +1 -1
- package/.claude/agents-en/design-sync.md +1 -1
- package/.claude/agents-en/document-reviewer.md +1 -1
- package/.claude/agents-en/integration-test-reviewer.md +1 -1
- package/.claude/agents-en/investigator.md +1 -1
- package/.claude/agents-en/prd-creator.md +1 -1
- package/.claude/agents-en/requirement-analyzer.md +1 -1
- package/.claude/agents-en/rule-advisor.md +1 -1
- package/.claude/agents-en/scope-discoverer.md +1 -1
- package/.claude/agents-en/solver.md +1 -1
- package/.claude/agents-en/task-decomposer.md +1 -1
- package/.claude/agents-en/task-executor-frontend.md +1 -1
- package/.claude/agents-en/task-executor.md +1 -1
- package/.claude/agents-en/technical-designer-frontend.md +1 -1
- package/.claude/agents-en/technical-designer.md +1 -1
- package/.claude/agents-en/verifier.md +1 -1
- package/.claude/agents-en/work-planner.md +1 -1
- package/.claude/agents-ja/acceptance-test-generator.md +1 -1
- package/.claude/agents-ja/code-reviewer.md +1 -1
- package/.claude/agents-ja/code-verifier.md +1 -1
- package/.claude/agents-ja/design-sync.md +1 -1
- package/.claude/agents-ja/document-reviewer.md +1 -1
- package/.claude/agents-ja/integration-test-reviewer.md +1 -1
- package/.claude/agents-ja/investigator.md +1 -1
- package/.claude/agents-ja/prd-creator.md +1 -1
- package/.claude/agents-ja/requirement-analyzer.md +1 -1
- package/.claude/agents-ja/rule-advisor.md +1 -1
- package/.claude/agents-ja/scope-discoverer.md +1 -1
- package/.claude/agents-ja/solver.md +1 -1
- package/.claude/agents-ja/task-decomposer.md +1 -1
- package/.claude/agents-ja/task-executor-frontend.md +1 -1
- package/.claude/agents-ja/task-executor.md +1 -1
- package/.claude/agents-ja/technical-designer-frontend.md +1 -1
- package/.claude/agents-ja/technical-designer.md +1 -1
- package/.claude/agents-ja/verifier.md +1 -1
- package/.claude/agents-ja/work-planner.md +1 -1
- package/.claude/skills-en/coding-standards/SKILL.md +3 -1
- package/.claude/skills-en/documentation-criteria/SKILL.md +3 -1
- package/.claude/skills-en/frontend/technical-spec/SKILL.md +3 -1
- package/.claude/skills-en/frontend/typescript-rules/SKILL.md +3 -1
- package/.claude/skills-en/frontend/typescript-testing/SKILL.md +3 -1
- package/.claude/skills-en/implementation-approach/SKILL.md +3 -1
- package/.claude/skills-en/integration-e2e-testing/SKILL.md +3 -1
- package/.claude/skills-en/project-context/SKILL.md +3 -1
- package/.claude/skills-en/subagents-orchestration-guide/SKILL.md +3 -1
- package/.claude/skills-en/task-analyzer/SKILL.md +3 -1
- package/.claude/skills-en/technical-spec/SKILL.md +3 -1
- package/.claude/skills-en/typescript-rules/SKILL.md +3 -1
- package/.claude/skills-en/typescript-testing/SKILL.md +3 -1
- package/.claude/skills-ja/coding-standards/SKILL.md +3 -1
- package/.claude/skills-ja/documentation-criteria/SKILL.md +3 -1
- package/.claude/skills-ja/frontend/technical-spec/SKILL.md +3 -1
- package/.claude/skills-ja/frontend/typescript-rules/SKILL.md +3 -1
- package/.claude/skills-ja/frontend/typescript-testing/SKILL.md +3 -1
- package/.claude/skills-ja/implementation-approach/SKILL.md +3 -1
- package/.claude/skills-ja/integration-e2e-testing/SKILL.md +3 -1
- package/.claude/skills-ja/project-context/SKILL.md +3 -1
- package/.claude/skills-ja/subagents-orchestration-guide/SKILL.md +3 -1
- package/.claude/skills-ja/task-analyzer/SKILL.md +3 -1
- package/.claude/skills-ja/technical-spec/SKILL.md +3 -1
- package/.claude/skills-ja/typescript-rules/SKILL.md +3 -1
- package/.claude/skills-ja/typescript-testing/SKILL.md +3 -1
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: acceptance-test-generator
|
|
3
|
-
description:
|
|
3
|
+
description: Generates high-ROI integration/E2E test skeletons from Design Doc ACs. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
|
|
4
4
|
tools: Read, Write, Glob, LS, TodoWrite, Grep
|
|
5
5
|
skills: integration-e2e-testing, typescript-testing, documentation-criteria, project-context
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: code-reviewer
|
|
3
|
-
description: Validates Design Doc compliance and
|
|
3
|
+
description: Validates Design Doc compliance and implementation completeness from third-party perspective. Use PROACTIVELY after implementation completes or when "review/implementation check/compliance" is mentioned. Provides acceptance criteria validation and quality reports.
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: coding-standards, typescript-rules, typescript-testing, project-context, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: code-verifier
|
|
3
|
-
description:
|
|
3
|
+
description: Validates consistency between PRD/Design Doc and code implementation. Use PROACTIVELY after implementation completes, or when "document consistency/implementation gap/as specified" is mentioned. Uses multi-source evidence matching to identify discrepancies.
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, coding-standards, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: design-sync
|
|
3
|
-
description:
|
|
3
|
+
description: Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: documentation-criteria, project-context, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: document-reviewer
|
|
3
|
-
description:
|
|
3
|
+
description: Reviews document consistency and completeness, providing approval decisions. Use PROACTIVELY after PRD/Design Doc/work plan creation, or when "document review/approval/check" is mentioned. Detects contradictions and rule violations with improvement suggestions.
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, technical-spec, project-context, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: integration-test-reviewer
|
|
3
|
-
description:
|
|
3
|
+
description: Verifies consistency between test skeleton comments and implementation code. Use PROACTIVELY after test implementation completes, or when "test review/skeleton verification" is mentioned. Returns quality reports with failing items and fix instructions.
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: integration-e2e-testing, typescript-testing, project-context
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: investigator
|
|
3
|
-
description:
|
|
3
|
+
description: Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports only observations without proposing solutions.
|
|
4
4
|
tools: Read, Grep, Glob, LS, WebSearch, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: prd-creator
|
|
3
|
-
description:
|
|
3
|
+
description: Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, project-context, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: requirement-analyzer
|
|
3
|
-
description:
|
|
3
|
+
description: Performs requirements analysis and work scale determination. Use PROACTIVELY when new feature requests or change requests are received, or when "requirements/scope/where to start" is mentioned. Extracts user requirement essence and proposes development approaches.
|
|
4
4
|
tools: Read, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: project-context, documentation-criteria, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: rule-advisor
|
|
3
|
-
description:
|
|
3
|
+
description: Selects optimal rulesets for tasks and performs metacognitive analysis. MUST BE USED before any implementation task starts (CLAUDE.md required process). Analyzes task essence with task-analyzer skill and returns structured JSON.
|
|
4
4
|
tools: Read, Grep, LS
|
|
5
5
|
skills: task-analyzer
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: scope-discoverer
|
|
3
|
-
description:
|
|
3
|
+
description: Discovers PRD/Design Doc scope from existing codebase. Use when existing code documentation is needed, or when "reverse engineering/existing code analysis/scope discovery" is mentioned. Identifies targets through multi-source discovery.
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, coding-standards, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: solver
|
|
3
|
-
description:
|
|
3
|
+
description: Derives multiple solutions for verified causes and analyzes tradeoffs. Use when verifier has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-decomposer
|
|
3
|
-
description:
|
|
3
|
+
description: Decomposes work plans into independent single-commit granularity tasks in docs/plans/tasks. Use PROACTIVELY when work plan (docs/plans/) is created, or when "task decomposition/split/decompose" is mentioned.
|
|
4
4
|
tools: Read, Write, LS, Bash, TodoWrite
|
|
5
5
|
skills: documentation-criteria, project-context, coding-standards, typescript-testing, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-executor-frontend
|
|
3
|
-
description:
|
|
3
|
+
description: Executes React implementation completely self-contained following frontend task files. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
|
|
4
4
|
tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: frontend/typescript-rules, frontend/typescript-testing, coding-standards, project-context, frontend/technical-spec, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-executor
|
|
3
|
-
description:
|
|
3
|
+
description: Executes implementation completely self-contained following task files. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
|
|
4
4
|
tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: typescript-rules, typescript-testing, coding-standards, project-context, technical-spec, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-designer-frontend
|
|
3
|
-
description:
|
|
3
|
+
description: Creates frontend ADR and Design Docs to evaluate React technical choices. Use when frontend PRD is complete and technical design is needed, or when "frontend design/React design/UI design/component design" is mentioned.
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, frontend/technical-spec, frontend/typescript-rules, coding-standards, project-context, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-designer
|
|
3
|
-
description:
|
|
3
|
+
description: Creates ADR and Design Docs to evaluate technical choices. Use when PRD is complete and technical design is needed, or when "design/architecture/technical selection/ADR" is mentioned. Defines implementation approach.
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, technical-spec, typescript-rules, coding-standards, project-context, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: verifier
|
|
3
|
-
description:
|
|
3
|
+
description: Critically evaluates investigation results and identifies oversights. Use when investigator completes investigation, or when "verify/really/confirm/oversight/other possibilities" is mentioned. Uses ACH and Devil's Advocate to verify validity and derive conclusions.
|
|
4
4
|
tools: Read, Grep, Glob, LS, WebSearch, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: work-planner
|
|
3
|
-
description:
|
|
3
|
+
description: Creates work plans from Design Docs and structures implementation tasks. Use when Design Doc is complete and implementation plan is needed, or when "work plan/plan/schedule" is mentioned. Creates trackable execution plans.
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, project-context, technical-spec, implementation-approach, typescript-testing, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: acceptance-test-generator
|
|
3
|
-
description:
|
|
3
|
+
description: Design DocのACから高ROIの統合/E2Eテストスケルトンを生成。Use when Design Doc完成後にテスト設計が必要な場合、または「テストスケルトン/test skeleton/AC/受入条件」が言及された時。振る舞い優先・最小限で最大カバレッジを実現。
|
|
4
4
|
tools: Read, Write, Glob, LS, TodoWrite, Grep
|
|
5
5
|
skills: integration-e2e-testing, typescript-testing, documentation-criteria, project-context
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: code-reviewer
|
|
3
|
-
description: Design Doc
|
|
3
|
+
description: Design Doc準拠と実装完全性を第三者視点で検証。Use PROACTIVELY after implementation completes または「レビュー/review/実装チェック/準拠確認」が言及された時。受入条件照合、実装漏れ検出、品質レポートを提供。
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: coding-standards, typescript-rules, typescript-testing, project-context, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: code-verifier
|
|
3
|
-
description:
|
|
3
|
+
description: PRD/Design Docとコード実装間の整合性を検証。Use PROACTIVELY after 実装完了時、または「ドキュメント整合性/実装漏れ/仕様通り」が言及された時。multi-source evidence matchingで不整合を特定。
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, coding-standards, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: design-sync
|
|
3
|
-
description: Design Doc
|
|
3
|
+
description: 複数Design Doc間の矛盾を検出し構造化レポートを提供。Use when 複数のDesign Docが存在する時、または「整合性/矛盾/sync/ドキュメント間」が言及された時。修正は行わず検出と報告に特化。
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: documentation-criteria, project-context, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: document-reviewer
|
|
3
|
-
description:
|
|
3
|
+
description: ドキュメントの整合性と完成度をレビューし承認判定を提供。Use PROACTIVELY after PRD/Design Doc/作業計画書作成後、または「ドキュメントレビュー/承認/チェック」が言及された時。矛盾・ルール違反を検出し改善提案。
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, technical-spec, project-context, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: integration-test-reviewer
|
|
3
|
-
description:
|
|
3
|
+
description: テストファイルのスケルトンコメントと実装コードの整合性を検証。Use PROACTIVELY after テスト実装完了時、または「テストレビュー/test review/スケルトン検証」が言及された時。不合格項目と修正指示を含む品質レポートを返却。
|
|
4
4
|
tools: Read, Grep, Glob, LS
|
|
5
5
|
skills: integration-e2e-testing, typescript-testing, project-context
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: investigator
|
|
3
|
-
description:
|
|
3
|
+
description: 問題に関連する情報を網羅的に収集し証拠マトリクスを作成。Use PROACTIVELY when バグ/エラー/問題/不具合/動かない/おかしい が報告された時。解決策は考えず観察結果のみを報告。
|
|
4
4
|
tools: Read, Grep, Glob, LS, WebSearch, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: prd-creator
|
|
3
|
-
description:
|
|
3
|
+
description: PRDを作成しビジネス要件を構造化。Use when 新機能/プロジェクト開始時、または「PRD/要件定義/ユーザーストーリー/何を作る」が言及された時。ユーザー価値と成功指標を定義。
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, project-context, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: requirement-analyzer
|
|
3
|
-
description:
|
|
3
|
+
description: 要件分析と作業規模判定を実行。Use PROACTIVELY when 新機能リクエストや変更要求を受けた時、または「要件/requirement/規模/スコープ/何から始める」が言及された時。ユーザー要求の本質を抽出し、適切な開発アプローチを提案。
|
|
4
4
|
tools: Read, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: project-context, documentation-criteria, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: rule-advisor
|
|
3
|
-
description:
|
|
3
|
+
description: タスクに最適なルールセットを選択しメタ認知的分析を実行。MUST BE USED before any implementation task starts(CLAUDE.md必須プロセス)。task-analyzerスキルでタスク本質を分析し、構造化JSONを返却。
|
|
4
4
|
tools: Read, Grep, LS
|
|
5
5
|
skills: task-analyzer
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: scope-discoverer
|
|
3
|
-
description:
|
|
3
|
+
description: 既存コードベースからPRD/Design Docのスコープを導出。Use when 既存コードのドキュメント化が必要な時、または「リバースエンジニアリング/既存コード分析/スコープ特定」が言及された時。マルチソース探索で対象を特定。
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, coding-standards, technical-spec
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: solver
|
|
3
|
-
description:
|
|
3
|
+
description: 検証済み原因に対して複数の解決策を導出しトレードオフを分析。Use when verifierが結論を出した後、または「解決策/どうすれば/修正方法/対処法」が言及された時。調査は行わず与えられた結論から解決に集中。
|
|
4
4
|
tools: Read, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-decomposer
|
|
3
|
-
description:
|
|
3
|
+
description: 作業計画書を1コミット粒度の独立タスクに分解しdocs/plans/tasksに配置。Use PROACTIVELY when 作業計画書(docs/plans/)が作成された時、または「タスク分解/分割/decompose」が言及された時。
|
|
4
4
|
tools: Read, Write, LS, Bash, TodoWrite
|
|
5
5
|
skills: documentation-criteria, project-context, coding-standards, typescript-testing, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-executor-frontend
|
|
3
|
-
description:
|
|
3
|
+
description: フロントエンドタスクファイルに従ってReact実装を完全自己完結で実行。Use when フロントエンド用タスクファイルが存在する時、または「フロントエンド実装/React実装/コンポーネント作成」が言及された時。質問せず調査から実装まで一貫実行。
|
|
4
4
|
tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: frontend/typescript-rules, frontend/typescript-testing, coding-standards, project-context, frontend/technical-spec, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-executor
|
|
3
|
-
description:
|
|
3
|
+
description: タスクファイルに従って実装を完全自己完結で実行。Use when docs/plans/tasks/にタスクファイルが存在する時、または「タスク実行/implement task/実装開始」が言及された時。質問せず調査から実装まで一貫実行。
|
|
4
4
|
tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TodoWrite
|
|
5
5
|
skills: typescript-rules, typescript-testing, coding-standards, project-context, technical-spec, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-designer-frontend
|
|
3
|
-
description:
|
|
3
|
+
description: フロントエンドADRとDesign Docを作成しReact技術選択肢を評価。Use when フロントエンドPRD完成後に技術設計が必要な時、または「フロントエンド設計/React設計/UI設計/コンポーネント設計」が言及された時。
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, frontend/technical-spec, frontend/typescript-rules, coding-standards, project-context, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-designer
|
|
3
|
-
description:
|
|
3
|
+
description: ADRとDesign Docを作成し技術的選択肢を評価。Use when PRD完成後に技術設計が必要な時、または「設計/design/アーキテクチャ/技術選定/ADR」が言及された時。実装アプローチを定義。
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite, WebSearch
|
|
5
5
|
skills: documentation-criteria, technical-spec, typescript-rules, coding-standards, project-context, implementation-approach
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: verifier
|
|
3
|
-
description:
|
|
3
|
+
description: 調査結果を批判的に評価し見落としを探す。Use when investigatorの調査完了後、または「検証/本当に/確認/見落とし/他の可能性」が言及された時。ACH・Devil's Advocate手法で妥当性を検証し結論を導出。
|
|
4
4
|
tools: Read, Grep, Glob, LS, WebSearch, TodoWrite
|
|
5
5
|
skills: project-context, technical-spec, coding-standards
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: work-planner
|
|
3
|
-
description:
|
|
3
|
+
description: Design Docから作業計画書を作成し実装タスクを構造化。Use when Design Doc完成後に実装計画が必要な時、または「作業計画/計画書/plan/スケジュール」が言及された時。進捗追跡可能な実行計画を立案。
|
|
4
4
|
tools: Read, Write, Edit, MultiEdit, Glob, LS, TodoWrite
|
|
5
5
|
skills: documentation-criteria, project-context, technical-spec, implementation-approach, typescript-testing, typescript-rules
|
|
6
6
|
---
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: coding-standards
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Detects code smells, anti-patterns, and readability issues. Applies clean code and refactoring principles.
|
|
5
|
+
Use when: implementing features, reviewing code, refactoring, or improving quality.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Universal Coding Standards
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: documentation-criteria
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Guides PRD, ADR, Design Doc, and Work Plan creation with templates and decision matrix.
|
|
5
|
+
Use when: planning features, writing specs, creating docs, or deciding which documents are needed.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Documentation Creation Criteria
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/technical-spec
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Defines frontend environment variables, component design, and data flow patterns.
|
|
5
|
+
Use when: configuring React environment, designing components, or setting up state management.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Technical Design Rules (Frontend)
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-rules
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Applies React/TypeScript type safety, component design, and state management rules.
|
|
5
|
+
Use when: implementing React components, defining types, designing state, or handling errors.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# TypeScript Development Rules (Frontend)
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-testing
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Designs tests with React Testing Library and MSW. Applies component testing patterns.
|
|
5
|
+
Use when: writing component tests, mocking APIs, or reviewing frontend test quality.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# TypeScript Testing Rules (Frontend)
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: implementation-approach
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment.
|
|
5
|
+
Use when: planning how to build a feature, deciding development approach, or defining verification levels.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Implementation Strategy Selection Framework (Meta-cognitive Approach)
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: integration-e2e-testing
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Designs integration and E2E tests with mock boundaries and behavior verification rules.
|
|
5
|
+
Use when: writing E2E tests, integration tests, test skeletons, or reviewing test quality.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Integration Test & E2E Test Design/Implementation Rules
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: project-context
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Provides project-specific tech stack, architecture, and implementation rules.
|
|
5
|
+
Use when: checking project structure, understanding tech stack, or referencing implementation guidelines.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Project Context
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: subagents-orchestration-guide
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Coordinates subagent task distribution and collaboration. Controls scale determination and autonomous execution mode.
|
|
5
|
+
Use when: splitting large tasks, coordinating multiple agents, or designing workflows.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Sub-agents Practical Guide - Orchestration Guidelines for Claude (Me)
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-analyzer
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata.
|
|
5
|
+
Use when: starting tasks, selecting skills, or judging work scope.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Task Analyzer
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-spec
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Defines environment variables, architecture design, and build/test commands.
|
|
5
|
+
Use when: configuring environment, designing architecture, or setting up builds.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# Technical Design Rules
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: typescript-rules
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Applies type safety and error handling rules. Enforces no-any policy and type guards.
|
|
5
|
+
Use when: implementing TypeScript, reviewing types, or designing error handling.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# TypeScript Development Rules
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: typescript-testing
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
Applies Vitest test design and quality standards. Provides coverage requirements and mock usage guides.
|
|
5
|
+
Use when: writing unit tests, using mocks, or reviewing test quality.
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# TypeScript Testing Rules
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-testing
|
|
3
|
-
description:
|
|
3
|
+
description: >
|
|
4
|
+
React Testing LibraryとMSWでテストを設計。コンポーネントテストパターンを適用。
|
|
5
|
+
Use when: コンポーネントテスト、APIモック作成、フロントエンドテスト品質レビュー時。
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
# TypeScript テストルール(フロントエンド)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "create-ai-project",
|
|
3
|
-
"version": "1.14.
|
|
3
|
+
"version": "1.14.1",
|
|
4
4
|
"packageManager": "npm@10.8.2",
|
|
5
5
|
"description": "TypeScript boilerplate with skills and sub-agents for Claude Code. Prevents context exhaustion through role-based task splitting.",
|
|
6
6
|
"keywords": [
|