Add Prompt component for applying llms tags via an agent

 (#6445)

Co-authored-by: fern-api[bot] <115122769+fern-api[bot]@users.noreply.github.com>
Co-authored-by: Devin Logan <devinannlogan@gmail.com>

Author: fern-api[bot]

fern/products/docs/pages/ai/llms-txt/customize-llms-txt.mdx

@@ -7,7 +7,19 @@ Customize what LLMs receive from your site by filtering content within a page us
 
 ## Filter within a page
 
-Within pages, use `<llms-only>` and `<llms-ignore>` tags to control what content is exposed to AI versus human readers on your documentation site.
+Within pages, use `<llms-only>` and `<llms-ignore>` tags to control what content is exposed to AI versus human readers on your documentation site. **UI-only elements belong to human readers, and their programmatic equivalents belong to AI agents.** Wrap clickable cards and UI walkthroughs in `<llms-ignore>`, and pair each with an `<llms-only>` block giving the CLI or API equivalent.
+
+<Prompt
+  title="Add llms-only and llms-ignore tags to my docs"
+>
+Read this page: https://buildwithfern.com/learn/docs/ai-features/customize-llm-output.md
+
+Then analyze my documentation repo and identify where `<llms-only>` and `<llms-ignore>` tags would improve agent readability, following the guiding principle that UI-only elements belong to human readers and their programmatic (CLI/API) equivalents belong to AI agents.
+
+1. Report your analysis first: list the pages and specific sections where you would add each tag, and explain why.
+2. Wait for my confirmation, then implement the changes.
+3. Add rules on when to use `<llms-only>` and `<llms-ignore>` to my `AGENTS.md` file (create the file if it doesn't exist).
+</Prompt>
 
 ### Content for AI only
 
@@ -75,9 +87,7 @@ Replace `my-org/fern-docs` with your desired owner and repository name. Use `--p
   </div>
 </div>
 
-On the docs site, human readers see only the numbered UI steps — the `<llms-only>` block is hidden. LLMs reading this page's Markdown output see the inverse: no UI steps, only the `gh repo create` command they can actually run. Each audience gets the path they can act on.
-
-The guiding principle: **UI-only elements belong to human readers, and their programmatic equivalents belong to AI agents.** Wrap clickable cards and UI walkthroughs in `<llms-ignore>` so agents skip them, and pair each UI step with an `<llms-only>` block that gives the CLI or API equivalent.
+On the docs site, human readers see only the numbered UI steps; LLMs reading this page's Markdown see only the `gh repo create` command they can actually run.
 
 To preview and debug what AI sees for any page, you can append `.md` or `.mdx` to the page URL to [view its Markdown source](/learn/docs/ai-features/markdown).