How to remix a prompt recipe
Aveniqa
Learn what to preserve, what to change and what to record when adapting an AI creation, including model settings, source attribution and remix history.
What is a prompt recipe?
On Aveniqa, a prompt recipe connects a creation with its prompt and available creation details. These may include a model, parameters, references and source information. A remix adapts an existing recipe into a new creative direction. Its history can help readers see the relationship between the source and later variations.
Inspect the original before changing it
Open the work, read its prompt or creation process, and check the model, references and available parameters. Decide which property you want to keep: perhaps the composition, the material treatment or the subject. Missing settings and unknown rights remain unknown. A visually similar output alone does not prove that the original process has been reproduced.
Give the remix a specific goal
Write one sentence that describes your intended change. This makes the result easier to compare and the remix easier to explain. For example, keep the composition and change the material treatment:
Keep the low camera angle, off-center teapot and soft window light. Change the teapot from matte ceramic to brushed stainless steel, with restrained reflections and the same cream background.
Use the available action on the work
Aveniqa shows remix and generation actions according to the work and the available model capabilities. Sign in when an action requires an account. Check the selected model and the displayed generation cost before submitting. If generation is unavailable for a work, its public prompt and creation details can still be read; availability should not be inferred from the presence of a model name.
Publish a useful record of the change
Give the new work a descriptive title and explain what changed. Retain the source and parent relationship when remixing through the platform. Record parameters you actually used, and distinguish reference material from your own output. Check the source work's license and attribution requirements. A branch history documents relationships; it does not establish copyright ownership or a license.