agentleFS
381487190381487190/opengod/skills/seedance/seedance-style/SKILL.md

seedance-style

Skill0 starsChanged 3 months agoMITView on GitHub

This skill should be used when the user asks for visual style, art direction, render feel, period aesthetic, texture, animation style, realism level, or style-safe alternatives to studio or franchise references.

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:

    Do not use studio, franchise, artist, or living-creator names as style anchors unless the user has a clearly authorized workflow.

    line 32
  2. Very specific:

    If the user asks for a hybrid, assign each style to a layer: live-action product photography with illustrated UI overlays is clearer than …

    line 48
  3. Distinctive:

    When sequence state is present, inherit medium grammar, current clip scope, continuity locks, exact reference tags, canonical design, …

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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-style

Translate style requests into production descriptors. Style should describe medium, texture, palette, lens or render behavior, period cues, and composition. Do not rely on studio, franchise, artist, or living-creator names when a safer descriptive style can preserve the user's intent.

Intent

Users point at art they love and ask to stand near it. The soul of this skill is honoring the love while refusing the theft: find what the love is made of - light, texture, rhythm, era - and rebuild it as something the user owns. They should feel their taste was understood, not corrected.

Style Safety Rule

Do not use studio, franchise, artist, or living-creator names as style anchors unless the user has a clearly authorized workflow. Preserve the intended visual function by describing medium, texture, palette, lighting, composition, era, line quality, and motion rhythm.

User intentSafe production descriptor
Cozy hand-drawn fantasyhand-painted 2D animation, soft watercolor backgrounds, rounded character silhouettes, warm pastel palette, gentle parallax
Sharp cyberpunk actionneon noir city, wet pavement reflections, high-contrast magenta and cyan light, fast lateral tracking, angular silhouettes
Premium product realismclean commercial realism, controlled reflections, shallow depth of field, neutral background, polished material detail
Retro documentary1970s documentary texture, muted film grain, practical daylight, handheld observational framing
Children's animationsoft clay-like characters, simple expressive faces, bright primary palette, bouncy squash-and-stretch motion

Layered Style Method

Separate style into layers instead of one broad label: medium (live action, stop-motion, 2D, 3D, miniature), surface (paper grain, clay, brushed metal, glass, fabric), palette (pastel, monochrome, sodium orange), camera/render (macro, shallow focus, orthographic, handheld), and motion rhythm (gentle, staccato, elastic, realistic weight).

Hybrid Style Rule

If the user asks for a hybrid, assign each style to a layer: live-action product photography with illustrated UI overlays is clearer than mixing many named influences. Keep character design, environment, lighting, and VFX in compatible registers.

Load [ref:2d-anime-grammar] when the style is 2D, anime, or cel-based — it covers layer grammar, burst-versus-held motion, impact frames, smears, rostrum-camera language, and the no-lens rule for stylized work.

Source-Look Lock

Field-observed from Chinese practice: realism styles stabilize when the prompt names the capture source and embraces its artifacts instead of fighting them. Classify the intended look, then lock its signature flaws deliberately:

Source lookLock its artifacts
Phone-shot daily / UGCvertical handheld phone footage, slight grip sway, auto-exposure shifts, ambient room sound
Livestreamfixed webcam framing, flat ring light, mild compression, real-time caption pacing
Security / dashcamlocked high-angle camera, timestamp burn-in feel, low-light noise, no camera response to events
Vintage filmgrainy film texture, gate weave, halation around highlights, era-correct contrast
Studio commercialcontrolled reflections, clean background, polished material detail, zero handheld motion

The flaw vocabulary is the style: faux-UGC that looks too clean reads as fake twice over.

Sequence State

When sequence state is present, inherit medium grammar, current clip scope, continuity locks, exact reference tags, canonical design, accepted transient state, and reserved future beats. Style may color the clip, but it cannot change identity, wardrobe, product design, surface profile, or events reserved for later.

Output Contract

Return a safe style descriptor, any protected-name rewrite, and one integrated prompt sentence.

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.