Aidelly Docs
App Guides

Prompt Library

Build, save, and run reusable prompt patterns with structured inputs — so repeatable tasks don't start from a blank chat every time.

What Prompt Library is for

Some content tasks are recurring with the same shape: weekly newsletter intros, product launch announcement copy, monthly recap threads. Typing the same setup prompt every time wastes time and produces inconsistent output.

Prompt Library lets you save the prompt and its required inputs as a reusable template. Run it, fill in the fields, get consistent output. Your team can run the same templates — no one has to remember the "good" prompt anyone wrote last month.

This guide walks you through:

  1. Running an existing template
  2. Building your own from scratch
  3. Saving and sharing across the workspace
  4. Versioning so changes don't break old runs

Before you start

  • (Recommended) Look at the built-in templates first — they're a fast way to see the format.
  • Set up Brand Profile so prompts that reference brand context have real content to draw on.

Step 1 — Open Prompt Library

  1. In the left sidebar, click 📚 Prompts.
  2. The page lists two sets:
    • Built-in templates — provided by Aidelly, kept up to date
    • Workspace prompts — your own and your team's saved templates

Step 2 — Run an existing template

  1. Click any template in the list.
  2. The runner panel opens on the right.
  3. Fill in the structured input fields:
    • Some are required (red asterisk)
    • Some are dropdowns, some are textareas
    • Required fields disable the Run button until filled
  4. Click Run.
  5. Output appears below the inputs in 5–15 seconds.

Step 3 — Refine the output

The output is editable.

  1. Click into the output area and tweak.
  2. Regenerate rolls a new run with the same inputs.
  3. Regenerate with changes lets you adjust an input mid-run.
  4. Use this sends the output to Create Post or saves to drafts.

Step 4 — Save the run for later

Every run is automatically saved to Recent runs (right side of the page).

  1. Click Recent runs to see your last ~50 runs.
  2. Click any run to see its inputs, output, and the template version that ran.
  3. Click Re-run with same inputs to repeat exactly, or Duplicate to start a new run from the same starting state.

Step 5 — Build your own template

When you've found a prompt pattern in Chat that consistently works:

  1. Click + New template in the top-right.

  2. Give it a clear name (e.g. "Weekly Newsletter Intro").

  3. Add a description (helps teammates know when to use it).

  4. Define input fields:

    • For each input, pick a type (Text / Long text / Number / Dropdown / Date)
    • Label it clearly
    • Mark required vs optional
    • For dropdowns, list the options
  5. Write the prompt body using {{field_name}} placeholders that match your inputs. Example:

    Write a short newsletter intro for {{topic}} aimed at {{audience}}.
    Tone: {{tone}}. Keep under 100 words.
  6. Pick a default model (Claude Haiku 4.5 for speed, Sonnet for quality).

  7. Click Save.

Step 6 — Test the template

  1. Click Run on the new template.
  2. Fill in the inputs with realistic values.
  3. Inspect the output.
  4. Adjust the prompt body if the output isn't quite right.
  5. Re-test.

Step 7 — Share with the workspace

By default, your templates are private. To share:

  1. Open the template.
  2. Click Settings → Visibility.
  3. Choose Workspace (everyone in the workspace can run it) or Private (only you).
  4. Optionally pin it to Workspace favourites so it appears at the top of every teammate's list.

Step 8 — Version your changes

Templates get refined. To track:

  1. When you edit and save a template, the version bumps.
  2. Old runs still show which version they used.
  3. The version history is visible under Settings → Versions on each template.
  4. Rollback by clicking Restore on a past version.

Common pitfalls

  • Placeholder didn't get substituted. The placeholder name in the prompt body must match the input field name exactly, including case. {{Topic}} won't match an input field named topic.
  • Output is inconsistent run-to-run. Try a lower-temperature model (Claude Haiku 4.5 produces tighter, more repeatable output than Sonnet for short tasks).
  • The template feels too long to fill in. Drop optional fields. The fewer required inputs, the more often the template gets used.
  • Teammates aren't using my templates. Either they don't know about them or the names aren't discoverable. Pin to favourites and name them by outcome ("Newsletter intro") not method ("3-paragraph short copy template").

What to do next

  • Use Brand Profile-aware prompts so output matches your voice — see Brand Profile
  • For one-off ad-hoc prompts, stay in Chat rather than saving a template
  • For repeatable post generation on a schedule, pair with Content Automations