What are contexts?
Contexts are reusable units of knowledge that provide guidance, instructions, documentation, and organizational expertise to humans and AI systems.
Your contexts act as the source of truth for information that needs to be shared consistently across multiple destinations.
A context can contain:
- Product documentation
- Engineering standards
- Design guidelines
- Team processes
- Domain knowledge
- Operating procedures
- Custom instructions
Why use contexts?
Teams often duplicate the same knowledge across documentation, prompts, AI assistants, and internal tools.
Contexts solve this by allowing teams to maintain information once and distribute it everywhere it is needed. Contexts allow you to:
- Keep information consistent and reduce duplication across tools
- Maintain knowledge and instructions more easily
- Improve the quality of AI responses
- Control the distribution of knowledge to appropriate teams
Types of contexts
Design system context
Connected to a design system. Distributes design system data alongside workspace knowledge like files and skills.
Workspace context
Not attached to any design system. Distributes workspace knowledge only — files and skills. Use it for team knowledge that isn’t tied to a design system.
|
Content type |
Design system context |
Workspace context |
|---|---|---|
|
Documentation pages |
Yes |
— |
|
Design tokens |
Yes |
— |
|
Token themes |
Yes |
— |
|
Assets |
Yes |
— |
|
Code components |
Yes |
— |
|
Figma components |
Yes |
— |
|
Design system components |
Yes |
— |
|
Files |
Yes |
Yes |
|
Skills |
Yes |
Yes |
Next steps to explore