agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/krea-2/SKILL.md

krea-2

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Adapt still-image briefs for Krea 2, using exploratory prompting for open visual search and locked prompting plus style references for production-consistent look development.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user wants possibilities.

    line 17
  2. Distinctive:

    Use when continuity matters.

    line 21
  3. Distinctive:

    Read image brief and canon.

    line 25
  4. Distinctive:

    Keep subject and action clear before style language.

    line 27
  5. Distinctive:

    Use reference images for style instead of trying to encode every stylistic property as adjectives when references exist.

    line 29

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

Krea 2 Prompting

Krea 2 is useful when style and aesthetic exploration are part of the task.

Modes

Explore

Use when the user wants possibilities. Start from a short concrete subject or scene plus only the essential constraint. Let the first batch explore style space. On later passes, add the selected style direction and production facts.

Lock

Use when continuity matters. Write a compact but specific description of subject, composition, environment, lighting, material, palette, and selected style. Name style or moodboard references and their intended influence.

Workflow

  1. Read image brief and canon.
  2. Choose explore or lock from the brief intent.
  3. Keep subject and action clear before style language.
  4. In lock mode, preserve the exact recurring character and environment identifiers used elsewhere.
  5. Use reference images for style instead of trying to encode every stylistic property as adjectives when references exist.
  6. Save under 04_generation/prompts/krea-2/<source-id>.md.

Done

Explore mode leaves room for deliberate variation. Lock mode removes accidental variation in facts the project already decided.

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.

Check your setup, free