How to share one landing page skill with your team's AI

Why each AI makes a different page

Ask five AIs for a landing page and you get five guesses: one leads with the company, one adds a second button, one asks for a phone number, one writes "the #1 choice" with nothing behind it. None of them knows the team's rules unless someone tells it, every time. A team skill tells it once. Each person's AI loads the same instructions when someone asks for a page, so the order, button and form come out the same whoever asked.

What the skill holds

The skill to copy

Copy this into a file named SKILL.md, or paste it where your team keeps skills, and fill in the brackets. Until a line is filled, the AI follows the default after it. This is the core of the library skill; the full version adds when to use it, a worked example and the checks.

---
name: landing-page-house-style
description: Builds a landing page or campaign page the team's house way, whoever's AI makes it - the brand voice and words to avoid, a fixed section order, one call to action with fixed wording, only the form fields the team allows, every claim that needs a source flagged, alt text on every image, readable contrast - and returns a preview, never publishing unless the person asks. Use when someone asks an AI to make, draft or update a landing page, campaign page, sign-up page or event page for the team.
---

# Landing page house style

## Our house style

Fill these in once for the team. Until a line is filled, follow the default after it.

- **Voice:** [3 traits, "this, not that"]. Default: plain, specific, no hype.
- **Words we avoid:** [list]. Default: "revolutionary", "world-class", "next-generation", "effortless".
- **Section order:** [list]. Default: headline and one-line promise with the button; the problem in the reader's words; how it works in 3 steps; proof; what it costs or what they get; 3 to 5 questions; the button again.
- **The one call to action:** [wording, such as "Book a 20-minute demo"]. Default: a verb and what happens next.
- **Form fields we ask:** [list]. Default: name and work email. **Never ask:** [list]. Default: date of birth, home address, anything the reply doesn't need.
- **Proof we hold:** [the numbers, customer quotes with permission, and logos we may use, each with its source].
- **Who approves publishing:** [name or role].

## Steps

1. **Read the brief against the house style.** Note the one action, and check it matches "The one call to action". If the brief asks for a second button, keep one and list the other as a text link.
2. **Write in the house voice.** Use "Voice" and drop every word on "Words we avoid". Lead the headline with what the reader gets, not with the company.
3. **Build the sections in the house order.** Keep the order even when a section is short. Leave out a section only when the brief has nothing true to put in it, and say so.
4. **Use the one call to action everywhere.** Same words on every button. One primary button style on the page.
5. **Build the form from the house list.** Only the fields in "Form fields we ask"; nothing from "Never ask". Label every field, mark optional ones "(optional)", and say under the button what happens next and how the data is used, with a link to the privacy policy. If the form also signs people up for email, say so beside the button and don't pre-tick it.
6. **Flag every claim that needs a source.** Numbers, comparisons ("fastest", "#1"), results, testimonials, "free", guarantees: keep them only if they're in "Proof we hold" or the brief, and mark the rest "[source needed: what]". Never invent a statistic, quote, logo or review. Run marketing-claims-check on the page before it's published.
7. **Write alt text.** Every image that carries meaning gets alt text saying what it shows and why it's there; decorative images get an empty alt. No text that exists only inside an image.
8. **Check accessibility.** Text contrast at least 4.5:1, or 3:1 for large text, as WCAG 2.2 sets for level AA; headings in order; every field has a label; link and button text says where it goes.
9. **Preview, don't publish.** Return the page as a preview (the host's private preview link, or the HTML file) with the checklist below. Publish, or replace a live page, only when the person asks to publish in this conversation.

## Output format

**Page:** [title] · **Status:** preview only, not published

[The page: sections in the house order, or the HTML]

**Before you publish**
- Call to action: "[wording]" on [n] buttons
- Form: [fields] · never asked: [list]
- Claims needing a source: [list, or "none"]
- Images: [n] with alt text, [n] decorative
- Contrast: [checked / to check]
- Preview: [link or file] · Publish when [approver] says so

Share it with the team in AI Skill Pod

Put the skill in AI Skill Pod and everyone on the team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise), from one invite link and free to start: Free covers up to 3 members.

1. Add the skill. In the app, click Add a skill, then Pick from the library, open Landing page house style and add it to your team's pod. On Team, write your filled-in "Our house style" lines in Our team's additions and click Save our additions: your AI reads them right after the official instructions, which keep updating. On Free, choose Paste a doc or prompt instead, paste the text above with your blanks filled in, click Turn into a skill, check it and click Save for the team.
2. Invite the team. Under Invite your team, send the link. Any email address works, contractors included.
3. Everyone connects their own AI. In Claude, add the pod as a custom connector (on Team and Enterprise, an Owner adds it and each member connects), or download the SKILL.md from the skill's page and upload it as a skill. In Cursor, click Add to Cursor under Connect your AI. In ChatGPT, the pod works as a custom connector on Pro, Business or Enterprise; on Business and Enterprise, an admin or owner adds it first.
4. Change it in one place. When a rule changes, such as a new button wording, edit the skill in the pod. Everyone connected gets the new version the next time their AI uses it, and each save is kept as a version (opening earlier versions starts on Team). A SKILL.md uploaded to Claude doesn't update itself, so upload it again.

AI Skill Pod is this site's product. Pod pricing: Free up to 3 members and 10 skills; Team $5 per seat a month from 3 seats.

Where the page goes

The skill works whatever hosts the page. If your host has a connector your AI can use, the AI hands it the page and gets a preview back; if not, the AI returns an HTML file for you to upload. Convika is one host that works this way: by its own description, its MCP connector takes the page, returns a private preview link, and publishes only when the person asks. Convika is made by the same team as AI Skill Pod. Whichever host you use, the skill ends the same way: a preview, the checklist, and publishing on request.

A worked example: four people, one spring page

Illustration: a made-up business. Northfield Bikes has three shops and four people who make pages: the owner in ChatGPT Business, two shop managers in Claude, and a freelance designer on her own Claude Pro account. Last spring their pages came out with three different buttons, and one form asked for a phone number. This year the owner filled in the house style once and shared it through the pod: voice "friendly, not cute; specific, not technical"; avoid "ultimate" and "best in town"; call to action "Book a tune-up"; form fields name, email and preferred shop; never ask phone number or date of birth; proof held, "4.8 stars from 312 Google reviews" (Google Business Profile, 1 November). The shop's button colour is its light green, #66BB6A, with #2E7D32 as the dark green.

The designer asked her AI for the spring tune-up page. Her brief: a free safety check with every tune-up booked from 1 to 30 April, and a hero photo of a mechanic at work. Her AI's first draft added "Trusted by 12,000 riders", "the best service in town", a phone field and a second button, "Shop new bikes". The skill sent back:

Page: Spring tune-up · Status: preview only, not published

Headline: Get your bike ready for spring in one visit
Promise: Book a tune-up in April and get a free safety check on brakes, tyres and lights.
[Button: Book a tune-up]
...
Proof: 4.8 stars from 312 Google reviews.
Form: Name · Email · Preferred shop
Under the button: We'll email you to confirm the time, and use your details only for this booking. Privacy policy.

Before you publish
- Call to action: "Book a tune-up" on 2 buttons; "Shop new bikes" is now a text link
- Form: name, email, preferred shop · never asked: phone number, date of birth (the draft's phone field removed)
- Claims needing a source: "Trusted by 12,000 riders" [source needed: count of riders]; "the best service in town" removed (no source); "free safety check" kept (in the brief, with the April dates beside it)
- Images: 1 with alt text ("A mechanic adjusting the brakes on a road bike"), 0 decorative
- Contrast: white on the light green is 2.4:1, so the button uses the dark green #2E7D32 (5.1:1)
- Preview: private preview link · Publish when the owner says so

The designer cut the riders line rather than hunt for a number, and the owner approved the preview that afternoon. The managers' pages for their own shops came back with the same button, form and order.

Check before you publish

1. One button wording on every button.
2. The form asks only what the house list allows, and says what happens next.
3. Every number, comparison and testimonial is in the proof list, or gone.
4. Every image that carries meaning has alt text.
5. Text contrast is at least 4.5:1 (3:1 for large text).
6. The approver has seen the preview.

Next step: keep everyone on the same version

A house style only helps if everyone's AI reads the current one. Stop skill version drift compares sending ZIP files with keeping one shared copy.

Questions

How do I get everyone's AI to make landing pages the same way?

Write the house way into one team skill: the voice and words to avoid, the section order, one call to action, the form fields you ask and never ask, which claims need a source, alt text, contrast, and a rule to return a preview first. Then share one copy that every person's AI reads, instead of each person keeping a prompt of their own.

Can Claude, Cursor and ChatGPT use the same landing page skill?

Yes. Put it in a skill pod such as AI Skill Pod and everyone on the team gets it in their Claude, Cursor or ChatGPT (Pro, Business or Enterprise), from one invite link; on ChatGPT Business and Enterprise an admin or owner adds the pod first. Claude can also take it as an uploaded skill. The skill text is the same everywhere.

Should the AI publish the landing page itself?

Not by default. Have it return a preview, as a private link or an HTML file, with a list of what to check: the button, the form, claims that need a source, alt text and contrast. Publish when the person who approves pages says so.