agentleFS
381487190381487190/opengod/skills/seedance/seedance-vocab-ja/SKILL.md

seedance-vocab-ja

Skill0 starsChanged 3 months agoMITView on GitHub

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.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Japanese cinematic vocabulary when the user asks for Japanese prompt wording, bilingual delivery, compact translation, or production …

    line 23
  2. Distinctive:

    Prefer concise production Japanese over literal translation.

    line 31
  3. Very specific:

    When the prompt leans on 映画のような, エモい, 雰囲気のある, 壮大な, or 高画質, load the Slop Traps table in references/vocab/ja.md and decompose each into the …

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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

Compact Pattern

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

De-Slop Rule

When the prompt leans on 映画のような, エモい, 雰囲気のある, 壮大な, or 高画質, load the Slop Traps table in 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.