Skip to content

yzsp-studio/mediakit-shared-suite / creative-video

creative-video

Verified

当用户需要通用视频生成、视频创作、视频提示词规划或文生/图生视频时使用,包括创意视频、长视频规划、产品广告、商品广告、UGC 口播/带货/信息流视频、品牌 TVC、企业宣传片、商务视频、品牌形象片、产品功能介绍、带旁白视频,以及带参考素材的视频生成。只有用户明确提出短剧、微电影、剧情短片、影视短片、动画短片、动态漫、分集剧情、长篇剧本或等价剧情影视制作场景时,才应调用 creative-drama;其他广告、品牌、企业、产品、UGC、创意、宣传、预告、活动和信息流视频需求默认仍使用本 skill。用户明确要求把短剧/剧情素材改造成普通视频、商业广告、UGC 或企业宣传视频时,也使用本 skill。

references/cli/tree.md

View on GitHub
# `design-cli design-workspace +tree`

## 用途

返回指定 Path 下的整棵目录树,只有层级关系,不返回任何 Item、Frame 或摘要。因此它不随内容数量增长,可以一次拉完。

用来定位分支:看清项目怎么组织,决定接下来 `+ls` 哪个目录。

## 命令

```bash
design-cli design-workspace +tree \
  --canvas-workspace-id <canvas_workspace_id> \
  [--path <path>]
```

## 参数与请求

| CLI 参数 | 必填 | JSON 字段 |
|---|---:|---|
| `--canvas-workspace-id` | 是 | `canvas_workspace_id` |
| `--path` | 否 | 目录路径,**必须以 `/` 开头**;未传或为空时取根路径 `/` |

```json
{"canvas_workspace_id":"10001","path":"/"}
```

## 输出

`xml_data` 内为 `<directory_tree>`,`<tree>` 中是 ASCII 目录树文本:

```xml
<directory_tree canvas_workspace_id="10001" path="/">
  <directory path="characters">
    <directory path="female-lead">
      <directory path="expressions"/>
    </directory>
    <directory path="male-lead"/>
  </directory>
  <directory path="deliverables"/>
</directory_tree>
```

顶层 `<path>` 是请求参数的回显,便于确认请求没被改写。

🔴 **树里 `<directory>` 的 `path` 是目录名片段,不是完整路径** —— 这是本命令唯一不以 `/` 开头的地方。要 `+ls` 某个目录时沿层级拼出完整路径、**并补上开头的 `/`**:上例 `expressions` 对应 `/characters/female-lead/expressions`。不想自己拼就用 [`+ls`](ls.md),它的 `child_paths` 直接给以 `/` 开头的完整路径。

从子路径查询时,树根就是该子路径:

```xml
<directory_tree>
  <canvas_workspace_id>10001</canvas_workspace_id>
  <path>/characters</path>
  <tree>
characters/
├── female-lead/
│   ├── three-views/
│   └── expressions/
└── male-lead/
  </tree>
</directory_tree>
```

退出码与错误处理见 [`README.md`](README.md)。
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall