Context

The Context block provides background information that the AI needs to understand your situation. It bridges the gap between what you know and what the AI knows, giving it the specific details required to provide relevant, accurate responses.

When to Use

Use Context blocks whenever the AI needs information it would not otherwise have:

• Project context: Details about your codebase, tech stack, or architecture
• User context: Information about your audience, customers, or end users
• Domain context: Industry-specific knowledge, terminology, or conventions
• Situational context: Current state, recent changes, or relevant history
• Data context: Relevant facts, statistics, or reference material

How to Use

1. Add a Context block to your prompt canvas
2. Include the specific information the AI needs to know
3. Organize information logically with clear sections if needed
4. Connect it to your other blocks in the appropriate order

Examples

Project Context

Project: E-commerce mobile app built with React Native and TypeScript
Backend: Node.js with PostgreSQL database
Authentication: Firebase Auth with social login support
Current sprint focus: Improving checkout flow conversion rates
Team size: 3 developers, launching MVP in 6 weeks

User Context

Target audience: Small business owners aged 35-55
Technical proficiency: Low to moderate (comfortable with email,
struggle with spreadsheets)
Primary pain point: Spending too much time on manual invoicing
They typically use: QuickBooks, Square, or paper records
Budget sensitivity: High - most are bootstrapped businesses

Domain Context

Industry: Healthcare (HIPAA compliance required)
Terminology note: "Encounter" means a patient visit, "Provider"
means doctor or nurse practitioner
Current regulations: Must store data in US-based servers only
Integration requirements: Must work with Epic and Cerner EHR systems

Code Context

Current function we're refactoring:

function processOrder(order) {
  // Legacy code - no type safety
  // Called 500+ times across the codebase
  // Must maintain backward compatibility
  return order.items.map(i => i.price * i.qty);
}

Related files: orderService.ts, cartUtils.ts, checkoutFlow.ts

Tips

• Only include relevant information: Too much context can dilute the important details
• Be specific with numbers and facts: "Large user base" is vague; "50,000 daily active users" is useful
• Update context as situations change: Stale context leads to outdated advice
• Structure longer context: Use headers or bullet points for readability
• Include constraints within context: "We cannot change the database schema"
• Provide examples of your data: Show sample inputs, typical values, or edge cases