TeamContext – Git-native shared context for vibe coding teams
Git-versioned team context for Claude Code teams; reviewable in PRs, synced with tc sync.

Shared prompt library for teams when Cursor and GitHub already handle this.
Engineering managers and team leads
PromptLayer · LangSmith · Cursor Rules
The idea is to make that context more portable and plug-and-play across teams and tools, with a local-first approach so it can run in ChatGPT, Codex, Claude, OpenClaw, or basically anywhere with MCP server connectivity. It also has an API if you want to pull prompt/context config out of your codebase so your team can actually see and edit it, or feature-flag between versions.
A big part of it for me is also being more conscious of token spend and getting better answers earlier on the things that actually matter to you and your team. I’m also working on the knowledge side of it, so contexts and workflows can use the right private/shared knowledge more safely without everything being hardwired into code.
We’re particularly interested in talking to teams that want to use knowledge graphs with shared agent contexts and workflows, and have that pass through our system into any AI runtime, local or hosted, without us needing visibility into the underlying private knowledge itself.
It’s still in alpha, so bear with me, but if this sounds useful I’d genuinely love feedback. Happy to share more information or give demos or free access if anyone wants to check it out.
Git-versioned team context for Claude Code teams; reviewable in PRs, synced with tc sync.
Git-like versioning for prompts running entirely locally with Ollama.
GitHub for prompts is an interesting bet, but PromptBase and FlowGPT already exist.
GitHub for prompts with security scans, but FlowGPT already owns this category.
PayPal pilot shows 2x faster integration with 65% lower token usage than baseline Cursor.
llms.txt generation from whiteboards is clever, but Notion AI already shares context between chats.