Create llms.txt skill

# Create llms.txt Create a short, factual guide to a Framer site’s content. Use live-site mode when the site has a confirmed public domain and prelaunch mode when it has not been published yet. ## Before you start - Confirm whether the request covers the whole site or one section. - Check for a live public domain. Never guess it from the project name or use a branch or preview address as the live domain. - Read an existing llms.txt if one is available and preserve useful content that is still accurate. - Use the sitemap, navigation, Framer pages, and CMS to find candidate pages. Read page content before describing it. ## Live-site mode 1. Open each candidate URL and check that it shows the expected public content. For Framer pages, try ?md; use the public HTML page if Markdown is unavailable. 2. Choose pages that help readers understand the organization, its products or services, pricing, documentation, and support. For a large CMS collection, start with roughly three to five pages covering distinct, important topics. 3. Skip drafts, private or broken pages, duplicate content, and thin utility pages. Flag pages hidden from search; include them only if the user asks or there is a clear reason. 4. Write llms.txt with a # Site name heading, a brief > summary, and useful ## sections. Format each link as - [Page title](https://confirmed-domain/path): Short factual description. 5. Check every URL and description in the finished file. Remove duplicate links and search for placeholders such as YOUR-DOMAIN, example.com, and TODO. Provide a downloadable UTF-8 file named llms.txt only when these checks pass. ## Prelaunch mode 1. Review the available branch or preview content. Prepare a draft with proposed sections, page titles, one-sentence descriptions, and project page paths such as /pricing. Do not turn those paths into links or add a placeholder domain. 2. Start the draft with # Prelaunch llms.txt draft and a note that the paths and descriptions need checking on the published site. List any pages that could not be read. 3. Provide the draft as a downloadable file named llms-draft.md. If file creation is unavailable, provide the complete draft in chat and say that no file was created. 4. Do not create a file named llms.txt or give upload instructions yet. 5. Once the user provides a live domain, verify the published pages and turn the draft into an upload-ready llms.txt. ## Handoff - Report the domain if confirmed, pages covered, number of live links checked, and any checks that could not be completed. - For an upload-ready file, tell the user to open Framer → Site Settings → Hosting → Files, upload it at /llms.txt, publish through their usual process, and check https://confirmed-domain/llms.txt. - If file creation is unavailable, say so and provide the complete verified text for the user to save. Never claim a download or hosted file exists when it does not. ## Rules - Keep the guide focused. Do not copy full pages, invent facts, or add promotional claims. - Do not claim that llms.txt improves rankings, guarantees AI mentions, or controls crawling or model training. - Do not change site pages, CMS content, robots.txt, sitemaps, indexing settings, or publishing settings. - Report what was checked and what remains uncertain. Do not grade the skill’s own performance.