99018f421a
Add tools for maximizing GitHub Copilot effectiveness through better context management: - Instructions: Guidelines for structuring code so Copilot understands it - Agent: Context Architect - plans multi-file changes by mapping dependencies - Prompts: - context-map: Map all affected files before changes - what-context-needed: Ask Copilot what files it needs - refactor-plan: Create phased refactor plans with rollback steps Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
6.1 KiB
Context Engineering
Tools and techniques for maximizing GitHub Copilot effectiveness through better context management. Includes guidelines for structuring code, an agent for planning multi-file changes, and prompts for context-aware development.
Tags: context, productivity, refactoring, best-practices, architecture
Items in this Collection
| Title | Type | Description | MCP Servers |
|---|---|---|---|
Context Engineering  |
Instruction | Guidelines for structuring code and projects to maximize GitHub Copilot effectiveness through better context management | |
| Context Architect |
Agent | An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies see usage | |
| Context Map |
Prompt | Generate a map of all files relevant to a task before making changes see usage | |
| What Context Do You Need? |
Prompt | Ask Copilot what files it needs to see before answering a question see usage | |
| Refactor Plan |
Prompt | Plan a multi-file refactor with proper sequencing and rollback steps see usage |
Collection Usage
Context Architect
recommended
The Context Architect agent helps plan multi-file changes by mapping dependencies and identifying all relevant files before making modifications.
Use this agent when:
- Planning refactors that span multiple files
- Adding features that touch several modules
- Investigating unfamiliar parts of the codebase
Example usage:
@context-architect I need to add rate limiting to all API endpoints.
What files are involved and what's the best approach?
For best results:
- Describe the high-level goal, not just the immediate task
- Let the agent search before you provide files
- Review the context map before approving changes
Context Map
optional
Use before any significant change to understand the blast radius. Produces a structured map of files, dependencies, and tests.
What Context Do You Need?
optional
Use when Copilot gives a generic or incorrect answer. Asks Copilot to explicitly list what files it needs to see.
Refactor Plan
optional
Use for multi-file refactors. Produces a phased plan with verification steps and rollback procedures.
This collection includes 5 curated items for Context Engineering.