Desktop

1200

Product

Teams

Pricing

How to check an AI-
generated citation

Follow a claim back to the original page. A simple review
process helps your team separate useful evidence from a
convincing summary.

A citation gives a reader a route back to the evidence. Before using an AI-generated answer in a review, open the original document and find the passage that supports the claim. Check the author, publication date, and version so you know exactly which source you are reading.


Read around the quoted passage


Read the paragraph before and after the quote. A result may apply only to a particular sample, method, or time period. Record those limits alongside the claim so another reader can judge whether the evidence applies to their question.


Keep evidence with the decision


Save the page reference and explain why the passage matters. If the source does not support the claim, revise or remove it. A shared review should make it easy for a colleague to repeat the check without retracing your whole search.

Article page in Framer titled “How to check an AI-generated citation,” with introductory copy and a header image.

/

SEO & AEO

SEO content writer skill

Create, revise, or audit website content for search visibility. Match search intent, use keywords naturally, and keep the copy clear and specific for readers.

Copy skill

Copied

Copy skill

Copied

# SEO Content Create, revise, or audit website content to improve search visibility while preserving the brand’s voice and serving the reader’s intent. ## Instructions - Identify the audience, page purpose, search intent, primary keyword, and CTA. - Plan the message, sections, and heading structure. - Write clear, specific copy that prioritizes people over keyword density. - Use keywords naturally in titles, headings, introductions, and metadata. - Create concise SEO titles, meta descriptions, slugs, FAQs, alt text, and internal-link suggestions. - Audit pages for clarity, structure, search intent, duplication, missing metadata, weak headings, and unsupported claims. - Avoid keyword stuffing, generic language, exaggerated promises, and invented facts. - Preserve the brand’s tone and prepare the content for use in Framer. - Keep recommendations focused on content. Do not change or recommend changes to the visual design, layout, typography, colors, spacing, components, animations, or interactions unless explicitly requested. - Flag design-dependent accessibility issues separately. - Clearly identify assumptions, missing information, and claims requiring verification.

How to apply skills to your project
  1. Keep new pages consistent with your project’s typography, colors, spacing, and components.

    Skill copied

    # Design system

    Use this skill when you add pages or sections to a site that already has a look. You extend the system the team built. You don’t invent a new one.

    ## Before you start

    - Open the home page and two pages close to the new one.

    1. Copy the skill

    Use the Copy button above the skill to copy this skill’s instructions to your clipboard.

  2. /skills

    Turn these instructions into

    a reusable skill:

    GPT 6 Sol

    2. Add it in agent chat

    Type /skills in your agent chat and paste the skill, or add it in Settings / Skills.

  3. Use

    /design-system

    to build a new

    Careers page. Include a couple job openings and a form.

    GPT 6 Sol

    3. Use it in chat

    Type the skill’s command, such as /design-system, in your agent to use it.

  4. Title

    design-system

    Description

    Use components, styles, spacing, and layouts to create new

    Content

    Design system

    Use dark color scheme. Reuse existing styles and components; never invent new colors or text styles.


    Pages

    • Apply the Base layout template to every new page.

    • Set a meta title and meta description on every new page.

    • Sections fill the screen width (1fr) and contain an inner wrapper with maxWidth="1200px" that holds the content.


    Colors

    Container backgrounds: Color/Black.

    Text:

    • Primary headings: Color/White

    • Secondary/body text: Color/White 60

    Accent: Color/Red is the only accent. Use it very sparingly (one highlight per section at most).

    Borders and dividers: Color/Border Solid or Color/Border Transparent.

    Typography

    Always use these text styles, never inline type styles:

    • Set Text Balance to Yes for text layers.

    • Use sentence case; do not use all caps.

    • Do not use eyebrow text (small text above a heading).

    • In heroes, use Text/Body L for supporting text.

    • For every paragraph, adjust its text-box width to produce 50–75 characters per line, targeting 65. Round the width up to the nearest 5 or 10 pixels. If that width is wider than the parent container, set the text box to Fill. Verify at every breakpoint before finishing.

    • Text/H0: jumbo headings and hero treatments

    • Text/H1: blog post titles and secondary page titles

    • Text/H2, Text/H3, Text/H4, Text/H5, Text/H6: all other headings, in hierarchy order

    • Text/Body L: sub heads

    • Text/Body: main body text

    • Text/Body M: small supporting text

    • Text/Button: button labels only

    4. Edit your skill

    Open Settings / Skills whenever you want to make changes.

Your next idea starts here

GPT 6 Sol

Create personal portfolio

Build startup site

Launch landing page

Start company blog

Framer UI showing Pages, Layers and Assets panels titles
Framer UI showing Pages, Layers and Assets panels titles