# Prompt Library
## Prompt Library
**Skill level:** Beginner
Copy a prompt, replace the parts in `[BRACKETS]`, and send it to your assistant. Each prompt names the Techlo files involved, so it works in AI editors and, with the file pasted in, in chat assistants too.
### Get Started
**Explain the project to the assistant**
```text
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.
```
**Describe your company once, then reuse it**
```text
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.
```
### Brand
**Rename the site**
```text
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/.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.
```
**Apply brand colors**
```text
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.
```
**Change the fonts**
```text
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.
```
**Use my logo**
```text
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.
```
### Homepages, Headers, And Sections
**Pick one homepage and drop the others**
```text
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..json. Run
npm run astro-check.
```
**Rewrite the homepage for my company**
```text
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.
```
**Reorder or remove homepage sections**
```text
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.
```
**Change a section on one page only**
```text
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.
```
**Switch a section layout**
```text
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.
```
**Change the header or footer background on a page**
```text
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 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.
```
### Content
**Rewrite the services**
```text
My services are: [LIST]. Rewrite the entries in src/content/services/english/, following the
frontmatter of service-01.mdx (title, customSlug, description, date, icon) and replacing the body
text of each one. The icon can be a Lucide name or a local SVG path, as the comments in that file
explain. Keep every key, keep customSlug the same in every language, and use paths that already
exist. Mark entries I don't need as draft: true. Then update
src/content/sections/english/services-section.md so the section text matches, and do the french
and arabic folders.
```
**Replace the projects with my work**
```text
Replace the sample projects with mine: [FOR EACH: TITLE, CLIENT (only if I may name them), YEAR,
WHAT WE BUILT, THE OUTCOME I CAN BACK UP]. The entries are the files in
src/content/projects/english/. Follow the frontmatter of 01.mdx and keep every key, with the same
customSlug in every language. Use only the outcomes I gave you: do not invent percentages or
figures. Tell me which image files to add. Mark entries I don't need as draft: true. Then add the
french and arabic versions.
```
**Write the team**
```text
Replace the sample team in src/content/team/english/ with: [FOR EACH PERSON: NAME, ROLE, SHORT
BIO, SOCIAL LINKS]. Follow the frontmatter of team-1.md and keep every key, with the same
customSlug in every language where it is set. Use image paths under /images/team/ and tell me
which image files to add. Mark the entries I don't need as draft: true, and update
src/content/sections/english/team-section.md so the section text matches. Then do the french and
arabic versions.
```
**Write testimonials**
```text
Here are my real client quotes: [FOR EACH: QUOTE, NAME, ROLE, COMPANY]. Put them in
src/content/testimonials/english/-index.md and in
src/content/sections/english/testimonial.md. Use only the quotes I gave you, keep the file
structure, and if I gave fewer than the sample has, reduce the list rather than inventing more.
Then do french and arabic.
```
**Write the FAQ**
```text
Replace the questions in src/content/faq/english/-index.md and
src/content/sections/english/faq-section.md with 10 questions a client would ask an IT services
company, with short, direct answers. Keep the structure and keys. Then translate them into the
french and arabic versions.
```
**Write pricing packages**
```text
Update the packages in src/content/sections/english/pricing-section.md to: [PACKAGE NAME, PRICE,
3-6 ITEMS INCLUDED for each]. Keep the file's structure, the button shape, and the options
documented in the comments, and mark [PACKAGE] as the featured one. Then copy the same figures
into the french and arabic versions and translate only the text.
```
**Write a blog post**
```text
Write a blog post titled "[TITLE]" about [TOPIC], around 800 words. Create
src/content/blog/english/[slug].mdx with the same frontmatter fields as the other posts in that
folder. Use an existing image path and an existing author from src/content/author/english/. Use
## headings, and the MDX shortcodes from src/lib/shortcodes.ts where they help. Add the french
and arabic versions.
```
**Set your business details**
```text
My details are: address [ADDRESS], phone [PHONE], email [EMAIL], office hours [HOURS]. Techlo
keeps contact details in three places: [settings.contactInfo] in src/config/config.toml,
src/content/contact//-index.md, and
src/content/sections//contact-section-two.md. Update all three, in every language, and
list what you changed in each. Also update contactInfo in every src/i18n/.json and the
social links in src/config/social.json ([LIST OF URLS]), setting "enable": false on the networks
I don't use.
```
**Add a legal or text page**
```text
Add a page at /[slug]/ titled "[TITLE]" with this content: [TEXT]. Create
src/content/pages/english/[slug].md like src/content/pages/english/terms-conditions.md, and the
french and arabic versions. [page].astro renders it, so no route file is needed. Add it to a
footer column in every src/config/menu..json.
```
### Navigation And Pages
**Clean up the menus**
```text
In every src/config/menu..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.
```
**Edit the Services mega menu**
```text
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..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.
```
**Add a page made of existing sections**
```text
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..json, then run npm run astro-check.
```
**Remove pages I don't need**
```text
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..json and from content files (search for the URL). Run
npm run astro-check and npm run build, and fix anything they report.
```
### Languages
**Use English only**
```text
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 a language**
```text
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.
```
**Improve the Arabic or French translation**
```text
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.
```
### Forms, SEO, And Launch
**Connect the contact form**
```text
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.
```
**Change the contact form fields**
```text
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.
```
**Add a newsletter form**
```text
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/.json in every language. Then
run npm run astro-check and tell me what to test.
```
**Write SEO descriptions**
```text
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.
```
**Pre-launch review**
```text
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/.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.
```
### Fix Problems
**Explain and fix an error**
```text
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.
```
**A change doesn't show up**
```text
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.
```
**Fix the Arabic layout**
```text
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/.
```