Loading...
Learn how to integrate Context Mesh with your favorite AI tools and workflows.
Context Mesh works with any AI coding assistant. Here's how to set it up.
The AI-first code editor with native file referencing.
123456789101112# In Cursor Settings > Rules for AI# Add the following: When working on this project, always check the context/ directory first.Load relevant context files before making changes:- @context/intent/project-intent.md for project overview- @context/decisions/*.md for architectural decisions- @context/knowledge/patterns/*.md for coding patterns- @context/agents/*.md for task execution Follow the patterns and decisions documented in the context.When making changes, suggest updates to context files if needed.Upload or paste context files for any AI assistant.
# Example prompt structure for Claude
## Loading Context
"Load @context/intent/project-intent.md and @context/decisions/001-tech-stack.md"
## Executing Agents
"Execute @context/agents/agent-feature.md"
## Creating Context
"Create a new decision record for choosing PostgreSQL over MongoDB.
Follow the template in @context/decisions/template.md"Works similarly to Cursor with file referencing.
Windsurf supports the same @file syntax for referencing context.
Your context should live alongside your code in version control.
12345678910111213141516# .gitignore - DON'T ignore context/# The context/ directory should be version controlled # Build outputs.next/dist/build/ # Dependenciesnode_modules/ # Environment.env*.local # The context directory is NOT ignored - it's part of your codebase!# context/ <- This should be tracked in gitEnhance your IDE experience with these configurations.
1234567891011121314151617181920212223242526272829303132333435// .vscode/tasks.json{ "version": "2.0.0", "tasks": [ { "label": "New Intent Document", "type": "shell", "command": "cp context/intent/template.md context/intent/feature-${input:featureName}.md", "problemMatcher": [] }, { "label": "New Decision Record", "type": "shell", "command": "cp context/decisions/template.md context/decisions/${input:decisionNumber}-${input:decisionName}.md", "problemMatcher": [] } ], "inputs": [ { "id": "featureName", "type": "promptString", "description": "Feature name (lowercase, hyphenated)" }, { "id": "decisionNumber", "type": "promptString", "description": "Decision number (e.g., 001)" }, { "id": "decisionName", "type": "promptString", "description": "Decision name (lowercase, hyphenated)" } ]}How to use Context Mesh effectively in a team.
Shared Context Repository
Store context in your main repo or a dedicated context repo.
Context Review
Include context changes in code reviews. They're as important as code.
Regular Evolution
Schedule time to review and evolve context based on learnings.
Take your Context Mesh skills to the next level.