runware-prompting
Skill8 starsChanged 5 months agoMITView on GitHub
Write effective prompts for Runware's image and video models. Use whenever an agent is composing a prompt and wants model-appropriate phrasing, in-image text, negation, or cinematic grammar. Foundation skill - outcome skills lean on it for the actual wording.
In this repository32 other files it gives its agents.
- add-audio-to-videoSkill
- animate-imageSkill
- bring-your-own-modelSkill
- character-consistencySkill
- cinematic-videoSkill
- composite-sceneSkill
- controlled-generationSkill
- dialogue-audioSkill
- edit-imageSkill
- edit-videoSkill
- game-assets-2dSkill
- image-to-3d-assetSkill
- llm-agentSkill
- logos-and-vectorsSkill
- multi-shot-videoSkill
- musicSkill
- photoreal-stillsSkill
- product-ad-videoSkill
- product-photographySkill
- reframe-videoSkill
- replace-in-videoSkill
- restore-and-upscaleSkill
- runware-modelsSkill
- runware-runSkill
- talking-avatarSkill
- text-in-imageSkill
- train-style-modelSkill
- ugc-adSkill
- video-upscaleSkill
- vision-understandingSkill
- voice-cloningSkill
- voiceoverSkill
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
- Distinctive: line 30
Cinematic grammar (Gemini-Omni, Luma, Runway, Kling): use a compact scaffold - framing/camera motion, style, lighting, location, action.
- Very specific: line 32
Multi-shot in one call (HappyHorse, Kling Turbo, Pixverse): use the model's beat/shot template (shot N, seconds, description.
≈ “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
Prompting Runware models
Different model families read prompts differently. Match the phrasing to the model. When in doubt, confirm the model's strengths via runware-models.
Cross-family principles
- Layer the scene for complex images: subject → environment → camera/framing → lighting → mood. Name objects and their positions, not just objects.
- Short and interpretive vs long and structured. Modern models reward concise intent; older/diffusion models reward dense descriptive stacks. Pick per family below.
- In-image text is quoted, exact, and placed. To render words in an image, quote the exact string and state placement and style. Models render what you quote, not what you describe.
- Negation: some models take inline negation in the positive prompt (write "Negative prompt: X, Y" as a clause and the model obeys); others have a real
negativePromptfield. Check the schema.
Image families
- LLM-based image models (gpt-image-2, Nano Banana 2): parse full natural language. Use structured briefs, inline negation, even pseudocode; say "photorealistic" explicitly; use camera language for composition. Nano Banana 2 has a
thinkingsetting for hard prompts and renders legible in-image text well; it also grounds on real facts viaproviderSettings.google.webSearch. - Seedream / Recraft: short interpretive prompts work; layer (subject → lighting → composition) for control. Recraft's Utility variants give flat, predictable output for mockups; constrain color with
settings.colors. - Ideogram: operates on a structured JSON (reserved keys:
description,style,background,elements), not a sentence. Text is a first-classtextelement. Use Magic Prompt to expand natural language, or hand-craft the JSON for repeatable layouts. - Grok / typography models: quoting the exact text is non-negotiable; placement and script/style are refinements.
Video families
- Cinematic grammar (Gemini-Omni, Luma, Runway, Kling): use a compact scaffold - framing/camera motion, style, lighting, location, action. Three to four sentences beat a wall of adjectives. These models read camera vocabulary (dolly, push-in, rack focus) directly.
- Image-to-video (Runway Gen, Pixverse, HappyHorse): the image fixes the subject and composition; the prompt should direct only the motion (subject motion + camera motion). Don't re-describe the scene the image already shows.
- Multi-shot in one call (HappyHorse, Kling Turbo, Pixverse): use the model's beat/shot template (
shot N, seconds, description;orBegin with… / Cut to… / End on…). Per-shot seconds must sum to the totalduration.
Quality bar
- Phrasing matches the chosen model family (not a generic prompt).
- Any required in-image text is quoted exactly and placed.
- For video, the prompt directs motion/camera, not a static scene description.
Related skills
runware-models (which model), runware-run (send it), and outcome skills (each adds its domain build-order on top of these basics).
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.

