القائمة
Use when creating product/logo reference locks, packshot constraints, exact claim text, brand colors, OCR baselines, forbidden alterations, and product-image QA.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to read, modify, search, add, or delete nodes on a project's canvas. Triggers on "canvas", "scene", "node", "add a clip", "edit the timeline", "what's in the canvas", "rearrange", "remove the X". Use the `clash canvas` CLI subcommands; always pass `--json` for parseable output.
Use when the user wants to list, switch, create, inspect, or delete Clash projects. Triggers on "project", "switch project", "open project", "new project", "delete project", or any reference to a project by name. Use the `clash projects` CLI subcommands.
Use when the user wants to cut, trim, split, reorder, or add media to a Project Timeline, or change its fps or composition size. Round-trip the Timeline through timelines/<id>.timeline.yaml with public `clash timeline list`, `pull`, and `apply` commands.
Use when the user wants to read, modify, search, add, or delete nodes on a project's canvas. Triggers on "canvas", "scene", "node", "add a clip", "edit the timeline", "what's in the canvas", "rearrange", "remove the X". Use the `clash canvas` CLI subcommands; always pass `--json` for parseable output.
Use when the user wants to list, switch, create, inspect, or delete Clash projects. Triggers on "project", "switch project", "open project", "new project", "delete project", or any reference to a project by name. Use the `clash projects` CLI subcommands.
AI video production with the Clash platform. Use this skill whenever the user mentions Clash, video projects, canvas editing, image/video generation, storyboards, or wants to create visual content. Also use when the user asks about managing Clash projects, tokens, or CLI setup.
| name | product-logo-lock |
| description | Use when creating product/logo reference locks, packshot constraints, exact claim text, brand colors, OCR baselines, forbidden alterations, and product-image QA. |
Use this skill before generating product or TVC images.
Record:
Generated panels must preserve approved product/logo constraints or be marked blocked for review.
For Clash-managed local projects, make logo and packshot roles explicit before generation:
clash production plan-reference-roles \
--target-asset asset-reference-pack \
--roles references/product-reference-roles.json \
--out actions/product-reference-roles.json \
--json
Use logo-lock for brand assets and product-packshot for packshots. These
roles should be locked and copy-on-write so downstream panels cannot mutate the
approved source asset.
After a generated frame, storyboard panel, or TVC end card exists, provide agent/local analyzer evidence instead of silently trusting the render:
clash production plan-product-logo-qa \
--target-asset asset-tvc-frame \
--reference-roles projections/references/asset-reference-pack.semantic-reference-roles.json \
--evidence qa/visual/product-logo-evidence.json \
--out actions/product-logo-qa.json \
--report qa/image/asset-tvc-frame.product-logo-qa.json \
--json
clash production apply-metadata \
--action actions/product-logo-qa.json \
--assets assets/manifest.json \
--json
The evidence file may come from OCR, visual inspection, or a local image QA tool, but it must name the semantic role being checked. Failed or missing locked-role evidence should block release instead of mutating the reference asset.