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

seedance-vocab-ru

Skill0 starsChanged 3 months agoMITView on GitHub

This skill should be used when the user asks for Russian Seedance 2.0 prompt wording, Russian cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Russian.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 Russian cinematic vocabulary when the user asks for Russian prompt wording, bilingual delivery, compact translation, role binding, …

    line 23
  2. Very specific:

    When the prompt leans on кинематографичный, эпичный, атмосферный, потрясающий, or высокое качество, load the Slop Traps table in …

    line 50

≈ “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-ru

Use Russian cinematic vocabulary when the user asks for Russian prompt wording, bilingual delivery, compact translation, role binding, first/last-frame workflow, or production vocabulary for camera, lighting, action, VFX, audio, and constraints. Preserve reference tags exactly: @Image1, @Video1, and @Audio1 stay unchanged.

Intent

Russian users arrive having already fought the hardest dialogue battle in this model and built workarounds worth respecting. The soul here is honoring that ingenuity: give them the field-tested paths, mark the limits honestly, and never promise what the community has proven fragile.

Usage Rule

Translate production intent, not every English word. Russian prompts should stay compact, concrete, and ordered by subject, action, camera, light, sound, and constraint.

Load [ref:vocab/ru] for dense role-binding, first/last-frame, camera, lighting, audio, edit/extend, constraint, and safety vocabulary.

FunctionRussian wording
Cameraмедленный наезд камеры, боковое сопровождение, фиксированный средний план, нижний ракурс, крупный план
Lightingконтровой свет, мягкий свет из окна, теплый практический источник, холодный лунный свет, контурная подсветка
Motionмедленно поворачивается, быстро проходит через кадр, капли стекают вниз, дым мягко рассеивается
Audioтихий фон помещения, короткая реплика, мягкий металлический щелчок, без музыки
First/last frame@Image1 как первый кадр, @Image2 как последний кадр, естественный переход к последнему кадру
Constraintsсохранить логотип, этикетку и форму без изменений

Compact Pattern

@Image1 — референс; сохранить лицо/форму продукта/логотип без изменений. Меняются только [движение/свет/камера]. Камера: [одно движение]. Звук: [аудиосигнал].

De-Slop Rule

When the prompt leans on кинематографичный, эпичный, атмосферный, потрясающий, or высокое качество, load the Slop Traps table in references/vocab/ru.md and decompose each into the physical elements that produce it - движение камеры, источник света, материал, звук.

Dialogue Rule

For spoken Russian, load the Russian Dialogue Notes in references/vocab/ru.md: lines of a few words, one speaker per generation, Cyrillic first with transliteration as the field-reported fallback, and a post-dub plan for fully voiced pieces.

Output Contract

Return Russian 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.