Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.figr.design/llms.txt

Use this file to discover all available pages before exploring further.

​
Product Context

Figr’s product context awareness is what makes AI-generated designs feel native to your specific product. Learn how to leverage this deep understanding for better design outcomes.

​
How Product Context Works

Multi-layered product understanding:
Diagram showing layers of product context from user data to technical constraints
Context layers:
User context:
- Persona characteristics and behaviors
- Skill levels and technical proficiency
- Device and platform preferences
- Geographic and cultural considerations

Business context:
- Strategic objectives and KPIs
- Market positioning and differentiation
- Revenue models and monetization
- Compliance and regulatory requirements

Technical context:
- Platform capabilities and limitations
- Performance requirements and constraints
- Integration points and dependencies
- Security and privacy requirements

Design context:
- Existing design system and patterns
- Brand guidelines and visual identity
- Accessibility standards and requirements
- Cross-platform consistency needs

​
Context Categories

1

User Context Deep Dive

Understanding your specific users:
Detailed user understanding:

Primary persona: Marketing Manager
- Technical proficiency: Intermediate
- Primary tasks: Campaign creation, performance analysis
- Pain points: Complex reporting, time-consuming setup
- Success metrics: Campaign ROI, time to launch
- Device usage: 60% desktop, 40% mobile

Secondary persona: Campaign Specialist
- Technical proficiency: Advanced
- Primary tasks: Detail optimization, A/B testing
- Pain points: Limited automation, manual processes
- Success metrics: Conversion optimization, efficiency
- Device usage: 90% desktop, 10% mobile
2

Business Context Integration

Aligning design with business objectives:
Business goal influence on design:

Revenue growth → Conversion optimization focus
User retention → Engagement feature emphasis
Market expansion → Localization considerations
Competitive differentiation → Unique feature highlighting
Cost reduction → Efficiency workflow prioritization

Brand positioning impact:

Premium positioning → Sophisticated, clean design
Value positioning → Efficiency and functionality focus
Innovation leader → Cutting-edge interaction patterns
Trust-focused → Conservative, reliable patterns
Accessibility leader → Inclusive design prioritization

Compliance requirements:

Healthcare (HIPAA) → Privacy-first design patterns
Finance (SOX) → Audit trail emphasis
Education (FERPA) → Student data protection
European markets (GDPR) → Consent management
Accessibility (WCAG) → Inclusive interaction design
3

Technical Context Application

Design within technical reality:
Technical limitation awareness:

Mobile performance → Lightweight interactions
Legacy browser support → Progressive enhancement
Slow networks → Offline-first design
Limited bandwidth → Image optimization priority
Battery life → Animation and processing limits

​
Context-Driven Design Examples

Context shapes dashboard priorities:
Two dashboard designs showing how different user contexts create different layouts
Executive user context:
Design implications:
- High-level metrics prominently displayed
- Trend visualization over detailed data
- One-click drill-down capabilities
- Mobile-optimized for on-the-go access
- Clean, presentation-ready layouts
Analyst user context:
Design implications:
- Detailed data tables with sorting/filtering
- Advanced chart customization options
- Export functionality in multiple formats
- Real-time data refresh controls
- Desktop-optimized for extended sessions

​
Leveraging Context for Better Designs

1

Context Query Optimization

Ask better questions to get better results:

Generic Request

Less effective: “Create a user settings page”Result: Generic settings layout

Context-Rich Request

More effective: “Create user settings for marketing managers who need quick access to notification preferences and team collaboration settings”Result: Prioritized layout with relevant features
2

Context Validation

Ensure context accuracy:
Context verification methods:

User research validation:
- Interview findings alignment
- Survey data correlation
- Usability testing confirmation
- Analytics pattern verification

Business requirement checking:
- Strategic objective alignment
- KPI impact assessment
- Stakeholder expectation matching
- Market positioning consistency

Technical constraint verification:
- Performance requirement feasibility
- Integration capability confirmation
- Security standard compliance
- Platform limitation acknowledgment
3

Context Evolution Management

Keep context current and relevant:
Context maintenance schedule:
- Quarterly user research integration
- Monthly analytics review
- Weekly feedback incorporation
- Daily usage pattern monitoring

​
Advanced Context Features

Predictive Context

Anticipate future needs:
  • User behavior prediction
  • Seasonal usage pattern awareness
  • Growth-stage design adaptation
  • Market trend incorporation
  • Technology evolution preparation

Multi-Context Design

Handle complex context combinations:
  • Cross-persona design optimization
  • Multi-platform context balancing
  • Regional variation management
  • Industry-specific customization
  • Accessibility context integration

​
Best Practices

1

Context Accuracy

Maintain high-quality context:
✅ Validate context with real user research
✅ Update context regularly as product evolves
✅ Consider edge cases and minority users
✅ Balance multiple context sources
✅ Document context assumptions clearly
2

Context Application

Use context effectively in design:
✅ Reference specific context in design requests
✅ Validate design decisions against context
✅ Consider context trade-offs explicitly
✅ Test designs with contextual users
✅ Iterate based on context-specific feedback

Configure Design Systems

Learn how to set up and manage design tokens for consistent, scalable design systems in Figr.Setting Tokens →