Create your own recipe

Create your own recipe when the same content job keeps requiring the same audience, structure, and review rules. Custom recipes in Create run against the completed response you have open.

Define the repeated job

Before writing the recipe, identify the stable result it should produce across different responses:

• The reader and purpose.
• The evidence it must include.
• The required order or sections.
• Any claims or material it must exclude.

If the request applies to only one response, it may be better handled while editing that result. A recipe is most useful when you expect to run it again.

Write the recipe

1. From Create, open New recipe.
2. Give it a name that describes the output, then add a one-line description that helps someone choose it.
3. Write the prompt as a production brief.
4. Add tags if they will help you find related recipes.
5. Choose Private or Team, then save it.

The name, description, and tags organize the recipe. The prompt controls what holito creates.

Use a structure such as:

Produce: [the output and its purpose]
For: [the audience]
Use: [the evidence and details that matter]
Structure: [the required order or sections]
Rules: [grounding, attribution, exclusions, length, or approval needs]

Tell holito what to do when the response does not support a required detail. Asking it to mark the gap or omit the claim is safer than asking it to complete the story.

Choose who can use it

Private recipes are visible only to you. Team recipes are available to members of the active organisation, including people working in its other workspaces.

Start privately when the recipe is still being tested. Share it with the team when its name, description, and prompt produce a result others can understand and review without relying on your private context.

Run the saved recipe on more than one representative response before treating it as a standard. Use Recipe best practices to improve repeated weaknesses.