A Context Card holds the background information you'd normally have to re-type every time — things like your role, your project details, your company's guidelines, or how you want the AI to respond. Save it once, and attach it to any prompt.
Click Contexts in the left sidebar.
What you'll see
Your card collection
All your cards organized by category. Each card displays its name, emoji, category, and a short preview.
The card editor
Click a card to open it. Write your context, add formatting and placeholders, and set details like category, emoji, and description.
Categories
Cards are grouped by what they're for:
- Technical — Standards, architecture, tools your team uses
- Business — Company info, brand voice, target audience
- Creative — Tone, style, formatting preferences
- Custom — Anything else you need
How to use it
Create a card
Click "New Card", pick a category, and write the context you want to reuse.
Give it a short name
Each card gets a short reference name (like @legal-team or @sales-playbook) so you can find it quickly.
Attach it to a prompt
In the Composer, click "Add Card" and pick the card you want to include.
Organize with folders
Group related cards into folders — for example, one folder per project or team.
From a public link
On Builder and above, choose From a public link and enter one public page address. Firecrawl reads it once; a successful read uses two Keypra credits even if you do not save a card.
Choose passages
Select the quotations relevant to your task. Nothing is selected automatically; open the original source if you need more context.
Write your context
Explain which details matter and what is missing. Changing your selection does not overwrite your draft.
Review and save
Choose a name, category and folder, then save. The source link, retrieval date and original selected quotations are kept alongside your edited context.
Use public links only, without private access details. Source text is evidence, not instructions to obey, and importing it does not establish accuracy. Keypra keeps no full-page import archive. Firecrawl receives the page address; its own data handling applies. Address checks do not establish complete protection against provider-side redirects or DNS changes.
Good to know
One card, one topic. A "Legal team context" card and a "Compliance rules" card work better together than one giant card with everything in it.
You can add placeholders like {{project_name}} to your cards. When you use the card in the Composer, you'll fill them in — so the same card adapts to different situations.