---
name: elser-seedance-vocab-ja
description: "This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese. Use inside ElserStudio for MCP-backed planning and production; all canonical reads, writes, generation, task polling, and canvas updates require the elser-studio MCP."
---

# ElserStudio MCP execution adapter

This is the complete active adaptation of upstream `seedance-vocab-ja` from Seedance 2.0 Skill OS v6.7.0. Read [the ElserStudio root skill](../../SKILL.md) and [the upstream-to-MCP contract](../../references/upstream-mcp-integration.md) before acting.

Mandatory overrides for every instruction below:

1. Use the `elser-studio` MCP for all canonical reads, writes, asset imports, media generation, task status, and canvas synchronization. Never call a Provider, database, object store, or BYOK credential directly.
2. Map upstream project state and production artifacts onto canonical Project, World, Episode, Shot, `generationContract`, generation-task, blob, and canvas records. Never create a parallel `project-state.json` or local run ledger.
3. Treat upstream Provider tags, endpoint fields, limits, prices, and surface names as source material only. Pass provider-neutral references and prompts to MCP; the desktop capability-router owns Provider syntax and current capability selection.
4. Preserve the full directing, multilingual, safety, research, professional-production, and review knowledge below. If it conflicts with ElserStudio identity authority, spend gates, MCP schemas, or observed task state, the ElserStudio contract wins.

---


# seedance-vocab-ja

Use Japanese cinematic vocabulary when the user asks for Japanese prompt wording, bilingual delivery, compact translation, or production vocabulary for camera, lighting, motion, VFX, and audio. Preserve reference tags exactly: `@Image1`, `@Video1`, and `@Audio1` remain in English brackets.

## Intent

The user working in Japanese often lives closest to the anime tradition this model loves to render. Serve both registers - the politeness-shaped natural sentence and the production term - and let the vocabulary feel native, never translated.

## Usage Rule

Prefer concise production Japanese over literal translation. Keep the structure readable: subject, action, camera, lighting, sound, and preservation constraint.

| Function | Japanese wording |
|---|---|
| Camera | `ゆっくりドリーイン`, `横移動のトラッキング`, `固定の中景`, `低いアングル`, `クローズアップ` |
| Lighting | `逆光`, `柔らかい窓光`, `暖かいプラクティカルライト`, `冷たい月明かり`, `輪郭光` |
| Motion | `ゆっくり振り返る`, `画面を素早く横切る`, `水滴が下へ流れる`, `煙が薄く広がる` |
| Audio | `静かな環境音`, `短い台詞`, `金属音`, `音楽なし` |
| Constraints | `ロゴ、ラベル、形状を正確に維持する` |

## Compact Pattern

`@Image1を参照として、被写体の顔/商品形状/ロゴを正確に維持する。変化は[動き/光/カメラ]のみ。カメラ：[一つの動き]。音：[音声指示]。`

## Register Rule

The moment a prompt contains dialogue, load Register (文体) in `../../upstream/seedance-2.0-v6.7.0/references/vocab/ja.md` and declare one register per speaker - 敬語, です・ます体, or 普通体 - with a first-person pronoun that matches it. An unstated register is a decision handed to the model, and the mora cost differs enough to break the sync budget (ありがとう 5 → ありがとうございます 10).

## De-Slop Rule

When the prompt leans on `映画のような`, `エモい`, `雰囲気のある`, `壮大な`, or `高画質`, load the Slop Traps table in `../../upstream/seedance-2.0-v6.7.0/references/vocab/ja.md` and decompose each into the physical elements that produce it - 動作動詞＋速度＋視点, 光源＋方向＋挙動.

## Output Contract

Return Japanese prompt wording, optional English gloss when useful, and unchanged reference tags.
