Prompt Library

Read AGENTS.md and SKILLS.md, then look at src/config/config.toml,
src/pages/[...lang]/index.astro, src/content/homepage/english/-index.md, and
src/content/sections/english/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 in a page's
frontmatter overrides a section, how options.layout works and when a homepage route's content
prop wins over it, how a page picks its header layout and position, and which collections
npm run astro-check actually validates. Don't change any files yet.

Here is my company. Use it for every copywriting request in this conversation:
- Name: [COMPANY NAME]
- What we do: [ONE SENTENCE]
- Who it is for: [AUDIENCE]
- Services: [3 TO 6 SERVICES]
- Tone: direct, technical, no buzzwords.
Never invent client names, testimonials, project results, certifications, partner badges, uptime
figures, or prices. 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 "Techlo" to "[NAME]". In src/config/config.toml update [site] title,
description, tagline, and logoText, and [seo] author. Then check `site` in every
src/i18n/<language>.json, and search src/content and src/config for any remaining "Techlo" 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-primary-soft, --color-theme-dark,
--color-theme-light, and --color-dark to match. Keep at least 4.5:1 contrast for text on
--color-body and on --color-theme-dark. Don't add arbitrary color values anywhere else, and don't
touch the typography tokens. List the values you chose.

Replace Sora with [GOOGLE FONT] for --font-primary in src/config/fonts.json. Keep the cssVariable
name, the weights, the fallback, and the IBM Plex Sans Arabic entry (it is loaded only on Arabic
pages). 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", set logoAlternate if I have a light version, adjust logoWidth and
logoHeight to keep its proportions, and set logoText to [NAME OR ""]. Also set image under
[site.favicon] to the main file, and tell me to run npm run generate-favicons.

I want the [second | third] homepage as my main homepage. Replace the sections of
src/pages/[...lang]/index.astro with the ones in src/pages/[...lang]/home-[two | three].astro,
and copy the frontmatter of src/content/homepage/english/home-[two | three].md into
src/content/homepage/english/-index.md (same for french and arabic). Keep the headerLayout and
headerPosition props that route uses. Then delete the other homepage routes and their content
files, and remove them from the Home menu in every src/config/menu.<language>.json. Run
npm run astro-check.

Rewrite the English homepage text for my company. The homepage is
src/pages/[...lang]/index.astro. Edit the named blocks in
src/content/homepage/english/-index.md and the section files it uses in
src/content/sections/english/. Keep every key, option, icon name, image path, and the number of
items in each list. Only change text values. 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. Then run npm run astro-check.

On [PAGE, for example /about/], change [WHAT] for that page only. Add or edit the matching named
block in that page's frontmatter in src/content/[about-us | pricing | faq | contact]/english/
-index.md, using a block name that exists in src/sections.schema.ts. Leave the file in
src/content/sections/english/ alone so other pages keep the current text. Do the same for french
and arabic.

Change the [services | projects | team | blog | testimonials] section to the "[VALUE]" layout.
Set options.layout in the matching file in src/content/sections/english/, using a value from the
comment next to it, and make the same change in the french and arabic copies. If the homepage
route passes a layout through that section's content prop, change it there too, because the route
wins. Then run npm run astro-check.

On [PAGE ROUTE in src/pages/[...lang]/], use headerLayout "[one | two | three]" and
headerPosition "[fixed | static | sticky]", and [a dark | a light] footer background. Set
headerLayout, headerPosition, and hasFooterDarkBackground on <Base> in that route file only.
Note that header layout three has no language switcher, so don't use it if I keep more than one
language.

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 and in the footer columns. Keep the JSON shape, the
weight values, and the same items in every language. Then check the header on desktop, with the
keyboard, and in the mobile menu.

The Services mega menu in headerPrimary should list these services: [LIST, with a one-line
description and an icon for each]. Update it in every src/config/menu.<language>.json, keeping
the hasMegaMenu shape documented in AGENTS.md under "Menus and Mega Menu" ({ enable, name,
description, icon, url, weight } inside menus). Update the cta card with [DETAILS] and the bottom
bar with [TEXT, LABEL, URL], or set their enable to false.

Create a page at /[slug]/ with these sections: [AboutSection, Features, StatsSection,
CallToAction]. Follow the "Add a new page" skill in SKILLS.md: copy src/pages/[...lang]/about.astro,
keep its getStaticPaths, and compose it from the section components. Put the page's own copy in
named blocks in a new content file, using block names from src/sections.schema.ts. 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 /projects/, /faq/, /testimonials/]. 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 generate-multilingual-content with that code, add a /[xx]/* block to netlify.toml, and
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 customSlug.

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 technical
audience. Keep every key, number, URL, icon name, and customSlug 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
comments next to them. Don't change the form fields.

The contact form should ask for: [LIST OF FIELDS]. Edit the form block in
src/content/sections/english/contact-section.md, which every contact form shares, and make the
same change in the french and arabic copies. If contact-section-two.md has its own form block,
update that too. Follow inputFieldSchema in src/sections.schema.ts, don't edit
widgets/ContactForm.astro, and keep the required flags.

No page renders a newsletter form today. Add widgets/SubscriptionForm.astro to the footer, set
formAction under [settings.subscription] in src/config/config.toml to [MY MAILCHIMP URL], and
make sure its labels come from subscription in src/i18n/<language>.json in every language. Then
run npm run astro-check and tell me what to test.

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 https://example.com and the build warns about it),
contactFormAction, [settings.contactInfo], src/content/contact/*/-index.md,
src/content/sections/*/contact-section-two.md, contactInfo in every src/i18n/<language>.json,
social links in src/config/social.json, every price in
src/content/sections/*/pricing-section.md, the sample projects in src/content/projects/, the
sample team in src/content/team/, the sample quotes in src/content/testimonials/, the legal pages
in src/content/pages/, any "#" or example.com links in the menus and content, and any remaining
"Techlo" 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 named block in the page's frontmatter, whether that block name is a key
of sectionsSchema in src/sections.schema.ts, the content prop the route passes to the section,
and the section file in src/content/sections/english/. Remember that older components read
differently named files (Features.astro reads features.md). 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/.