👋 Hey Product Hunt,
I’m Cédric, CTO and co-founder of Packmind. We’ve just built an open-source framework for Context Engineering — versioning, distributing, and enforcing organizational standards across repos and coding agents.
### Why we built it
Over the past year, we’ve been scaling AI-assisted development across our teams. Today, about 65% of our commits come from coding agents (Copilot, Cursor, Claude Code, and Kiro).
The productivity gain is real — but so is the drift it creates.
Each assistant ends up coding from a different context snapshot of our architecture, naming conventions, and standards. Some pull from outdated instruction files, others from old wikis. The result: AI-generated code that’s locally correct but globally inconsistent.
We built Packmind OSS to fix that.
### What Packmind OSS does
Create, scale, and govern your engineering playbook for AI coding assistants (Copilot, Cursor, Claude Code, Codex, Kiro…).
✅ Create — turn scattered rules from wikis, ADRs, and code reviews into a living playbook.
✅ Scale — auto-sync the same context across all repos & agents.
✅ Govern — check adherence, visualize drift, and repair it automatically.
### 🔥 We’d love your thoughts
– What’s been most frustrating about managing the context for your AI coding agents?
– How do you keep standards and prompts consistent across repos or assistants?
– What features or integrations would you love to see next?
We’re early, learning fast, and curious about how other teams are scaling AI-assisted development safely.
👉 OSS Repo: https://github.com/PackmindHub/packmind