AI Tools

Available tools

Tool	Access
GitHub Copilot	Individual account — available to all developers
Gemini	Available through the Google organization

When to use them

Use AI tools to accelerate development tasks: code completion, generating boilerplate, explaining unfamiliar code, writing tests, drafting documentation, or reviewing logic.

These tools work best as assistants for tasks you already understand. Do not rely on them blindly for security-sensitive code, complex business logic, or anything you cannot review confidently.

What must not be sent to AI tools

• Client or personal data — no names, emails, IDs, or any data that belongs to end users
• Credentials and secrets — no API keys, tokens, passwords, or private keys

When in doubt, refer to the Constructions-3D AI Charter for the full rules.

Copilot customization in repositories

Each repository can ship Copilot customization files to improve the quality and consistency of AI suggestions in that specific codebase:

• .github/copilot-instructions.md — always-on instructions that Copilot reads on every interaction in the repo. Use it to describe the stack, coding conventions, naming rules, and any project-specific context the model should always be aware of.
• .github/instructions/*.instructions.md — scoped instruction files that apply only to files matching a given glob pattern. Useful for per-language or per-directory rules.
• .github/prompts/*.prompt.md — reusable prompt files that can be invoked on demand in Copilot Chat. Use them for recurring tasks (e.g. writing a migration, generating a test suite for a module).

Agent skills are defined in the Groupe-3D/Groupe-3D repository under skills/. They are available across all projects and document domain-specific workflows that Copilot agents can follow.

Skills must be installed locally in ~/.copilot/skills/ for your editor to pick them up. With a local clone of this repository, run the sync script to install or update them:

bash ~/path/to/Groupe-3D/skills/sync.sh

To avoid running this manually each time, add a shell alias (see the skills README for details):

# Add to ~/.zshrc or ~/.bashrc — adjust the path to your local clone
alias sync-skills='bash ~/path/to/Groupe-3D/skills/sync.sh'

The script never deletes skills you created yourself — it only adds or updates organisation-managed skills.

Using skills inside a devcontainer

When working inside a devcontainer, ~/.copilot/skills lives on the host machine and must be mounted into the container. The required bind mount and VS Code setting are part of the standard devcontainer setup documented in Devcontainers — Skills mount.

MCP servers

MCP (Model Context Protocol) servers extend Copilot agents with access to external tools and services. The following MCP servers are configured for use at Groupe-3D:

MCP server	Purpose
GitHub	Interact with repositories, issues, pull requests, and code search directly from the agent
Linear	Read and update tickets, projects, and cycles without leaving the editor
C3D Test Planner	Access and manage manual test plans from the agent

MCP servers must be configured in each developer’s local VS Code settings or devcontainer configuration. Refer to each tool’s documentation for the setup steps.