ai-context-mcp
AGENTS.md2 starsChanged 34 days agoApache-2.0View on GitHub
This repository uses local AI context MCP servers — one per project below. Each server provides indexed code context (module maps, ranked search, file content) scoped exclusively to its project. Use the single repo-wide skill ai-context-workflow to route queries to the right project server.
In this repository3 other files it gives its agents.
- ai-context-workflowSkill
- benchmarkSkill
- idea-mcpSkill
The file
Files
Repository Agent Instructions
AI Context
This repository uses local AI context MCP servers — one per project below.
Each server provides indexed code context (module maps, ranked search, file content)
scoped exclusively to its project. Use the single repo-wide skill
ai-context-workflow to route queries to the right project server.
| Skill | MCP server | When to use |
ai-context-workflow | any registered *-context server | Code context / architecture across the repo |
ai-context-context-workflow (deprecated) | ai-context-context | Old per-project skill; prefer ai-context-workflow |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.