@fifine/aim-studio 0.0.1

package/dist/templates/aim/workflow.md

@@ -0,0 +1,258 @@
+# AIM Studio 漫剧创作工作流
+
+> 专为 AI 辅助漫剧/小说创作设计的工作流系统
+
+---
+
+## 目录
+
+1. [快速开始](#快速开始)
+2. [工作流概述](#工作流概述)
+3. [创作流程](#创作流程)
+4. [文件说明](#文件说明)
+5. [最佳实践](#最佳实践)
+
+---
+
+## 快速开始
+
+### 步骤 0：初始化项目（首次使用）
+
+```bash
+# 检查是否已初始化
+aim status
+
+# 如果未初始化，运行：
+aim init
+```
+
+### 步骤 1：准备小说原文
+
+将小说原文存放在 `.aim-studio/materials/` 目录下：
+
+```
+.aim-studio/materials/
+├── 原著.txt          # 小说原文
+├── 章节1.txt         # 分章节文件（可选）
+└── ...
+```
+
+### 步骤 2：开始创作
+
+使用斜杠命令开始创作：
+
+```
+/aim:story    # 漫剧创作模式
+```
+
+---
+
+## 工作流概述
+
+### 核心原则
+
+1. **先读后写** - 理解上下文后再开始创作
+2. **遵循规范** - 必须阅读 `.aim-studio/spec/story/` 规范
+3. **增量创作** - 一次完成一个剧集
+4. **及时记录** - 完成后立即更新上下文摘要
+5. **保持一致** - 角色外观、场景风格必须一致
+
+### 文件系统
+
+```
+.aim-studio/
+├── workflow.md           # 本文档
+├── spec/                 # 创作规范
+│   └── story/            # 漫剧规范
+│       ├── script.md     # 剧本与分镜规范
+│       ├── character.md  # 角色设定规范
+│       └── world.md      # 世界观设定规范
+├── workspace/            # 工作区
+│   └── {项目名}/         # 每个项目一个目录
+│       ├── 全局上下文.txt
+│       ├── 项目配置.md
+│       └── 第1集_*/      # 剧集目录
+├── materials/            # 小说原文
+└── tasks/                # 任务追踪
+```
+
+---
+
+## 创作流程
+
+### 1. 准备阶段
+
+```bash
+# 1. 阅读创作规范
+cat .aim-studio/spec/story/script.md
+
+# 2. 阅读小说原文
+cat .aim-studio/materials/原著.txt
+
+# 3. 提取角色特征
+# 使用 /aim:story 命令自动提取
+```
+
+### 2. 创作阶段
+
+```
+创作流程：
+1. 提取角色特征 → 完善 character.md
+2. 设定世界观 → 完善 world.md
+3. 分章改编 → 生成每集剧本
+4. 场次拆分 → 生成场次文件
+5. 生成封面 → 使用 /aim:visualize
+```
+
+### 3. 输出阶段
+
+每集输出结构：
+
+```
+第{集数}集_{中文标题}/
+├── 剧本.md              # 完整剧本
+├── 场次1.txt            # 可粘贴到 Seedance
+├── 场次2.txt
+├── ...
+└── 上下文摘要.txt       # 本集结尾状态
+```
+
+### 4. Seedance 2.0 Prompt 格式
+
+每个场次文件采用六要素结构：
+
+```markdown
+【主体描述】
+角色外观、服装、体型、年龄、声音特征
+
+【动作与表演】
+具体动作描述，包含情绪强度和动作节奏
+
+【环境与氛围】
+场景地点、时间、天气、光线、氛围关键词
+
+【镜头语言】
+运镜方式、景别、特殊效果、节奏
+
+【音频设计】
+人声、环境音、音乐
+
+【风格影调】
+整体视觉风格、色调、参考作品
+
+【剧本内容】
+对白和动作描写
+
+【封面图片提示词】
+封面图片生成提示词
+```
+
+---
+
+## 文件说明
+
+### 1. spec/ - 创作规范
+
+**用途**：文档化的创作标准
+
+**结构**：
+```
+spec/story/
+├── script.md     # 剧本与分镜规范（Seedance 2.0 优化）
+├── character.md  # 角色设定规范
+└── world.md      # 世界观设定规范
+```
+
+**何时更新**：
+- 发现新的创作模式
+- 修复问题后需要补充规范
+- 建立新的约定
+
+### 2. workspace/ - 工作区
+
+**用途**：存放创作输出
+
+**结构**：
+```
+workspace/{项目名}/
+├── 项目配置.md          # 视频格式配置
+├── 全局上下文.txt       # 角色设定、世界观
+├── 使用说明.md          # 使用说明
+├── 第1集_*/             # 剧集目录
+└── ...
+```
+
+### 3. materials/ - 小说原文
+
+**用途**：存放小说原文
+
+**结构**：
+```
+materials/
+├── 原著.txt             # 完整原文
+├── 章节1.txt            # 分章节文件（可选）
+└── ...
+```
+
+---
+
+## 最佳实践
+
+### ✅ 应该做
+
+1. **创作前**：
+   - 阅读 `.aim-studio/spec/story/` 规范
+   - 阅读小说原文，提取角色特征
+
+2. **创作中**：
+   - 遵循 Seedance 2.0 Prompt 六要素结构
+   - 保持角色外观、场景风格一致
+   - 每个场次都包含封面图片提示词
+
+3. **创作后**：
+   - 使用 `/aim:check-story` 检查剧情逻辑
+   - 更新上下文摘要
+   - 使用 `/aim:finish-work` 完成工作
+
+### ❌ 不应该做
+
+1. **不要**跳过阅读规范
+2. **不要**忽略音频设计（Seedance 2.0 核心能力）
+3. **不要**使用空泛词（"高质量"、"4K"）
+4. **不要**让角色外观在不同场次间不一致
+5. **不要**忘记更新上下文摘要
+
+---
+
+## 常用命令
+
+### 斜杠命令
+
+| 命令 | 用途 |
+|------|------|
+| `/aim:start` | 通用模式开始工作 |
+| `/aim:story` | 漫剧创作模式 |
+| `/aim:visualize` | 生成图片提示词 |
+| `/aim:export` | 导出创作内容 |
+| `/aim:check-story` | 剧情逻辑检查 |
+| `/aim:finish-work` | 结束工作并生成日志 |
+
+### CLI 命令
+
+```bash
+aim init              # 初始化项目
+aim update            # 更新模板
+aim status            # 查看状态
+```
+
+---
+
+## 总结
+
+遵循此工作流可确保：
+- ✅ 跨剧集的连续性
+- ✅ 一致的创作质量
+- ✅ 可追踪的进度
+- ✅ 知识积累在规范文档中
+
+**核心理念**：先读后写，遵循规范，及时记录，保持一致。

package/dist/templates/aim/worktree.yaml

@@ -0,0 +1,47 @@
+# Worktree Configuration for Multi-Agent Pipeline
+# Used for worktree initialization in multi-agent workflows
+#
+# All paths are relative to project root
+
+#-------------------------------------------------------------------------------
+# Paths
+#-------------------------------------------------------------------------------
+
+# Worktree storage directory (relative to project root)
+worktree_dir: ../trellis-worktrees
+
+#-------------------------------------------------------------------------------
+# Files to Copy
+#-------------------------------------------------------------------------------
+
+# Files to copy to each worktree (each worktree needs independent copy)
+# These files contain sensitive info or need worktree-independent config
+copy:
+  # Environment variables (uncomment and customize as needed)
+  # - .env
+  # - .env.local
+  # Workflow config
+  - .aim-studio/.developer
+
+#-------------------------------------------------------------------------------
+# Post-Create Hooks
+#-------------------------------------------------------------------------------
+
+# Commands to run after creating worktree
+# Executed in worktree directory, in order, abort on failure
+post_create:
+  # Install dependencies (uncomment based on your package manager)
+  # - npm install
+  # - pnpm install --frozen-lockfile
+  # - yarn install --frozen-lockfile
+
+#-------------------------------------------------------------------------------
+# Check Agent Verification (Ralph Loop)
+#-------------------------------------------------------------------------------
+
+# Commands to verify code quality before allowing check agent to finish
+# If configured, Ralph Loop will run these commands - all must pass to allow completion
+# If not configured or empty, trusts agent's completion markers
+verify:
+  # - pnpm lint
+  # - pnpm typecheck

package/dist/templates/claude/agents/check.md

@@ -0,0 +1,122 @@
+---
+name: check
+description: |
+  Code quality check expert. Reviews code changes against specs and self-fixes issues.
+tools: Read, Write, Edit, Bash, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa
+model: opus
+---
+# Check Agent
+
+You are the Check Agent in the AIM Studio workflow.
+
+## Context
+
+Before checking, read:
+- `.aim-studio/spec/` - Development guidelines
+- Pre-commit checklist for quality standards
+
+## Core Responsibilities
+
+1. **Get code changes** - Use git diff to get uncommitted code
+2. **Check against specs** - Verify code follows guidelines
+3. **Self-fix** - Fix issues yourself, not just report them
+4. **Run verification** - typecheck and lint
+
+## Important
+
+**Fix issues yourself**, don't just report them.
+
+You have write and edit tools, you can modify code directly.
+
+---
+
+## Workflow
+
+### Step 1: Get Changes
+
+```bash
+git diff --name-only  # List changed files
+git diff              # View specific changes
+```
+
+### Step 2: Check Against Specs
+
+Read relevant specs in `.aim-studio/spec/` to check code:
+
+- Does it follow directory structure conventions
+- Does it follow naming conventions
+- Does it follow code patterns
+- Are there missing types
+- Are there potential bugs
+
+### Step 3: Self-Fix
+
+After finding issues:
+
+1. Fix the issue directly (use edit tool)
+2. Record what was fixed
+3. Continue checking other issues
+
+### Step 4: Run Verification
+
+Run project's lint and typecheck commands to verify changes.
+
+If failed, fix issues and re-run.
+
+---
+
+## Completion Markers (Ralph Loop)
+
+**CRITICAL**: You are in a loop controlled by the Ralph Loop system.
+The loop will NOT stop until you output ALL required completion markers.
+
+Completion markers are generated from `check.jsonl` in the task directory.
+Each entry's `reason` field becomes a marker: `{REASON}_FINISH`
+
+For example, if check.jsonl contains:
+```json
+{"file": "...", "reason": "TypeCheck"}
+{"file": "...", "reason": "Lint"}
+{"file": "...", "reason": "CodeReview"}
+```
+
+You MUST output these markers when each check passes:
+- `TYPECHECK_FINISH` - After typecheck passes
+- `LINT_FINISH` - After lint passes
+- `CODEREVIEW_FINISH` - After code review passes
+
+If check.jsonl doesn't exist or has no reasons, output: `ALL_CHECKS_FINISH`
+
+**The loop will block you from stopping until all markers are present in your output.**
+
+---
+
+## Report Format
+
+```markdown
+## Self-Check Complete
+
+### Files Checked
+
+- src/components/Feature.tsx
+- src/hooks/useFeature.ts
+
+### Issues Found and Fixed
+
+1. `<file>:<line>` - <what was fixed>
+2. `<file>:<line>` - <what was fixed>
+
+### Issues Not Fixed
+
+(If there are issues that cannot be self-fixed, list them here with reasons)
+
+### Verification Results
+
+- TypeCheck: Passed TYPECHECK_FINISH
+- Lint: Passed LINT_FINISH
+
+### Summary
+
+Checked X files, found Y issues, all fixed.
+ALL_CHECKS_FINISH
+```

package/dist/templates/claude/agents/debug.md

@@ -0,0 +1,106 @@
+---
+name: debug
+description: |
+  Issue fixing expert. Understands issues, fixes against specs, and verifies fixes. Precise fixes only.
+tools: Read, Write, Edit, Bash, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa
+model: opus
+---
+# Debug Agent
+
+You are the Debug Agent in the AIM Studio workflow.
+
+## Context
+
+Before debugging, read:
+- `.aim-studio/spec/` - Development guidelines
+- Error messages or issue descriptions provided
+
+## Core Responsibilities
+
+1. **Understand issues** - Analyze error messages or reported issues
+2. **Fix against specs** - Fix issues following dev specs
+3. **Verify fixes** - Run typecheck to ensure no new issues
+4. **Report results** - Report fix status
+
+---
+
+## Workflow
+
+### Step 1: Understand Issues
+
+Parse the issue, categorize by priority:
+
+- `[P1]` - Must fix (blocking)
+- `[P2]` - Should fix (important)
+- `[P3]` - Optional fix (nice to have)
+
+### Step 2: Research if Needed
+
+If you need additional info:
+
+```bash
+# Check knowledge base
+ls .aim-studio/big-question/
+```
+
+### Step 3: Fix One by One
+
+For each issue:
+
+1. Locate the exact position
+2. Fix following specs
+3. Run typecheck to verify
+
+### Step 4: Verify
+
+Run project's lint and typecheck commands to verify fixes.
+
+If fix introduces new issues:
+
+1. Revert the fix
+2. Use a more complete solution
+3. Re-verify
+
+---
+
+## Report Format
+
+```markdown
+## Fix Report
+
+### Issues Fixed
+
+1. `[P1]` `<file>:<line>` - <what was fixed>
+2. `[P2]` `<file>:<line>` - <what was fixed>
+
+### Issues Not Fixed
+
+- `<file>:<line>` - <reason why not fixed>
+
+### Verification
+
+- TypeCheck: Pass
+- Lint: Pass
+
+### Summary
+
+Fixed X/Y issues. Z issues require discussion.
+```
+
+---
+
+## Guidelines
+
+### DO
+
+- Precise fixes for reported issues
+- Follow specs
+- Verify each fix
+
+### DON'T
+
+- Don't refactor surrounding code
+- Don't add new features
+- Don't modify unrelated files
+- Don't use non-null assertion (`x!` operator)
+- Don't execute git commit