Prompt Library

Read AGENTS.md and SKILLS.md, then look at src/config/config.toml,
src/pages/[...lang]/index.astro, and src/content/sections/english/home-banner.md. Summarize in 10
bullet points how this Astro theme is organized: where text lives, how a page picks its sections,
how a named block becomes a section's content prop, which sections ignore enable: false, where
the layout options live, and which collections npm run astro-check actually validates. Don't
change any files yet.

Here is my product. Use it for every copywriting request in this conversation:
- Name: [PRODUCT NAME]
- What it does: [ONE SENTENCE]
- Who it is for: [AUDIENCE]
- Main features: [3 TO 6 FEATURES]
- Tone: short, clear, confident. No hype words.
Never invent customer names, testimonials, user counts, uptime figures, funding, or
certifications. If you need one, leave the sample value and list it for me.
Confirm with one line, and don't change any files yet.

Change the brand from "Upstart" to "[NAME]". In src/config/config.toml update [site] title,
description, tagline, and logoText, and [seo] author. Then set common.siteTagline and
common.siteDescription in every src/i18n/<language>.json, and search src/content and src/config
for any remaining "Upstart" in visible text and replace it. Don't rename files or code
identifiers.

My brand color is [HEX] and my accent color is [HEX]. In src/styles/theme.css update
--color-primary and --color-accent, and adjust --color-secondary, --color-theme-dark, and
--color-border-light to match. This is a dark theme: --color-body is near-black and
--color-text-default is light, so check that body text, muted text, and borders still reach at
least 4.5:1 contrast on the new background. Don't add arbitrary color values anywhere else. List
the values you chose.

Replace Satoshi with [GOOGLE FONT] for --font-primary in src/config/fonts.json. Satoshi's entry
has "provider": "local", so change the provider to "google" and set the right weights and
subsets. Keep Syne for --font-secondary, Instrument Serif for --font-tertiary, and the IBM Plex
Sans Arabic entry (loaded only on Arabic pages). Tell me which local font files under
src/assets/ are now unused. Don't edit any CSS file. Remind me to restart npm run dev.

I added my logo at src/assets/images/[FILE].svg. In src/config/config.toml set [site] logo to
"/images/[FILE].svg", adjust logoWidth and logoHeight to keep its proportions, set logoText to
[NAME OR ""], and tell me what logoHoverAnimation does so I can decide. Also set image under
[site.favicon] to the same file, and tell me to run npm run generate-favicons.

Rewrite the English homepage text for my product. The homepage is
src/pages/[...lang]/index.astro. Edit the section files it uses in
src/content/sections/english/ and the named blocks in src/content/homepage/english/-index.md.
Keep every key, option, icon name, image path, and the number of items in each list. Only change
text values, and keep any **bold** markers the layout relies on. Then write the french and arabic
versions, with identical keys.

On the homepage (src/pages/[...lang]/index.astro), move [SECTION] above [SECTION] and remove
[SECTION]. Only edit the route file: don't delete any content files, and remove imports that are
no longer used. Note that HomeBanner and IntegrationSection ignore enable: false, so taking them
out of the route is the only way to hide them. Then run npm run astro-check.

On [PAGE ROUTE in src/pages/[...lang]/], change [WHAT] for that page only. Add a named block to
that page's content file and pass it to the section as the content prop in the route, the way
index.astro passes faqSection and features.astro passes why-us-two.md to WhyUs. Leave the shared
section file alone. Do the same for french and arabic.

Set layoutType to "[creative | modern]" in src/content/sections/english/why-us.md and
why-us-two.md, and their french and arabic copies. For the pricing page, the layout prop of
PricingSection in src/pages/[...lang]/pricing.astro chooses "regular" or "comparison": set it to
"[VALUE]". Then run npm run astro-check.

Hide the [SECTION] everywhere. Set enable: false in src/content/sections/english/[FILE].md and in
the french and arabic copies. If it is HomeBanner or IntegrationSection, tell me instead which
route to remove it from, because those ignore enable.

In every src/config/menu.<language>.json: keep only links to the pages I use ([LIST]), and set
"enable": false on the rest in headerPrimary, footerMenuQuickLink, footerMenuResources,
footerMenuLegal, and footerMenu. Keep the JSON shape, the weight values (Navbar sorts by them),
and the same items in every language. Then check the header on desktop, with the keyboard, and in
the mobile menu.

Turn the "[MENU NAME]" item in headerPrimary into a mega menu in every
src/config/menu.<language>.json. Use hasMegaMenu: true with menus as groups of
{ enable, name, description, icon, url, weight }, following the shape documented in AGENTS.md
under "Menus and Mega Menu". Each icon is an SVG path such as /images/icons/svg/focus.svg, and
only the mobile menu shows the icons. Add the cta card with [DETAILS] and the bottom bar with
[TEXT, LABEL, URL]; the bar also shows the contact details from [settings.contactInfo].

Create a page at /[slug]/ with these sections: [WhyUs, Customers, TestimonialSection,
CallToAction]. Follow the "Add a new page" skill in SKILLS.md: copy src/pages/[...lang]/
features.astro, keep its getStaticPaths, and compose it from the section components, passing
headingTag="h1" to the section that opens the page. Put the page's own copy in a new content file
and pass it with the content prop where a section needs page-specific values. Add "[slug]" to
headerPrimary in every src/config/menu.<language>.json, then run npm run astro-check.

I don't need these pages: [LIST, for example /changelog/, /integration/, /faq/]. For each one,
delete its route file or folder in src/pages/[...lang]/ and its content folder in src/content/,
remove it from src/lib/utils/aiContent.ts if it is listed there, then remove every link to it
from each src/config/menu.<language>.json and from content files (search for the URL). Run
npm run astro-check and npm run build, and fix anything they report.

I only need English. Set enable = false under [settings.multilingual] in src/config/config.toml.
Don't delete any files yet. Then tell me exactly what npm run toml:watch and
npm run remove-multilingual would do, and which lines I should remove from netlify.toml.

Add [LANGUAGE] (code "[xx]", folder "[name]", locale "[xx-XX]", social locale "[xx_XX]") and keep
the other languages. Follow the "Add or remove a language" skill in SKILLS.md: run
npm run toml:watch first (the language scripts need the generated config), then
npm run generate-multilingual-content with those values, and add a /[xx]/* block to
netlify.toml. Add a font entry to src/config/fonts.json if the script needs its own font. Then
translate the copied content folders, src/config/menu.[xx].json, and src/i18n/[xx].json, keeping
every key, icon name, URL, number, and MDX shortcode tag.

The [Arabic | French] content is machine translated. Review src/content/[FOLDER]/
[arabic | french] and src/i18n/[ar | fr].json and rewrite the text so it reads naturally for a SaaS
audience. Keep every key, number, URL, icon name, and MDX shortcode tag exactly as it is, and
don't change the English files. For Arabic, keep numbers, emails, and URLs left to right.

Connect the contact form to [Formspree with form ID xxxx | formsubmit.co with [EMAIL] | Netlify
Forms]. Update contactFormAction and contactFormProvider in src/config/config.toml, following the
comment next to them. Don't change the form fields.

The contact form should ask for: [LIST OF FIELDS]. Edit form.inputs in
src/content/sections/english/contact-section.md, and make the same change in the french and
arabic copies. Don't write new form markup and don't edit ContactSection.astro; validation and
sending stay in src/lib/utils/FormHandle.ts. Keep the existing field shape and required flags.

For each page's -index.md in src/content/*/english/ and each file in src/content/pages/english/,
write a metaDescription of 140-160 characters based on that page's real content. Only add or
change metaDescription. Then do the french and arabic versions.

Review this site before launch and list what is still demo content. Check: baseUrl in [site] in
src/config/config.toml (it ships as a pages.dev URL), contactFormAction, formAction under
[settings.subscription], [settings.contactInfo], the contact details in
src/content/sections/*/contact-section.md, social links in src/config/social.json, every price
and the comparison block in src/content/sections/*/pricing-section.md, the sample integrations in
src/content/integration/, the sample quotes in src/content/sections/*/testimonial.md, the
changelog entries, the legal pages in src/content/pages/, any "#" or example.com links in the
menus and content, and any remaining "Upstart" in visible text. Don't change files: list the file
and the line for each item.

npm run [dev | build | astro-check] fails with this error:
[PASTE THE FULL ERROR]
Explain the cause in one sentence, then fix it with the smallest change. Don't change unrelated
files.

I changed [WHAT] in [FILE] but the page [URL] still shows the old version. Find where that page
gets this text: check the route in src/pages/[...lang]/, the named block it passes as the content
prop, and the section file in src/content/sections/english/. Remember that FaqSection.astro reads
src/content/faq/<language>/-index.md instead of a section file. Tell me which one wins and why.
Don't change anything yet.

On [PAGE] at /ar/, [WHAT LOOKS WRONG]. Follow the RTL Rules in AGENTS.md: replace physical
classes with logical ones, add rtl: handling for translate-x, transform origins, and gradients,
and add any direction-bearing icon to the rtlFlipIcons list in
src/layouts/helpers/Icons.astro rather than at the call site. Then tell me what to check at /ar/.