Turn websites into Gemini context

Why websites needs preparation before Gemini

Documentation and reference pages are often the missing context behind a codebase, client project, or research question.

Gemini is useful when you want a large working context and need to combine notes, docs, and technical material in one pass. The result depends heavily on how cleanly your source material is grouped, labeled, and filtered before it reaches the model.

Step-by-step workflow

Add the public URL, let Riflet extract readable page text, then combine it with local files or repos.

• Add website pages as a Riflet source.
• Select documentation pages, product pages, help articles, changelogs, public specs, and reference pages.
• Use filters to remove stale exports, generated files, and unrelated background material.
• Export one Markdown or text bundle and use it in Gemini Gems.

What to include

For this workflow, prioritize documentation pages, product pages, help articles, changelogs, public specs, and reference pages. Add a short instruction file at the top if the AI needs naming conventions, project goals, or constraints.

Scraped pages are snapshots. Re-export when the website changes or when you need a different section of the site.

Getting the bundle into Gemini Gems

Gemini Gems keeps uploaded material in Gem knowledge. Create or edit a Gem and attach the bundle as knowledge, sitting alongside the instructions that define how the Gem should behave. It accepts text, Markdown, PDF, and Google Docs, so a Markdown or plain-text export from Riflet needs no further conversion.

A large context window tempts you to attach everything. The binding constraint is usually attention, not capacity: a focused bundle beats a full dump even when both comfortably fit, because every irrelevant page competes with the relevant ones.

A Gem's knowledge is edited in the Gem itself, so the update is a deliberate step. That is an advantage when you want the Gem's answers to stay pinned to a known version of the source material.

Token budget advice

Riflet lets you check the bundle against Gemini 3.7 Flash's 1,048,576-token context window before export. Keep room for your actual question and for the model's answer.

If the bundle is too large, remove files that merely repeat what another file already explains. Context quality usually beats context volume.

Honest limitation

Riflet does not push live updates into Gemini. It creates the context file. When the source changes, re-export and upload the new bundle yourself.