> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pagifye.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Starter Prompts for Pagifye MCP

> Four ready-to-use prompts for your first tests with Pagifye MCP: check your connection, compare sections, build one section, then build a landing page.

Use these four Pagifye MCP prompts in order, in the same chat. Replace the parts in \[square brackets] with your own details. The first two don't use any copies. In ChatGPT, type `@` and choose **Pagifye** first.

## 1. Check Your Connection

Check your Pagifye connection

Use Pagifye to check my connection. Tell me which team and plan I'm connected to, how many copies my team has left and when they reset, and which component libraries I can use, with the kinds of sections each one has.

## 2. Compare Sections

Compare hero sections

Use Pagifye to find hero sections for \[a project management app for small agencies].

* Search one library, light variant.
* Look at the previews of the 3 best matches and number them 1 to 3.
* Describe each layout in one sentence and say which suits my product best.

Wait for me to choose one before you build anything.

## 3. Build One Section

Uses one copy.

> [tab] Claude or ChatGPT
>
> Build a section as an HTML page
>
> Build option \[2] as one HTML file that I can open in my browser.
>
> * Use its Pagifye Tailwind code and keep its layout, spacing and colors.
> * Set up Tailwind with Pagifye's theme colors, font and Alpine.js, following Pagifye's Tailwind setup guide. If you can't open the guide, tell me before you build.
> * Replace the placeholder text with copy for \[my product: what it does and who it's for].

> [tab] Code tools
>
> Add a section to your project
>
> Add option \[2] to \[index.html], right below the navbar.
>
> * Use its Pagifye Tailwind code and keep its layout, spacing and colors.
> * If my project isn't set up for Pagifye yet, add Pagifye's theme colors, font and Alpine.js, following Pagifye's Tailwind setup guide. If you can't open the guide, tell me before you build.
> * Replace the placeholder text with copy for \[my product: what it does and who it's for].

## 4. Build a Landing Page

Uses one copy per section, about eight in total. Your AI checks your copies before it builds.

Build a landing page

Build a landing page for \[product name], \[one sentence: what it does and who it's for], using Pagifye components.

* Use one Pagifye library and the light variant for every section.
* Sections, in order: navbar, hero, features, testimonials, pricing, FAQ, call to action, footer.
* First, list the component you chose for each section with a one-line description, how many copies building will use and how many my team has left. Wait for my OK.
* Then build it \[as one HTML file I can open in my browser] or \[in index.html]. Set up Pagifye's theme colors, font and Alpine.js from Pagifye's Tailwind setup guide. If you can't open the guide, tell me before you build.
* Replace all placeholder text with copy for my product.

## Tips

* **Mention Pagifye** so your AI knows which tool to use.
* **Say what you're building and who it's for**, so your AI picks better sections and writes better copy.
* **Keep one library and one variant** (light, gray or dark) across a page so the sections match.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.