ai-context-engine
Skill1 starsChanged 6 months agoMITView on GitHub
The full Context Engine architecture: dual RAG (procedural + factual), Pinecone-based ingestion, the Planner / Executor / Tracer triad, specialist agents (Context Librarian, Researcher, Writer), the Agent Registry, production hardening (dependency injection, logging, modularization), plus an appendix-style reference guide.
In this repository21 other files it gives its agents.
- ai-context-engineeringSkill
- ai-context-engine-productionSkill
- ai-dataset-engineeringSkill
- ai-evaluationSkill
- ai-finetuningSkill
- ai-foundation-modelsSkill
- ai-inference-optimizationSkill
- ai-multi-agent-mcpSkill
- ai-production-architectureSkill
- ai-prompt-engineeringSkill
- ai-rag-and-agentsSkill
- ai-rag-defenseSkill
- ddia-architectureSkill
- ddia-batch-stream-processingSkill
- ddia-data-ethicsSkill
- ddia-data-modelingSkill
- ddia-replication-shardingSkill
- ddia-transactions-consistencySkill
- job-description-analyzerSkill
- resume-content-writerSkill
- resume-fit-scorerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Check guidelines.md to find which files to load
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Context Engine
Knowledge from "Context Engineering for Multi-Agent Systems" (Chapters 3-5 + Appendix A). The full architecture and hardening of the glass-box Context Engine.
Quick Start
- Check
guidelines.mdto find which files to load - Load only relevant files (each topic has knowledge.md, rules.md, examples.md)
- Apply guidance to your work
Contents
References
| Category | Purpose |
dual-rag | Procedural vs factual RAG, context library vs knowledge base |
rag-ingestion | Pinecone setup, token-aware chunking, embeddings, upsert |
engine-components | Planner, Executor, Execution Tracer (the engine triad) |
specialist-agents | Context Librarian, Researcher, Writer (initial + hardened) |
agent-registry | Capability descriptions, get_handler, dependency injection |
hardening | DI, structured logging, proactive context mgmt, modularization |
engine-reference | Appendix-style reference guide for the commons library |
Workflows
| Workflow | Purpose |
workflows/build-context-engine.md | Full engine build (dual RAG → triad → agents → registry → run) |
workflows/setup-rag-pipeline.md | Pinecone ingestion (chunk → embed → upsert) |
workflows/harden-engine.md | Take prototype to production (DI, logging, modularization) |
Guidelines
See guidelines.md for task-based file selection.
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.