ai-context-engine-production
Skill1 starsChanged 6 months agoMITView on GitHub
Production deployment of the Context Engine: moderation gatekeepers (two-stage protocol), policy-driven meta-control (the 5 principles), reusable control-deck templates, domain adaptation (legal + marketing case studies), API + worker + Docker + observability deployment topology, and business-value framing for stakeholders.
In this repository21 other files it gives its agents.
- ai-context-engineeringSkill
- ai-context-engineSkill
- 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 21
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 Production
Knowledge from "Context Engineering for Multi-Agent Systems" (Chapters 8-10). The safeguards, applications, and deployment topology that take the engine to production.
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 |
moderation | Two-stage moderation protocol, gatekeeper integration, fail-safe |
policy-driven-control | The 5 principles, policy as outermost context layer |
control-decks | Reusable templates: high-fidelity RAG / context reduction / grounded reasoning |
domain-applications | Legal compliance + strategic marketing case studies |
production-deployment | FastAPI orchestration, async workers, Docker, observability |
business-value | 5 enterprise capabilities, ROI framing, stakeholder messaging |
Workflows
| Workflow | Purpose |
workflows/add-moderation.md | Wire two-stage moderation gatekeeper into the engine |
workflows/adapt-to-domain.md | Adapt the engine to a new vertical (legal, medical, marketing, etc.) |
workflows/deploy-to-production.md | Full go-live (env → API → workers → Docker → observability) |
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.