create-ai-project 1.14.1 → 1.14.2
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/skills-en/coding-standards/SKILL.md +1 -3
- package/.claude/skills-en/documentation-criteria/SKILL.md +1 -3
- package/.claude/skills-en/frontend/technical-spec/SKILL.md +1 -3
- package/.claude/skills-en/frontend/typescript-rules/SKILL.md +1 -3
- package/.claude/skills-en/frontend/typescript-testing/SKILL.md +1 -3
- package/.claude/skills-en/implementation-approach/SKILL.md +1 -3
- package/.claude/skills-en/integration-e2e-testing/SKILL.md +1 -3
- package/.claude/skills-en/project-context/SKILL.md +1 -3
- package/.claude/skills-en/subagents-orchestration-guide/SKILL.md +1 -3
- package/.claude/skills-en/task-analyzer/SKILL.md +1 -3
- package/.claude/skills-en/technical-spec/SKILL.md +1 -3
- package/.claude/skills-en/typescript-rules/SKILL.md +1 -3
- package/.claude/skills-en/typescript-testing/SKILL.md +1 -3
- package/.claude/skills-ja/coding-standards/SKILL.md +1 -3
- package/.claude/skills-ja/documentation-criteria/SKILL.md +1 -3
- package/.claude/skills-ja/frontend/technical-spec/SKILL.md +1 -3
- package/.claude/skills-ja/frontend/typescript-rules/SKILL.md +1 -3
- package/.claude/skills-ja/frontend/typescript-testing/SKILL.md +1 -3
- package/.claude/skills-ja/implementation-approach/SKILL.md +1 -3
- package/.claude/skills-ja/integration-e2e-testing/SKILL.md +1 -3
- package/.claude/skills-ja/project-context/SKILL.md +1 -3
- package/.claude/skills-ja/subagents-orchestration-guide/SKILL.md +1 -3
- package/.claude/skills-ja/task-analyzer/SKILL.md +1 -3
- package/.claude/skills-ja/technical-spec/SKILL.md +1 -3
- package/.claude/skills-ja/typescript-rules/SKILL.md +1 -3
- package/.claude/skills-ja/typescript-testing/SKILL.md +1 -3
- package/package.json +1 -1
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: coding-standards
|
|
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.
|
|
3
|
+
description: Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Universal Coding Standards
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: documentation-criteria
|
|
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.
|
|
3
|
+
description: Guides PRD, ADR, Design Doc, and Work Plan creation with templates and decision matrix.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Documentation Creation Criteria
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/technical-spec
|
|
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.
|
|
3
|
+
description: Defines frontend environment variables, component design, and data flow patterns. Use when configuring React environment.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Technical Design Rules (Frontend)
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-rules
|
|
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.
|
|
3
|
+
description: Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# TypeScript Development Rules (Frontend)
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-testing
|
|
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.
|
|
3
|
+
description: Designs tests with React Testing Library and MSW. Applies component testing patterns.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# TypeScript Testing Rules (Frontend)
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: implementation-approach
|
|
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.
|
|
3
|
+
description: Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when planning feature implementation.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Implementation Strategy Selection Framework (Meta-cognitive Approach)
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: integration-e2e-testing
|
|
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.
|
|
3
|
+
description: Designs integration and E2E tests with mock boundaries and behavior verification rules. Use when writing E2E or integration tests.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Integration Test & E2E Test Design/Implementation Rules
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: project-context
|
|
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.
|
|
3
|
+
description: Provides project-specific tech stack, architecture, and implementation rules. Use when checking project structure.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Project Context
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: subagents-orchestration-guide
|
|
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.
|
|
3
|
+
description: Coordinates subagent task distribution and collaboration. Controls scale determination and autonomous execution mode.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Sub-agents Practical Guide - Orchestration Guidelines for Claude (Me)
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: task-analyzer
|
|
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.
|
|
3
|
+
description: Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata. Use when starting tasks or selecting skills.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Task Analyzer
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: technical-spec
|
|
3
|
-
description:
|
|
4
|
-
Defines environment variables, architecture design, and build/test commands.
|
|
5
|
-
Use when: configuring environment, designing architecture, or setting up builds.
|
|
3
|
+
description: Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# Technical Design Rules
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: typescript-rules
|
|
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.
|
|
3
|
+
description: Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# TypeScript Development Rules
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: typescript-testing
|
|
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.
|
|
3
|
+
description: Applies Vitest test design and quality standards. Provides coverage requirements and mock usage guides. Use when writing unit tests.
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# TypeScript Testing Rules
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: frontend/typescript-testing
|
|
3
|
-
description:
|
|
4
|
-
React Testing LibraryとMSWでテストを設計。コンポーネントテストパターンを適用。
|
|
5
|
-
Use when: コンポーネントテスト、APIモック作成、フロントエンドテスト品質レビュー時。
|
|
3
|
+
description: React Testing LibraryとMSWでテストを設計。コンポーネントテストパターンを適用。
|
|
6
4
|
---
|
|
7
5
|
|
|
8
6
|
# 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.2",
|
|
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": [
|