Examples

These pages use the per-page override feature to demonstrate what each override surface does. Each example sets a different llmActions: frontmatter shape; visit the page and compare its dropdown (or its absence) against any other page on this site.

What you can override per page

Each frontmatter override is documented on its own example page. Open the page, click the dropdown, and inspect what changed.

Page	Frontmatter
Opt out entirely	llmActions: false
Custom prompt	llmActions: { prompt: '…' }
Custom trigger label	llmActions: { triggerLabel: '…' }
Hide specific providers	llmActions.actions.openIn.providers.<id>: false
Per-provider prompt	llmActions.actions.openIn.providers.<id>.prompt: '…'
No PDF on this page	llmActions.actions.printPdf: false
No print notice	llmActions.printNotice: false
Mixed overrides	combination of several

How precedence works

When a page sets a prompt, the layered precedence (most-specific wins) is:

1. Per-page and per-provider prompt
2. Per-page top-level prompt
3. Global per-provider prompt
4. Global top-level prompt

So a page-level prompt overrides the global default, but does not override a per-provider prompt that was explicitly set in the global config. The Per-provider prompt example walks through this case.

Tip: use llmActions: true to document intent

llmActions: true is the same as omitting the key — the page inherits the global config — but it lets you record intent in the frontmatter:

---
title: SDK quickstart
llmActions: true # AI tools enabled here
---