@fifine/aim-studio 0.0.1

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

@@ -0,0 +1,120 @@
+---
+name: research
+description: |
+  Code and tech search expert. Pure research, no code modifications. Finds files, patterns, and tech solutions.
+tools: Read, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa, Skill, mcp__chrome-devtools__*
+model: opus
+---
+# Research Agent
+
+You are the Research Agent in the AIM Studio workflow.
+
+## Core Principle
+
+**You do one thing: find and explain information.**
+
+You are a documenter, not a reviewer. Your job is to help get the information needed.
+
+---
+
+## Core Responsibilities
+
+### 1. Internal Search (Project Code)
+
+| Search Type | Goal | Tools |
+|-------------|------|-------|
+| **WHERE** | Locate files/components | Glob, Grep |
+| **HOW** | Understand code logic | Read, Grep |
+| **PATTERN** | Discover existing patterns | Grep, Read |
+
+### 2. External Search (Tech Solutions)
+
+Use web search for best practices and code examples.
+
+---
+
+## Strict Boundaries
+
+### Only Allowed
+
+- Describe **what exists**
+- Describe **where it is**
+- Describe **how it works**
+- Describe **how components interact**
+
+### Forbidden (unless explicitly asked)
+
+- Suggest improvements
+- Criticize implementation
+- Recommend refactoring
+- Modify any files
+- Execute git commands
+
+---
+
+## Workflow
+
+### Step 1: Understand Search Request
+
+Analyze the query, determine:
+
+- Search type (internal/external/mixed)
+- Search scope (global/specific directory)
+- Expected output (file list/code patterns/tech solutions)
+
+### Step 2: Execute Search
+
+Execute multiple independent searches in parallel for efficiency.
+
+### Step 3: Organize Results
+
+Output structured results in report format.
+
+---
+
+## Report Format
+
+```markdown
+## Search Results
+
+### Query
+
+{original query}
+
+### Files Found
+
+| File Path | Description |
+|-----------|-------------|
+| `src/services/xxx.ts` | Main implementation |
+| `src/types/xxx.ts` | Type definitions |
+
+### Code Pattern Analysis
+
+{Describe discovered patterns, cite specific files and line numbers}
+
+### Related Spec Documents
+
+- `.aim-studio/spec/xxx.md` - {description}
+
+### Not Found
+
+{If some content was not found, explain}
+```
+
+---
+
+## Guidelines
+
+### DO
+
+- Provide specific file paths and line numbers
+- Quote actual code snippets
+- Distinguish "definitely found" and "possibly related"
+- Explain search scope and limitations
+
+### DON'T
+
+- Don't guess uncertain info
+- Don't omit important search results
+- Don't add improvement suggestions in report (unless explicitly asked)
+- Don't modify any files

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

@@ -0,0 +1,53 @@
+---
+name: story
+description: |
+  漫剧/小说创作 Agent。负责根据设定撰写剧本、角色小传和分镜描述。
+tools: Read, Bash, mcp__exa__web_search_exa
+model: opus
+---
+# Story Agent (漫剧主笔)
+
+你是 AIM Studio 的漫剧主笔 (Story Agent)。你的任务是协助用户创作高质量的漫剧或小说剧本。
+
+## 核心职责
+
+1. **世界观与角色构建**：完善设定文档。
+2. **剧本创作**：编写符合规范的分场剧本。
+3. **分镜描述**：为画面提供详细的 AI 绘画提示词建议。
+
+## 工作流程
+
+Hook 会自动注入当前任务的 Context (位于 `.aim-studio/spec/story/` 及 `implement.jsonl` 指定的文件)。
+
+### 第一步：理解需求与设定
+仔细阅读 `prd.md` (如果有) 和 `spec/story/` 下的设定文档。
+如果是新项目，优先检查 `character.md` 和 `world.md` 是否已填充。若未填充，**不要急于写剧本**，先根据用户需求完善这些设定。
+
+### 第二步：创作/完善内容
+
+**创作原则**：
+- **冲突驱动**：每场戏都应有明确的冲突或悬念。
+- **画面感**：使用视觉化的语言描述动作和环境。
+- **对白精炼**：避免说教式对话，展现角色性格。
+
+**格式要求**：
+- 严格遵守 `spec/story/script.md` 中的剧本格式。
+- 场次、地点、时间、气氛标注清晰。
+
+### 第三步：自我检查
+- 检查剧情逻辑是否连贯。
+- 检查人物行为是否符合 `character.md` 中的设定。
+- 检查格式是否规范。
+
+---
+
+## 常用指令
+
+- **完善设定**: "请根据这个创意完善角色和世界观..."
+- **撰写大纲**: "请为这个故事写一个10章的大纲..."
+- **撰写剧本**: "请写第一章的剧本..."
+- **生成分镜**: "请将第一场戏转换为分镜描述..."
+
+---
+
+请始终保持**专业、富有创造力**的语气。用**中文**回复（除非用户指定其他语言）。

package/dist/templates/claude/commands/aim/before-backend-dev.md

@@ -0,0 +1,13 @@
+Read the backend development guidelines before starting your development task.
+
+Execute these steps:
+1. Read `.trellis/spec/backend/index.md` to understand available guidelines
+2. Based on your task, read the relevant guideline files:
+   - Database work → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging → `.trellis/spec/backend/logging-guidelines.md`
+   - Type questions → `.trellis/spec/backend/type-safety.md`
+3. Understand the coding standards and patterns you need to follow
+4. Then proceed with your development plan
+
+This step is **mandatory** before writing any backend code.

package/dist/templates/claude/commands/aim/before-frontend-dev.md

@@ -0,0 +1,13 @@
+Read the frontend development guidelines before starting your development task.
+
+Execute these steps:
+1. Read `.trellis/spec/frontend/index.md` to understand available guidelines
+2. Based on your task, read the relevant guideline files:
+   - Component work → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook work → `.trellis/spec/frontend/hook-guidelines.md`
+   - State management → `.trellis/spec/frontend/state-management.md`
+   - Type questions → `.trellis/spec/frontend/type-safety.md`
+3. Understand the coding standards and patterns you need to follow
+4. Then proceed with your development plan
+
+This step is **mandatory** before writing any frontend code.

package/dist/templates/claude/commands/aim/break-loop.md

@@ -0,0 +1,153 @@
+# 剧情深度分析
+
+> 分析的价值不在于指出问题，而在于提供可行的修改方案。
+
+当完成一段创作后，使用此命令进行深度分析，提升剧情质量。
+
+---
+
+## 分析框架
+
+从以下 5 个维度分析你的创作：
+
+### 1. 角色行为一致性
+
+角色在当前场景中的行为是否符合其人设？
+
+| 检查点 | 问题 | 修正建议 |
+|--------|------|----------|
+| 性格 | 行为与性格设定矛盾 | 保持角色核心性格特征 |
+| 能力 | 做出超出能力范围的事 | 确保能力设定一致 |
+| 动机 | 行为缺乏合理动机 | 补充内心动机描写 |
+| 成长 | 行为与成长曲线不符 | 遵循角色成长轨迹 |
+
+### 2. 伏笔与呼应收束
+
+检查埋下的伏笔是否有对应收回：
+
+| 伏笔类型 | 检查方法 | 示例 |
+|----------|----------|------|
+| 道具伏笔 | 前面出现的道具是否在后续使用 | 神秘盒子在第3集出现，第8集打开 |
+| 性格伏笔 | 角色性格特点是否有铺垫 | 内向角色在第1集只说了3句话 |
+| 事件伏笔 | 事件苗头是否在后续发展 | 第1集提到的预言在第10集应验 |
+| 对话伏笔 | 关键对话是否有深意 | 老人的话暗示了真实身份 |
+
+### 3. 剧情逻辑连贯性
+
+检查剧情发展是否合理：
+
+| 问题类型 | 典型症状 | 检查方法 |
+|----------|----------|----------|
+| 因果断裂 | 事件缺乏充分铺垫 | 回顾：是什么导致这个结果？ |
+| 动机不足 | 角色行动突兀 | 回顾：角色为什么这么做？ |
+| 巧合过多 | 剧情依赖过多巧合 | 统计：巧合占比是否过高？ |
+| 节奏异常 | 节奏忽快忽慢 | 对比：与相邻场次的节奏差异 |
+
+### 4. 情感节奏把控
+
+分析情感起伏是否合理：
+
+| 阶段 | 目标 | 检查点 |
+|------|------|--------|
+| 铺垫 | 建立情感基础 | 情感是否有足够铺垫？ |
+| 升温 | 积累情感张力 | 情感是否逐步加深？ |
+| 高潮 | 情感爆发点 | 爆发是否足够强烈？ |
+| 回落 | 情感合理平复 | 回落是否过于突兀？ |
+
+### 5. 世界观一致性
+
+检查世界观设定是否前后一致：
+
+| 检查项 | 示例问题 |
+|--------|----------|
+| 地理设定 | 城市位置是否前后矛盾？ |
+| 时间设定 | 季节、节日是否合理？ |
+| 能力设定 | 角色能力是否忽强忽弱？ |
+| 规则设定 | 世界观规则是否被打破？ |
+
+---
+
+## 输出格式
+
+请按以下格式输出分析结果：
+
+```markdown
+## 剧情深度分析：[标题]
+
+### 1. 角色行为一致性
+- **角色名**: [行为描述]
+- **是否符合人设**: ✅/❌
+- **问题**: [如有]
+- **建议**: [修正建议]
+
+### 2. 伏笔与呼应收束
+| 伏笔 | 首次出现 | 呼应位置 | 状态 |
+|------|----------|----------|------|
+| ... | ... | ... | ✅/⚠️ |
+
+### 3. 剧情逻辑连贯性
+- **因果链**: [完整/断裂]
+- **问题**: [列出问题]
+- **建议**: [改进建议]
+
+### 4. 情感节奏
+- **当前阶段**: [铺垫/升温/高潮/回落]
+- **评估**: [评估结果]
+
+### 5. 世界观一致性
+- **问题**: [如有]
+- **建议**: [如有]
+
+---
+
+## 核心原则
+
+> **分析的价值不在于指出问题，而在于提供可行的修改方案。**
+
+30 分钟的分析节省 3 小时的返工。
+
+---
+
+## 分析后行动
+
+完成分析后，请：
+
+1. **标记问题优先级** - P0（必须修复）/ P1（建议修复）/ P2（可选优化）
+2. **制定修改计划** - 列出需要修改的具体位置
+3. **执行修改** - 直接在对应文件中修改
+4. **复查** - 确认修改后问题已解决
+
+> **分析文本毫无价值，真正有价值的是修改后的作品。**
+
+---
+
+## 组合使用方案
+
+### 方案一：深度检查流程
+
+```
+1. 创作完成一集
+2. /aim:break-loop       → 5维度深度分析
+3. 根据分析修改...
+4. /aim:check-story      → 快速一致性检查
+5. /aim:finish-work      → 完成工作
+```
+
+### 方案二：问题定位流程
+
+```
+1. 遇到剧情问题
+2. /aim:break-loop       → 定位问题根源
+3. 针对性修改
+4. /aim:check-story      → 确认修复
+```
+
+---
+
+## 相关命令
+
+| 命令 | 用途 |
+|------|------|
+| `/aim:check-story` | 快速一致性检查 |
+| `/aim:finish-work` | 完成工作 |
+| `/aim:story` | 继续创作 |

package/dist/templates/claude/commands/aim/check-backend.md

@@ -0,0 +1,13 @@
+Check if the code you just wrote follows the backend development guidelines.
+
+Execute these steps:
+1. Run `git status` to see modified files
+2. Read `.trellis/spec/backend/index.md` to understand which guidelines apply
+3. Based on what you changed, read the relevant guideline files:
+   - Database changes → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging changes → `.trellis/spec/backend/logging-guidelines.md`
+   - Type changes → `.trellis/spec/backend/type-safety.md`
+   - Any changes → `.trellis/spec/backend/quality-guidelines.md`
+4. Review your code against the guidelines
+5. Report any violations and fix them if found

package/dist/templates/claude/commands/aim/check-cross-layer.md

@@ -0,0 +1,153 @@
+# Cross-Layer Check
+
+Check if your changes considered all dimensions. Most bugs come from "didn't think of it", not lack of technical skill.
+
+> **Note**: This is a **post-implementation** safety net. Ideally, read the [Pre-Implementation Checklist](.trellis/spec/guides/pre-implementation-checklist.md) **before** writing code.
+
+---
+
+## Related Documents
+
+| Document | Purpose | Timing |
+|----------|---------|--------|
+| [Pre-Implementation Checklist](.trellis/spec/guides/pre-implementation-checklist.md) | Questions before coding | **Before** writing code |
+| [Code Reuse Thinking Guide](.trellis/spec/guides/code-reuse-thinking-guide.md) | Pattern recognition | During implementation |
+| **`/trellis:check-cross-layer`** (this) | Verification check | **After** implementation |
+
+---
+
+## Execution Steps
+
+### 1. Identify Change Scope
+
+```bash
+git status
+git diff --name-only
+```
+
+### 2. Select Applicable Check Dimensions
+
+Based on your change type, execute relevant checks below:
+
+---
+
+## Dimension A: Cross-Layer Data Flow (Required when 3+ layers)
+
+**Trigger**: Changes involve 3 or more layers
+
+| Layer | Common Locations |
+|-------|------------------|
+| API/Routes | `routes/`, `api/`, `handlers/`, `controllers/` |
+| Service/Business Logic | `services/`, `lib/`, `core/`, `domain/` |
+| Database/Storage | `db/`, `models/`, `repositories/`, `schema/` |
+| UI/Presentation | `components/`, `views/`, `templates/`, `pages/` |
+| Utility | `utils/`, `helpers/`, `common/` |
+
+**Checklist**:
+- [ ] Read flow: Database -> Service -> API -> UI
+- [ ] Write flow: UI -> API -> Service -> Database
+- [ ] Types/schemas correctly passed between layers?
+- [ ] Errors properly propagated to caller?
+- [ ] Loading/pending states handled at each layer?
+
+**Detailed Guide**: `.trellis/spec/guides/cross-layer-thinking-guide.md`
+
+---
+
+## Dimension B: Code Reuse (Required when modifying constants/config)
+
+**Trigger**: 
+- Modifying UI constants (label, icon, color)
+- Modifying any hardcoded value
+- Seeing similar code in multiple places
+- Creating a new utility/helper function
+- Just finished batch modifications across files
+
+**Checklist**:
+- [ ] Search first: How many places define this value?
+  ```bash
+  # Search in source files (adjust extensions for your project)
+  grep -r "value-to-change" src/
+  ```
+- [ ] If 2+ places define same value -> Should extract to shared constant
+- [ ] After modification, all usage sites updated?
+- [ ] If creating utility: Does similar utility already exist?
+
+**Detailed Guide**: `.trellis/spec/guides/code-reuse-thinking-guide.md`
+
+---
+
+## Dimension B2: New Utility Functions
+
+**Trigger**: About to create a new utility/helper function
+
+**Checklist**:
+- [ ] Search for existing similar utilities first
+  ```bash
+  grep -r "functionNamePattern" src/
+  ```
+- [ ] If similar exists, can you extend it instead?
+- [ ] If creating new, is it in the right location (shared vs domain-specific)?
+
+---
+
+## Dimension B3: After Batch Modifications
+
+**Trigger**: Just modified similar patterns in multiple files
+
+**Checklist**:
+- [ ] Did you check ALL files with similar patterns?
+  ```bash
+  grep -r "patternYouChanged" src/
+  ```
+- [ ] Any files missed that should also be updated?
+- [ ] Should this pattern be abstracted to prevent future duplication?
+
+---
+
+## Dimension C: Import/Dependency Paths (Required when creating new files)
+
+**Trigger**: Creating new source files
+
+**Checklist**:
+- [ ] Using correct import paths (relative vs absolute)?
+- [ ] No circular dependencies?
+- [ ] Consistent with project's module organization?
+
+---
+
+## Dimension D: Same-Layer Consistency
+
+**Trigger**: 
+- Modifying display logic or formatting
+- Same domain concept used in multiple places
+
+**Checklist**:
+- [ ] Search for other places using same concept
+  ```bash
+  grep -r "ConceptName" src/
+  ```
+- [ ] Are these usages consistent?
+- [ ] Should they share configuration/constants?
+
+---
+
+## Common Issues Quick Reference
+
+| Issue | Root Cause | Prevention |
+|-------|------------|------------|
+| Changed one place, missed others | Didn't search impact scope | `grep` before changing |
+| Data lost at some layer | Didn't check data flow | Trace data source to destination |
+| Type/schema mismatch | Cross-layer types inconsistent | Use shared type definitions |
+| UI/output inconsistent | Same concept in multiple places | Extract shared constants |
+| Similar utility exists | Didn't search first | Search before creating |
+| Batch fix incomplete | Didn't verify all occurrences | grep after fixing |
+
+---
+
+## Output
+
+Report:
+1. Which dimensions your changes involve
+2. Check results for each dimension
+3. Issues found and fix suggestions

package/dist/templates/claude/commands/aim/check-frontend.md

@@ -0,0 +1,13 @@
+Check if the code you just wrote follows the frontend development guidelines.
+
+Execute these steps:
+1. Run `git status` to see modified files
+2. Read `.trellis/spec/frontend/index.md` to understand which guidelines apply
+3. Based on what you changed, read the relevant guideline files:
+   - Component changes → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook changes → `.trellis/spec/frontend/hook-guidelines.md`
+   - State changes → `.trellis/spec/frontend/state-management.md`
+   - Type changes → `.trellis/spec/frontend/type-safety.md`
+   - Any changes → `.trellis/spec/frontend/quality-guidelines.md`
+4. Review your code against the guidelines
+5. Report any violations and fix them if found

package/dist/templates/claude/commands/aim/check-story.md

@@ -0,0 +1,59 @@
+---
+name: check-story
+description: 检查剧情一致性与逻辑
+---
+
+# 剧情检查
+
+检查当前剧本与设定的一致性，发现并修正潜在问题。
+
+## 检查维度
+
+### 角色一致性
+- [ ] 对白风格是否符合角色设定
+- [ ] 行为决策是否符合性格逻辑
+- [ ] 外貌描述是否一致
+- [ ] 能力表现是否在设定范围内
+- [ ] 角色成长是否合理（长篇故事）
+
+### 剧情连贯性
+- [ ] 时间线是否合理
+- [ ] 前后事件是否矛盾
+- [ ] 伏笔是否有遗漏
+- [ ] 章节衔接是否流畅
+
+### 设定一致性
+- [ ] 是否与世界观冲突
+- [ ] 力量体系是否一致
+- [ ] 场景描述是否一致
+
+### 视频格式检查（如适用）
+- [ ] 单场时长是否符合配置
+- [ ] 每集场次数是否合理
+- [ ] 视频总时长是否在预期范围
+
+## 执行方式
+
+直接执行检查：
+1. 读取当前剧集内容
+2. 读取 `.aim-studio/spec/story/` 下的设定文件（character.md, world.md）
+3. 按上述维度逐项检查
+4. 输出检查报告
+
+## 输出格式
+
+```markdown
+## 检查报告
+
+### 发现问题
+| 类型 | 位置 | 问题描述 | 严重程度 | 修改建议 |
+|------|------|----------|----------|----------|
+| 角色一致性 | EP03场次2 | 主角对白风格突变 | 中 | 调整为... |
+
+### 通过项
+- ✅ 时间线合理
+- ✅ 世界观无冲突
+
+### 建议优化
+- （可选的优化建议）
+```