Rivya AI Docs

Rivya Prompt Writing Guide

Write Rivya prompts for images, videos, audio, and chat by defining the task, subject, constraints, references, review target, and criteria.

Use this prompt writing guide when a Rivya task depends on a clearer image prompt, video prompt, audio brief, chat request, or reusable prompt example.

A good Rivya prompt is not the longest prompt.

It is the prompt that makes the task, subject, constraints, and review target clear enough for the first useful result.

This page gives a practical structure you can reuse across image, video, audio, and chat workflows.

Start With The Task

Start by naming the job.

Examples:

  • create a clean product photo
  • make a short product demo video
  • write a voice-over script
  • generate a landing-page hero concept
  • explain this uploaded image
  • solve this math problem step by step

The task tells Rivya what kind of output you expect. Without it, the rest of the prompt becomes style noise.

Describe The Subject Clearly

After the task, describe the subject.

For images and videos, include visible details:

  • product type
  • material
  • color
  • shape
  • scene
  • action
  • audience

For audio and text, include functional details:

  • speaker style
  • language
  • tone
  • length
  • target listener
  • use case

Clear subject details are more useful than generic words like premium, cinematic, modern, or viral.

Add Constraints Only When Needed

Constraints are useful when they prevent a bad output.

Good constraints are specific:

  • no busy background
  • keep the label readable
  • use a calm narrator voice
  • avoid exaggerated camera movement
  • keep the answer suitable for a beginner

Too many constraints can make a prompt brittle. Add the constraints that matter most for the next review, not every possible preference.

Use References Intentionally

References work best when you say what they should control.

A reference can guide:

  • product identity
  • composition
  • lighting
  • brand style
  • voice direction
  • previous output continuity

Do not assume the model knows which part of a reference matters. Pair uploads with a short note such as use this for product shape, not background or use this for mood and lighting only.

Write For Review

A prompt should help you review the result.

Before submitting, ask:

  • What would make this output usable?
  • What would make it unusable?
  • What is the one thing that must work first?
  • Should this be a quick test or a polished attempt?

If the answer is unclear, simplify the prompt before generating.

Common Prompt Mistakes

Common mistakes include:

  • starting with style before task
  • asking for several asset types in one prompt
  • using references without explaining their role
  • overloading one short video with too many scenes
  • asking for exact text inside generated visuals
  • trying to fix every possible issue in the first run

Better prompting is usually clearer prompting, not more complicated prompting.

Prompt Use Checklist

When the next step depends on a prompt, template, or example, check:

  • Identify the task before choosing style words.
  • Keep the subject, constraints, reference role, and review target visible.
  • Use templates as starting points, not fixed scripts.
  • Decide whether the prompt should run from a public prompt hub such as Image Prompts or Video Prompts, a model page, or Studio.
  • Save useful prompt variants before rewriting them heavily.

The goal is to make prompts reusable without making them generic.

When To Rework The Prompt

Rework the prompt when it asks for several asset types at once, hides the review criteria, gives references no role, or tries to solve every edge case in one run.

In those cases, narrow the task before adding more adjectives or switching models.

Table of Contents