@fifine/aim-studio 0.0.1

package/dist/templates/claude/commands/aim/create-command.md

@@ -0,0 +1,154 @@
+# Create New Slash Command
+
+Create a new slash command in both `.cursor/commands/` (with `trellis-` prefix) and `.claude/commands/trellis/` directories based on user requirements.
+
+## Usage
+
+```
+/aim:create-command <command-name> <description>
+```
+
+**Example**:
+```
+/aim:create-command review-pr Check PR code changes against project guidelines
+```
+
+## Execution Steps
+
+### 1. Parse Input
+
+Extract from user input:
+- **Command name**: Use kebab-case (e.g., `review-pr`)
+- **Description**: What the command should accomplish
+
+### 2. Analyze Requirements
+
+Determine command type based on description:
+- **Initialization**: Read docs, establish context
+- **Pre-development**: Read guidelines, check dependencies
+- **Code check**: Validate code quality and guideline compliance
+- **Recording**: Record progress, questions, structure changes
+- **Generation**: Generate docs, code templates
+
+### 3. Generate Command Content
+
+Based on command type, generate appropriate content:
+
+**Simple command** (1-3 lines):
+```markdown
+Concise instruction describing what to do
+```
+
+**Complex command** (with steps):
+```markdown
+# Command Title
+
+Command description
+
+## Steps
+
+### 1. First Step
+Specific action
+
+### 2. Second Step
+Specific action
+
+## Output Format (if needed)
+
+Template
+```
+
+### 4. Create Files
+
+Create in both directories:
+- `.cursor/commands/trellis-<command-name>.md`
+- `.claude/commands/trellis/<command-name>.md`
+
+### 5. Confirm Creation
+
+Output result:
+```
+[OK] Created Slash Command: /<command-name>
+
+File paths:
+- .cursor/commands/trellis-<command-name>.md
+- .claude/commands/trellis/<command-name>.md
+
+Usage:
+/aim:<command-name>
+
+Description:
+<description>
+```
+
+## Command Content Guidelines
+
+### [OK] Good command content
+
+1. **Clear and concise**: Immediately understandable
+2. **Executable**: AI can follow steps directly
+3. **Well-scoped**: Clear boundaries of what to do and not do
+4. **Has output**: Specifies expected output format (if needed)
+
+### [X] Avoid
+
+1. **Too vague**: e.g., "optimize code"
+2. **Too complex**: Single command should not exceed 100 lines
+3. **Duplicate functionality**: Check if similar command exists first
+
+## Naming Conventions
+
+| Command Type | Prefix | Example |
+|--------------|--------|---------|
+| Session Start | `start` | `start` |
+| Pre-development | `before-` | `before-frontend-dev` |
+| Check | `check-` | `check-frontend` |
+| Record | `record-` | `record-session` |
+| Generate | `generate-` | `generate-api-doc` |
+| Update | `update-` | `update-changelog` |
+| Other | Verb-first | `review-code`, `sync-data` |
+
+## Example
+
+### Input
+```
+/aim:create-command review-pr Check PR code changes against project guidelines
+```
+
+### Generated Command Content
+```markdown
+# PR Code Review
+
+Check current PR code changes against project guidelines.
+
+## Steps
+
+### 1. Get Changed Files
+```bash
+git diff main...HEAD --name-only
+```
+
+### 2. Categorized Review
+
+**Frontend files** (`apps/web/`):
+- Reference `.aim-studio/spec/frontend/index.md`
+
+**Backend files** (`packages/api/`):
+- Reference `.aim-studio/spec/backend/index.md`
+
+### 3. Output Review Report
+
+Format:
+
+## PR Review Report
+
+### Changed Files
+- [file list]
+
+### Check Results
+- [OK] Passed items
+- [X] Issues found
+
+### Suggestions
+- [improvement suggestions]
+```

package/dist/templates/claude/commands/aim/export.md

@@ -0,0 +1,187 @@
+---
+name: export
+description: 导出剧本用于AI视频生成
+---
+
+# 导出剧本
+
+将剧本导出为可直接粘贴到 AI 视频生成工具（如 Seedance）的格式。
+
+## 导出流程
+
+### 1. 选择导出范围
+
+```bash
+# 导出单集
+/aim:export --ep 1
+
+# 导出多集
+/aim:export --ep 1-5
+
+# 导出全部
+/aim:export --all
+```
+
+### 2. 选择导出格式
+
+| 格式 | 用途 | 说明 |
+|------|------|------|
+| `seedance` | Seedance Web 端 | 单场次独立 prompt，包含上下文 |
+| `batch` | 批量生成 | 所有场次合并，适合批量处理 |
+| `review` | 预览检查 | 带注释格式，便于检查 |
+| `text` | 纯文本发布 | 去除备注，统一标点 |
+
+### 3. 导出内容结构
+
+每次导出会生成以下文件：
+
+```
+export/
+├── EP01/
+│   ├── scene_01.txt      # 场次1 - 可直接粘贴
+│   ├── scene_02.txt      # 场次2 - 可直接粘贴
+│   ├── context.txt       # 本集上下文摘要
+│   └── characters.txt    # 本集角色参考
+├── EP02/
+│   └── ...
+└── global_context.txt    # 全局设定（角色、世界观）
+```
+
+---
+
+## Seedance 导出格式
+
+### 单场次 Prompt 模板
+
+每个场次文件包含完整的上下文信息，可直接粘贴：
+
+```
+【角色设定】
+[角色名]：[外貌描述]，[性格关键词]
+（如有多位角色，逐一列出）
+
+【场景设定】
+[场景名称]：[环境描述]，[氛围]
+
+【前情提要】（如适用）
+[上一场次的关键事件，1-2句话]
+
+【本场次剧本】
+场次 X：[场景] - [时间] - [气氛] - [时长]
+
+[画面描述]
+
+[角色名]：(情绪) 台词
+
+[画面描述]
+
+...
+
+【视觉风格】
+[风格关键词，如：xianxia, fantasy, cinematic lighting]
+```
+
+### 示例输出
+
+```
+【角色设定】
+沈安在：白衣中年男子，两鬓霜白，面容俊俏，气质高深莫测。性格：腹黑、护短、爱演。
+慕容天：少年身形，目光从落寞到坚定。性格：勤奋、尊师重道、意志坚定。
+
+【场景设定】
+青云峰主殿：破旧的大殿，阳光透过残破窗棂洒落，萧条冷清的氛围。
+
+【前情提要】
+慕容天决定下山离开，沈安在内心吐槽自己的穿越遭遇。
+
+【本场次剧本】
+场次 1：青云峰主殿内 - 清晨 - 萧条落寞 - 30秒
+
+白衣中年沈安在瘫坐在太师椅上，神情苦涩。殿外，少年慕容天背着大包小包，站在门口。
+
+慕容天：(低沉) 师父，弟子不孝，今日便要下山继承家业，还望师父珍重！
+
+沈安在听到声音，却懒得出门。镜头推进他的脸，苦涩中带着自嘲。
+
+沈安在：(内心独白) 老天啊，你是让我来这边受折磨的吗？
+
+【视觉风格】
+xianxia, chinese fantasy, cinematic lighting, melancholic atmosphere
+```
+
+---
+
+## 保持一致性的策略
+
+### 1. 全局上下文文件
+
+`global_context.txt` 包含：
+- 核心角色设定（外貌、性格、说话风格）
+- 世界观设定（力量体系、地理环境）
+- 视觉风格关键词
+
+**使用方式**：
+- 首次使用时，先粘贴全局上下文
+- 或将全局上下文保存为 Seedance 的"项目设定"
+
+### 2. 集间上下文文件
+
+每集的 `context.txt` 包含：
+- 本集角色状态快照
+- 本集关键事件摘要
+- 上一集结尾状态
+
+### 3. 角色参考文件
+
+每集的 `characters.txt` 包含：
+- 本集出场角色的完整设定
+- SD Prompt 片段
+- 服装变化记录
+
+---
+
+## 执行方式
+
+```bash
+# 交互式导出
+/aim:export
+
+# 快速导出（使用默认设置）
+/aim:export --ep 1 --format seedance
+
+# 导出纯文本格式
+/aim:export --ep 1 --format text
+
+# 导出并打开目录
+/aim:export --ep 1 --open
+```
+
+---
+
+## 导出后检查清单
+
+- [ ] 每个场次文件是否可独立使用？
+- [ ] 角色设定是否完整？
+- [ ] 前情提要是否准确？
+- [ ] 视觉风格是否一致？
+- [ ] 时长是否符合配置？
+
+---
+
+## 注意事项
+
+1. **首次使用**：建议先粘贴 `global_context.txt` 到 Seedance，建立项目基准
+2. **连续剧**：每集开始前，先粘贴上一集的 `context.txt`
+3. **角色一致性**：使用相同的角色描述和 SD Prompt 片段
+4. **时长控制**：根据视频格式配置，调整每场次的字数
+
+---
+
+## 纯文本导出（传统格式）
+
+如需导出为传统发布格式，直接读取当前剧本并整理为适合发布的格式：
+- 去除构建过程中的备注
+- 统一标点符号
+- 优化段落间距
+
+输出目标：纯文本 / 长图文案 / 剧本杀格式（请根据用户需求调整）

package/dist/templates/claude/commands/aim/finish-work.md

@@ -0,0 +1,104 @@
+---
+name: finish-work
+description: 完成创作并记录工作
+---
+
+# 完成工作
+
+完成当前创作任务后，进行最终检查并记录工作内容。
+
+---
+
+## 适用场景
+
+- 完成一集剧本创作
+- 完成一个场次的创作
+- 结束创作会话
+
+---
+
+## 检查清单
+
+### 1. 内容完整性
+
+- [ ] 剧本内容是否完整
+- [ ] Seedance 2.0 六要素是否齐全
+- [ ] 角色行为是否符合人设
+- [ ] 剧情逻辑是否连贯
+
+### 2. 格式检查
+
+- [ ] 文件格式是否符合规范
+- [ ] 命名是否一致
+- [ ] 段落划分是否合理
+
+### 3. 质量检查
+
+- [ ] 是否有明显的逻辑错误
+- [ ] 角色对话是否自然
+- [ ] 场景描述是否清晰
+
+### 4. 相关文件更新
+
+- [ ] 是否需要更新角色设定 (character.md)
+- [ ] 是否需要更新世界观设定 (world.md)
+- [ ] 是否需要添加新角色
+
+---
+
+## 执行步骤
+
+### 步骤 1：自我检查
+
+按照上述清单逐项检查。
+
+### 步骤 2：可选检查
+
+如果需要更深入的检查：
+
+```
+/aim:check-story
+```
+
+### 步骤 3：记录工作
+
+使用记录命令保存本次工作内容：
+
+```bash
+python3 ./.aim-studio/scripts/add_session.py --title "<工作标题>" --summary "<工作摘要>"
+```
+
+### 步骤 4：报告完成
+
+向用户报告完成的内容和下一步建议。
+
+---
+
+## 组合使用方案
+
+### 完整工作流程
+
+```
+1. 创作中...
+2. /aim:check-story       → 检查剧情一致性
+3. 修改问题...
+4. /aim:finish-work       → 完成工作
+5. /aim:record-session    → 记录工作内容
+```
+
+### 快速完成流程
+
+```
+1. 创作中...
+2. /aim:finish-work       → 快速完成检查
+```
+
+---
+
+## 相关命令
+
+| 命令 | 用途 |
+|------|------|
+| `/aim:check-story` | 检查剧情一致性 |
+| `/aim:record-session` | 记录工作内容 |
+| `/aim:start` | 开始新会话 |

package/dist/templates/claude/commands/aim/integrate-skill.md

@@ -0,0 +1,219 @@
+# Integrate Claude Skill into Project Guidelines
+
+Adapt and integrate a Claude global skill into your project's development guidelines (not directly into project code).
+
+## Usage
+
+```
+/aim:integrate-skill <skill-name>
+```
+
+**Examples**:
+```
+/aim:integrate-skill frontend-design
+/aim:integrate-skill mcp-builder
+```
+
+## Core Principle
+
+> [!] **Important**: The goal of skill integration is to update **development guidelines**, not to generate project code directly.
+>
+> - Guidelines content -> Write to `.aim-studio/spec/{target}/doc.md`
+> - Code examples -> Place in `.aim-studio/spec/{target}/examples/skills/<skill-name>/`
+> - Example files -> Use `.template` suffix (e.g., `component.tsx.template`) to avoid IDE errors
+>
+> Where `{target}` is `frontend` or `backend`, determined by skill type.
+
+## Execution Steps
+
+### 1. Read Skill Content
+
+```bash
+openskills read <skill-name>
+```
+
+If the skill doesn't exist, prompt user to check available skills:
+```bash
+# Available skills are listed in AGENTS.md under <available_skills>
+```
+
+### 2. Determine Integration Target
+
+Based on skill type, determine which guidelines to update:
+
+| Skill Category | Integration Target |
+|----------------|-------------------|
+| UI/Frontend (`frontend-design`, `web-artifacts-builder`) | `.aim-studio/spec/frontend/` |
+| Backend/API (`mcp-builder`) | `.aim-studio/spec/backend/` |
+| Documentation (`doc-coauthoring`, `docx`, `pdf`) | `.aim-studio/` or create dedicated guidelines |
+| Testing (`webapp-testing`) | `.aim-studio/spec/frontend/` (E2E) |
+
+### 3. Analyze Skill Content
+
+Extract from the skill:
+- **Core concepts**: How the skill works and key concepts
+- **Best practices**: Recommended approaches
+- **Code patterns**: Reusable code templates
+- **Caveats**: Common issues and solutions
+
+### 4. Execute Integration
+
+#### 4.1 Update Guidelines Document
+
+Add a new section to the corresponding `doc.md`:
+
+```markdown
+@@@section:skill-<skill-name>
+## # <Skill Name> Integration Guide
+
+### Overview
+[Core functionality and use cases of the skill]
+
+### Project Adaptation
+[How to use this skill in the current project]
+
+### Usage Steps
+1. [Step 1]
+2. [Step 2]
+
+### Caveats
+- [Project-specific constraints]
+- [Differences from default behavior]
+
+### Reference Examples
+See `examples/skills/<skill-name>/`
+
+@@@/section:skill-<skill-name>
+```
+
+#### 4.2 Create Examples Directory (if code examples exist)
+
+```bash
+# Directory structure ({target} = frontend or backend)
+.aim-studio/spec/{target}/
+|-- doc.md                      # Add skill-related section
+|-- index.md                    # Update index
++-- examples/
+    +-- skills/
+        +-- <skill-name>/
+            |-- README.md               # Example documentation
+            |-- example-1.ts.template   # Code example (use .template suffix)
+            +-- example-2.tsx.template
+```
+
+**File naming conventions**:
+- Code files: `<name>.<ext>.template` (e.g., `component.tsx.template`)
+- Config files: `<name>.config.template` (e.g., `tailwind.config.template`)
+- Documentation: `README.md` (normal suffix)
+
+#### 4.3 Update Index File
+
+Add to the Quick Navigation table in `index.md`:
+
+```markdown
+| <Skill-related task> | <Section name> | `skill-<skill-name>` |
+```
+
+### 5. Generate Integration Report
+
+---
+
+## Skill Integration Report: `<skill-name>`
+
+### # Overview
+- **Skill description**: [Functionality description]
+- **Integration target**: `.aim-studio/spec/{target}/`
+
+### # Tech Stack Compatibility
+
+| Skill Requirement | Project Status | Compatibility |
+|-------------------|----------------|---------------|
+| [Tech 1] | [Project tech] | [OK]/[!]/[X] |
+
+### # Integration Locations
+
+| Type | Path |
+|------|------|
+| Guidelines doc | `.aim-studio/spec/{target}/doc.md` (section: `skill-<name>`) |
+| Code examples | `.aim-studio/spec/{target}/examples/skills/<name>/` |
+| Index update | `.aim-studio/spec/{target}/index.md` |
+
+> `{target}` = `frontend` or `backend`
+
+### # Dependencies (if needed)
+
+```bash
+# Install required dependencies (adjust for your package manager)
+npm install <package>
+# or
+pnpm add <package>
+# or
+yarn add <package>
+```
+
+### [OK] Completed Changes
+
+- [ ] Added `@@@section:skill-<name>` section to `doc.md`
+- [ ] Added index entry to `index.md`
+- [ ] Created example files in `examples/skills/<name>/`
+- [ ] Example files use `.template` suffix
+
+### # Related Guidelines
+
+- [Existing related section IDs]
+
+---
+
+## 6. Optional: Create Usage Command
+
+If this skill is frequently used, create a shortcut command:
+
+```bash
+/aim:create-command use-<skill-name> Use <skill-name> skill following project guidelines
+```
+
+## Common Skill Integration Reference
+
+| Skill | Integration Target | Examples Directory |
+|-------|-------------------|-------------------|
+| `frontend-design` | `frontend` | `examples/skills/frontend-design/` |
+| `mcp-builder` | `backend` | `examples/skills/mcp-builder/` |
+| `webapp-testing` | `frontend` | `examples/skills/webapp-testing/` |
+| `doc-coauthoring` | `.aim-studio/` | N/A (documentation workflow only) |
+
+## Example: Integrating `mcp-builder` Skill
+
+### Directory Structure
+
+```
+.aim-studio/spec/backend/
+|-- doc.md                           # Add MCP section
+|-- index.md                         # Add index entry
++-- examples/
+    +-- skills/
+        +-- mcp-builder/
+            |-- README.md
+            |-- server.ts.template
+            |-- tools.ts.template
+            +-- types.ts.template
+```
+
+### New Section in doc.md
+
+```markdown
+@@@section:skill-mcp-builder
+## # MCP Server Development Guide
+
+### Overview
+Create LLM-callable tool services using MCP (Model Context Protocol).
+
+### Project Adaptation
+- Place services in a dedicated directory
+- Follow existing TypeScript and type definition conventions
+- Use project's logging system
+
+### Reference Examples
+See `examples/skills/mcp-builder/`
+
+@@@/section:skill-mcp-builder
+```