film-style-library
Skill2 starsChanged 50 days agoApache-2.0View on GitHub
Lock a film or game-video project to one visual language before asset production. Use the user's references when available or create a small project-specific comparison board when an authorized image tool is present. Produces the style header, asset-sheet modifier, negative constraints, and model routing consumed by downstream Skills.
In this repository74 other files it gives its agents.
- card-gameSkill
- pixel-art-spriteSkill
- rhythm-gameSkill
- side-scrollerSkill
- visual-novelSkill
- boss-modelSkill
- character-modelSkill
- environment-sceneSkill
- vfx-effectSkill
- weapon-propSkill
- worldview-3d-asset-production-routeSkill
- film-action-combatSkill
- film-character-sheetSkill
- film-dialogue-voiceoverSkill
- film-directionSkill
- film-end-creditsSkill
- film-generate-reviewSkill
- film-locationSkill
- film-pipelineSkill
- film-prop-sheetSkill
- film-screen-captureSkill
- film-scriptSkill
- film-shot-promptSkill
- film-storySkill
- anime-action-sceneSkill
- cinematic-filmSkill
- game-cutscene-generatorSkill
- product-demoSkill
- social-media-videoSkill
- worldview-gameplay-experience-studySkill
- worldview-gameplay-video-analysisSkill
- boss-battleSkill
- hero-skill-systemSkill
- horror-chaseSkill
- narrative-choiceSkill
- platformer-levelSkill
- puzzle-mechanicSkill
- roguelike-generatorSkill
- worldview-game-asymmetric-information-cooperationSkill
- worldview-game-barricade-delay-and-route-choiceSkill
- worldview-game-character-handoff-and-shared-evidenceSkill
- worldview-game-chase-route-architectureSkill
- worldview-game-death-loop-persistent-cluesSkill
- worldview-game-driving-horror-divided-attentionSkill
- worldview-game-evidence-based-entity-identificationSkill
- worldview-game-horror-experience-rhythmSkill
- worldview-game-horror-mundane-routine-corruptionSkill
- worldview-game-horror-procedural-duty-and-incidentSkill
- worldview-game-horror-returning-place-escalationSkill
- worldview-game-horror-role-and-identity-pressureSkill
- worldview-game-key-item-backtrackingSkill
- worldview-game-limited-save-riskSkill
- worldview-game-lure-hide-escapeSkill
- worldview-game-observation-gated-stalkerSkill
- worldview-game-perception-distortion-and-trustSkill
- worldview-game-relief-resource-with-hidden-costSkill
- worldview-game-restore-power-under-pressureSkill
- worldview-game-roaming-stalker-pressureSkill
- worldview-game-safe-room-pressure-resetSkill
- worldview-game-scarce-inventory-triageSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
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
- Distinctive: line 24
Check every later reference against the lock before it enters generation.
- Distinctive: line 28
Prefer evidence in this order:
- Distinctive: line 47
Only present directions that fit the story and delivery format.
- Distinctive: line 66
If the user already supplied consistent references, confirm the inferred direction in one sentence and continue.
- Distinctive: line 70
When the project has no suitable references and image generation is available:
- Distinctive: line 73
Create no more than four candidates.
- Very specific: line 79
If image generation is unavailable or unauthorized, use text cards and set reference to null.
- Distinctive: line 102
Use only tools verified in the current environment.
- Distinctive: line 106
Before any image becomes a generation reference:
- Distinctive: line 109
If it matches, record the check and continue.
- Distinctive: line 110
If it conflicts, stop before spending quota.
- Distinctive: line 111
If the style is reopened, invalidate downstream assets and prompts that depended on the earlier lock.
- Distinctive: line 120
Do not generate production characters, locations, or props before the style lock exists.
≈ “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.
Files
Film Style Library
Why this stage exists
Words such as “animated,” “cinematic,” and “realistic” leave too many production decisions open. Line weight, material response, lighting, motion cadence, lens behavior, and surface detail can produce very different results inside the same label. A small visual comparison usually resolves that ambiguity faster than another paragraph of adjectives.
The first locked asset also influences every later reference. If its visual language is wrong, characters, locations, props, and shots inherit the mismatch. Lock style before producing those assets.
What this Skill does
- Inspect the request, existing project, and any user-supplied references.
- Infer a likely direction when the evidence is already strong; otherwise compare three or four relevant directions.
- Lock the selected direction in
films/<slug>/style.json. - Emit four fields every downstream Skill can reuse:
style_headerfor image and video prompts;sheet_modifierfor character, location, and prop sheets;negative_blockfor the main forms of visual drift;model_routingfor tools actually available in the project.
- Check every later reference against the lock before it enters generation.
Build the comparison from project evidence
Prefer evidence in this order:
- approved user-supplied images;
- an existing project style guide or locked production asset;
- project-specific comparison frames made with an authorized image tool;
- concise text cards when no image evidence can be created.
Do not ship or depend on a permanent universal image library. A generic card can carry the wrong subject, era, palette, or production assumptions into a new project. Comparison frames belong to the current project and must keep subject, framing, action, aspect ratio, and major palette constant. Change only the visual-language fields the user is choosing.
Useful direction families include:
| Direction | Shape and surface | Light and color | Motion and camera |
| Photographic cinema | Natural anatomy and materials | Motivated light and restrained grade | Physical lenses and controlled camera mass |
| Real-time game cinematic | Game-ready geometry and PBR surfaces | World lighting that can survive runtime | Readable staging and camera collision awareness |
| Graphic 2D animation | Designed silhouettes, line weight, and cel regions | Flat palettes and hard shadow groups | Held poses, smears, impact frames, selective camera motion |
| Stylized 3D animation | Simplified proportions and shaped materials | Soft bounce and controlled gradients | Clear arcs, expressive timing, stable spatial continuity |
| Documentary observation | Unstaged texture and practical detail | Available light and muted correction | Restrained handheld framing led by events |
Only present directions that fit the story and delivery format. Do not make the user choose between unrelated scenes and call that a style choice.
Conversation pattern
User: I want an animated short about two rival swordsmen.
Agent: Which direction is closest to what you see?
A. Graphic 2D — sharp silhouettes, cel regions, impact frames
B. Stylized 3D — shaped materials, soft bounce, expressive timing
C. Photographic — natural materials, motivated light, physical lenses
Reply with a letter, or send a reference image.
User: A
Agent: Locked: Graphic 2D. Every character sheet, location plate, prop sheet,
and shot prompt for this project will use that visual language.If the user already supplied consistent references, confirm the inferred direction in one sentence and continue. Ask only when the evidence conflicts or two materially different directions remain plausible.
Create project-specific comparison frames
When the project has no suitable references and image generation is available:
- Record the exact subject, framing, action, aspect ratio, and major palette shared by every candidate.
- Create no more than four candidates.
- Change only shape, surface, light, line, motion treatment, and lens behavior.
- Save candidates under
films/<slug>/style-comparison/with their generation record. - Describe each visible difference in one sentence.
- Record the selected file in
style.json; rejected candidates are not downstream references.
If image generation is unavailable or unauthorized, use text cards and set reference to null. Do not claim that a verbal choice has the same evidentiary strength as a selected image.
Style lock file
Write films/<slug>/style.json:
{
"style_id": "graphic-2d",
"style_name": "Graphic 2D animation",
"reference": "films/<slug>/style-comparison/selected.png",
"style_header": "Graphic 2D animation with designed silhouettes, clean line weight, hard cel-shadow groups, controlled impact frames, and stable spatial continuity.",
"sheet_modifier": "Production sheet with the locked silhouette, line, palette, and cel-shadow rules on a plain neutral background.",
"negative_block": "No photographic skin, no generic 3D render, no painterly texture drift, and no changes to the locked palette or proportions.",
"model_routing": {
"sheets": "<available image tool or manual workflow>",
"video": "<available video tool or runtime>",
"video_draft": "<optional available draft path>"
},
"locked_at": "<ISO-8601 timestamp>"
}Use only tools verified in the current environment. A missing provider, model, credential, or budget is a capability gap, not permission to invent availability.
Guard later references
Before any image becomes a generation reference:
- Compare silhouette, proportions, surface language, palette, lighting, and line treatment with the selected reference.
- If it matches, record the check and continue.
- If it conflicts, stop before spending quota. Name the mismatch and offer two clear choices: rebuild that asset inside the lock or deliberately reopen the project style.
- If the style is reopened, invalidate downstream assets and prompts that depended on the earlier lock.
Output
films/<slug>/style.json- optional
films/<slug>/style-comparison/candidates and generation record - one confirmation line naming the selected direction
- a list of any existing assets that conflict with the lock
Do not generate production characters, locations, or props before the style lock exists.
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
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.

