Team and Enterprise Deployment

Commit Prompts to Your Repository

Copy the prompts you use from your prompt repo (see Prompt Delivery) into your code repo and commit them. Everyone who pulls the repo gets the same prompts, and new developers get them when they clone.

your-project/
├── <your tools' instruction files>   # one per AI tool your team uses
└── prompts/
    ├── VERSION                       # which release you copied from
    ├── js/express/5.2/prompt.md      # the prompts you use, in the delivered layout
    └── python/django/5.2/prompt.md

Each tool reads its own instruction file. See IDE Integrations, AI Coding Agents, and Claude Code for the file each tool uses and how to keep several in sync.

In a monorepo, give each service its own prompt with directory-level instruction files; see Claude Code.

Organization-Level Defaults

Some tools support organization-wide configuration:

Tool	Organization setting
GitHub Copilot	Organization custom instructions (Copilot Business or Enterprise). They apply on GitHub.com and in Copilot code review, not in local editors.
Cursor	Team rules in the Cursor dashboard (Team and Enterprise plans). Admins can make a rule required for everyone.
Claude Code	A managed CLAUDE.md at a system path (for example /etc/claude-code/CLAUDE.md on Linux), deployed to machines with MDM or similar tools. Developers can't exclude it.

For tools without organization-wide configuration, the committed repository files are the standard.