Skip to content
New: Customize your theme with an AI assistant. Read the guide

Prompt Library

Skill level: Beginner

Copy a prompt, replace the parts in [BRACKETS], and send it to your assistant. Each prompt names the Givo files involved, so it works in AI editors and, with the files pasted in, in chat assistants too.

Get Started

Explain the project to the assistant

Read AGENTS.md and SKILLS.md, then look at src/config/config.toml, src/pages/[...lang]/index.astro,
src/content/homepage/english/-index.md, src/content/donate/english/-index.md, and
src/content/sections/english/hero-section.md. Summarize in 10 bullet points how this Astro
theme is organized: where text lives, where the organization details, causes, and donation
amounts live, how pages pick their sections, how a page overrides a section (named blocks), and
how options.layout works. Don't change any files yet.

Describe your organization once, then reuse it

Here is my organization. Use it for every copywriting request in this conversation:
- Name: [ORGANIZATION NAME]
- What we do: [PROGRAMS, e.g. FOOD BANK, HOMEWORK CLUB, WINTER SHELTER]
- Where we work: [TOWNS, REGIONS, OR COUNTRIES]
- Who we help: [PEOPLE AND COMMUNITIES]
- Facts you may use: [YEAR FOUNDED, REGISTRATION NUMBER, PEOPLE REACHED LAST YEAR, SHARE SPENT ON PROGRAMS]
- Tone: short, plain, warm. No hype words, no guilt.
Never invent goals, amounts raised, donor counts, quotes, beneficiary stories, statistics, or
registration numbers. Confirm with one line, and don't change any files yet.

Organization Details And Brand

Rename the organization and update the contact details everywhere

My organization is "[NAME]", registered as "[LEGAL NAME]" with number [REGISTRATION NUMBER],
phone [PHONE AS DIALED, e.g. +15551234567] shown as "[PHONE AS WRITTEN]", email [EMAIL].
In src/config/config.toml:
- [organization]: set legalName, registrationNumber, phone (E.164: + country code, digits
only), phoneDisplay, and email. Set nonprofitStatus to [OUR STATUS, or "" if unsure].
- [site]: set title and logoText to my name.
Then rewrite seo.tagline and seo.siteDescription in every src/i18n/<language>.json for my
organization. Search src/content and src/i18n (every language) for "Givo" in visible text and
list it. Don't rename files, ids, or code identifiers. List every file you changed.

Set the address and office hours

In [organization] of src/config/config.toml, set the address to [STREET, CITY, STATE OR
PROVINCE, POSTAL CODE, COUNTRY CODE] and timezone to "[IANA ZONE, e.g. Europe/London]".
[We have no public office: set [organization.address] show = false.] Set [organization.hours]
to: [DAYS AND TIMES], in 24-hour "HH:MM-HH:MM" format, with "" for closed days. Set
closedDates to these days: [DATES YYYY-MM-DD]. Remove the "# sample" comments on the values
you changed.

Apply my brand colors

My brand colors are: main [HEX], highlight [HEX]. In src/styles/theme.css, in the :root block,
set --theme-primary and --theme-accent (buttons, links, progress bars, with white text from
--theme-on-primary) to a shade of my main color with at least 4.5:1 contrast against white
labels and on the page background. Update the hover shades and the matching --page-primary
values. Set --theme-gold (the donation panel and small marks, with --theme-on-gold text) to my
highlight color, keeping at least 4.5:1 with --theme-on-gold. In :root.dark, set versions that
read on the dark page background. Keep every variable name. Tell me the values you chose and
their contrast ratios.

Change the fonts

Replace Urbanist with [GOOGLE FONT]. Edit src/config/fonts.json only: keep the cssVariable
"--font-primary", keep the weight range "400 700", and keep the fallback. Leave Readex Pro
(--font-arabic, Arabic pages) and JetBrains Mono (--font-code). [For a separate heading font,
add a --font-heading entry to fonts.json and remove the --font-heading line in
src/styles/theme.css.] Then tell me to restart npm run dev.

Use my logo

I put my logo at public/images/[FILE].svg. In [site] of src/config/config.toml set
logo = "/images/[FILE].svg" and logoWidth / logoHeight so it is about 28px tall with its own
proportions. Then set [site.favicon] image to "/images/[SQUARE MARK FILE]" and tell me to run
npm run generate-favicons and npm run generate-og-image.

Causes And Donations

Replace the sample causes with mine

Our causes are: [TITLE, CATEGORY, GOAL, AMOUNT RAISED SO FAR, NUMBER OF DONORS, DEADLINE OR
"ONGOING", ONE-PARAGRAPH SUMMARY; ...]. Follow the "Add a cause" recipe in SKILLS.md. For each
one, copy a file in src/content/causes/english/ to a new file named after the cause (the file
name is the URL) and set title, description, category (an id from categories: in -index.md),
goal, raised, donors, and deadline (remove deadline for an ongoing cause). Keep the image paths
and tell me which photos to replace. Leave impact, updates, and gallery as they are and list
them for me to rewrite. Add the same entries, translated, with the same numbers, in every other
language folder. Set draft: true on the sample causes I don't keep. Then update the Causes mega
menu in every src/config/menu.<language>.json (one group per category), point cta.cause at
[CAUSE FILE NAME], and update the causes: list in causesSection and the cause: id in
heroSection of every src/content/homepage/<language>/-index.md.

Update the amount raised

New totals: [CAUSE FILE NAME: RAISED, DONORS; ...]. Set raised and donors in each of these
files in src/content/causes/, in every language folder, with the same numbers. Change nothing
else. Then remind me to rebuild and deploy the site.

Change the currency and the preset amounts

We take donations in [CURRENCY, e.g. EUR]. In src/content/donate/english/-index.md set currency
to "[ISO CODE]", amounts.oneTime to [AMOUNTS], amounts.monthly to [AMOUNTS], default.oneTime to
[N], default.monthly to [N], and minimum to [N]. Copy exactly the same numbers into the donate
file of every other language. Then search src/content (every language) for amounts typed as
text with a "$" or "dollar" (in descriptions, cause impact lines, tiers, events, stories, and
the impact page) and list them for me without changing them.

Write what each amount pays for

Here is what our gifts pay for: [AMOUNT: OUTCOME; AMOUNT: OUTCOME; ...]. In
src/content/donate/english/-index.md replace the impactMap list with these, sorted from the
smallest amount up (the receipt shows the outcome of the closest lower amount). Write each
label so it reads after "$50 pays for". Do the same in every other language, translated, with
the same amounts. Don't invent outcomes I didn't give you.

Change the monthly giving tiers

Our monthly tiers are: [NAME, AMOUNT, ONE-LINE DESCRIPTION, BENEFITS; ...]. Replace the tiers
list in src/content/donate/english/-index.md with these (name, amount, description, features).
Do the same in every other language, translated, with the same amounts. Only promise benefits I
listed.

Connect the donation form

[Option A] Our payment provider gave us this form URL: [URL]. In the form block of every
src/content/donate/<language>/-index.md set mode: "form", endpoint to that URL, and method to
"[post | get]".
[Option B] We use a hosted checkout page: [URL]. In the form block of every
src/content/donate/<language>/-index.md set mode: "redirect" and processorUrl to that URL, with
{amount}, {frequency}, and {cause} where the page expects them: [HOW OUR PROVIDER NAMES THESE
PARAMETERS].
Keep thanksUrl. Then tell me how to make a small test donation.

Turn off the cover-the-fees line or the tribute option

[We don't want the "cover the fees" line: set coverFeesPercent: 0 in every
src/content/donate/<language>/-index.md.] [We don't offer gifts in honor or in memory: remove
the tribute block under form: in every src/content/sections/<language>/donate-section.md, and
tell me where the /tribute/ page is linked from, so I can remove those links too.]

Events, Volunteering, And Impact

Add an event

Add an event: [TITLE, DATE, START AND END TIME, VENUE AND ADDRESS or "ONLINE", CAPACITY, PRICE
(0 = FREE), SIGN-UP LINK, CATEGORY, SHORT DESCRIPTION]. Follow the "Add an event" recipe in
SKILLS.md: copy a file in src/content/events/english/ to [slug].md and set the frontmatter.
Times are local wall-clock times; leave timezone empty if the event is in the time zone of
[organization]. Keep the image path and tell me which photo to replace. Add the translated
entry, with the same dates and numbers, in every other language folder. Then tell me the URL
of its add to calendar file.

Update the volunteer roles

Our volunteer roles are: [ROLE, WHAT YOU DO, WHERE, TIME COMMITMENT, SKILLS; ...]. Replace the
roles list in volunteerRolesSection of src/content/pages/english/volunteer.md with these,
following the existing keys (each role keeps an id, which the sign-up form uses). Do the same
in every other language with the same ids. Then check that the volunteer form's role choices
come from this list.

Update the impact page and the spending split

Our figures for [YEAR] are: total spending [AMOUNT]; programs [N]%, fundraising [N]%, running
costs [N]%; people reached [N]; [OTHER FIGURES]. Update figures and spend in
src/content/impact/english/-index.md. Then make the same split appear in giftSplitSection.items
of src/content/homepage/english/-index.md and in the spendSplit description of
src/content/donate/english/-index.md. Do the same in every other language. Remove "# sample" on
values I gave you, and list every sample value still left on /impact/.

Homepage And Layouts

Change a section’s layout

On [PAGE URL], switch the [SECTION] to the [LAYOUT] layout. Find the page's content file and
its named block for that section (or the section file in src/content/sections/english/ if the
page has no block), and set options.layout. Use only a value listed in the comment next to
layout:. Do the same in the other language folders.

Reorder or remove homepage sections

On the main homepage (src/pages/[...lang]/index.astro), move the [SECTION] line above the
[SECTION] line inside <Base> and remove the [SECTION] line. Keep the
<LayoutVariants section="..." content={...} /> wrapper on the sections that use it. Only edit
the route file; don't delete content files.

Use another homepage as the main one

I want the /home-[appeal | community]/ design as my main homepage. Replace the page body of
src/pages/[...lang]/index.astro with that of home-[NAME].astro, reading the "-index" entry
instead of "home-[NAME]". Copy all frontmatter of src/content/homepage/english/home-[NAME].md
into -index.md (same for the other language folders), and remove robots and
excludeFromSitemap there. Then delete the homepage routes and content files I don't use and
remove their links from the Pages menu in each src/config/menu.<language>.json. Run
npm run astro-check.

Change the header and footer layout

Set the site header to [default | centered | utility] and the footer to [default | minimal |
large] in [settings.layout] of src/config/config.toml. Then list every page file that sets its
own headerLayout or footerLayout in frontmatter, so I can decide whether to keep them.

Turn on the announcement bar for an appeal

Show an announcement above the header on every page: "[TEXT]" with a link "[LABEL]" to [URL].
Edit announcement-bar.md in every language folder of src/content/sections/: set enable: true,
rewrite label, text, and link, set end to [YYYY-MM-DD], and set a new id (so visitors who
closed the old message see the new one). Keep hideOn and tone.

Content

Clean up the menus

In each src/config/menu.<language>.json: set "enable": false on the "Pages" header item (it
lists every demo page), and make the footer columns link only to pages I keep: [LIST]. Keep the
Legal column last. Keep the same structure in every file, then run npm run check-i18n.

Turn off one language

I don't need [LANGUAGE] yet. Add its code to disableLanguages in [settings.multilingual] of
src/config/config.toml, and tell me to restart npm run dev. Keep its files.

Keep only English

I only need English. In [settings.multilingual] of src/config/config.toml set enable = false.
Tell me to run npm run dev once, then npm run remove-multilingual, which deletes the content
folders, menu files, and i18n files of every other language. Before that, list any translated
text I might want to keep, and save a git commit.

Check the site before launch

Prepare my site for launch. In src/config/config.toml: set [site] baseUrl to "[URL]", check
that contactFormAction and the Mailchimp formAction are no longer placeholders, and keep
[settings.layoutSwitcher] enable = false. Check that the form block of every
src/content/donate/<language>/-index.md has an endpoint or a processorUrl. Then search
src/content, src/config, and src/i18n for "# sample", "PLACEHOLDER", "example.com",
"example.org", and "555" and list every value I still have to replace, grouped by file. Don't
change them. Finally run npm run build and report the warnings.

Fix an error

npm run [dev | build | astro-check] shows this error: [PASTE THE WHOLE ERROR]. Find the cause,
explain it in one sentence, and fix it in the content or config file, not in a component.
Type something to search...