This directory contains GitHub-specific configuration files that enhance the development experience with AI coding assistants like GitHub Copilot.
Custom instructions for GitHub Copilot that provide context about the EventRelay project, including:
- Architecture overview and design patterns
- Code quality standards and best practices
- Technology stack details
- Common development tasks and workflows
- Security guidelines
- Testing standards
- References to evaluated resources and optional tools
Purpose: Helps Copilot generate more accurate and contextually appropriate code suggestions.
User persona map for adapting Copilot's explanations and implementation guidance to builders, founders, operations leads, educators, enterprise teams, and EventRelay contributors.
Purpose: Keeps persona-specific context available without weakening the repository's workflow, security, or validation requirements.
Comprehensive evaluation of recommended resources for EventRelay integration:
- langwatch/better-agents - Agent testing and reliability toolkit
- github/github-mcp-server - Official GitHub MCP integration
- Google Cloud agent-starter-pack - Production agent templates
Each resource is evaluated for relevance, value add, integration effort, and includes a decision (integrate, defer, or skip) with rationale.
Purpose: Documents evaluation decisions and provides guidance on future enhancements.
Documentation for Model Context Protocol (MCP) server configuration, including:
- Available MCP servers and their capabilities
- Configuration examples for different editors
- Environment variable setup
- Troubleshooting guide
- Best practices for MCP usage
Purpose: Guides developers in setting up and using MCP servers for enhanced AI capabilities.
Ready-to-use MCP server configuration file that can be:
- Used directly by compatible editors (VS Code, Cursor)
- Copied to editor-specific configuration locations
- Modified for custom MCP server setups
Purpose: Provides a working MCP configuration that integrates with EventRelay's agent framework.
GitHub Copilot automatically reads copilot-instructions.md to understand project context. No additional setup is needed beyond having Copilot enabled in your editor.
To get the most value:
- Ensure you're working in the repository root
- Ask Copilot questions about project-specific patterns
- Reference project concepts in comments to get contextual suggestions
-
Copy
mcp-servers.jsonto your editor's MCP configuration location:- Cursor:
~/.cursor/mcp.json - VS Code: Workspace settings or user settings
- Cursor:
-
Update paths if your workspace location differs
-
Set required environment variables in
.env:YOUTUBE_API_KEY=your_key MCP_TIMEOUT=300 MCP_MAX_CONCURRENT=5
-
Restart your editor to activate MCP servers
See mcp-config.md for examples of using MCP servers from Python code.
The repository also includes:
../.devcontainer/- Dev container configuration for consistent environments../.vscode/- VS Code workspace settings and recommended extensions
When project patterns or architecture change:
- Update
copilot-instructions.mdto reflect new patterns - Update
mcp-config.mdif MCP server capabilities change - Validate changes with validation script:
python3 scripts/validate_copilot_instructions.py - Test that instructions produce better AI suggestions
- Commit changes to keep AI context current
../docs/CLAUDE.md- Claude AI master framework../.claude/claude_instructions.md- Claude code-specific instructions../.cursor/rules/- Cursor editor-specific rules../README.md- Project overview and setup
To validate that the Copilot instructions meet all requirements:
# Run validation script
python3 scripts/validate_copilot_instructions.pyThe script checks for:
- Required sections (Environment Variables, Database Connections, etc.)
- Backend-frontend compatibility documentation
- API key management guidance
- Code examples in Python, TypeScript, and Bash
- Database configuration documentation
When adding new features or patterns:
- Document them in relevant instruction files
- Add examples to help AI assistants understand usage
- Keep instructions focused on patterns, not implementation details
- Run validation script to ensure completeness
- Test that AI tools produce better suggestions with updated context