Quick clarification — Team Rules vs team marketplace
Team Rules (what we’ve been talking about)
- Edited in the Cursor Teams dashboard (web UI).
- Stored on Cursor’s servers, pushed to members automatically.
- Good for short org-wide text (“always use X”, globs on file types).
- Not in our git repo — no PR, no diff, no “context engineering like code” for that layer.
Team marketplace (what the docs already offer on Teams/Enterprise)
- A Git repo (GitHub, Azure DevOps, GitLab, Bitbucket) full of plugins.
- Each plugin can bundle rules (.mdc), skills (SKILL.md), agents, MCP, etc.
- Dashboard → Plugins & MCPs → Team Marketplaces → Import from Repo.
- Admins mark plugins Required / Default on / Default off so everyone gets the same pack.
- Changes land via git (PRs to that repo); GitHub can Auto Refresh on push.
So today there are two lanes:
Dashboard Team Rules = enforced prose, not git
Team marketplace = git-backed rules + skills, but plugin-shaped and a separate admin flow
What we actually want (default Team UX)
- Not “learn marketplace vs Team Rules vs project .cursor/.”
- One obvious team default: org context lives in git (review, CI, rollback), syncs to every member and Cloud Agents — like we already treat AGENTS.md and wiki, not like paste into a dashboard.
- Team marketplace is close for rules + skills in a repo, but it’s not the main story Cursor tells, and it doesn’t replace Team Rules or feel like first-class “team config as code.”
Bottom line for the forum:
We’re not asking for something impossible — marketplace is a partial answer.
We’re asking for git-native team context to be the normal, documented path for Teams (not a side quest through plugins), with Team Rules either merged into that model or clearly secondary.