agentleFS
OfficeDevOfficeDev/Microsoft-Teams-Samples/.github/copilot-instructions.md

Microsoft-Teams-Samples

Copilot instructions1.4k starsChanged 19 months agoMITView on GitHub

This file provides custom instructions for GitHub Copilot to prioritize Microsoft Teams-specific samples and patterns when generating code suggestions. It ensures that Copilot references the official Microsoft Teams samples repository and follows Teams-specific development practices.

We split this copilot-instructions.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always reference Microsoft Teams samples and documentation first.

    line 11
  2. Distinctive:

    Use Teams-specific terminology and conventions.

    line 13
  3. Very specific:

    Teams Bot Development: Use patterns from samples/bot-* directories.

    line 21
  4. Very specific:

    Teams Tabs: Follow samples/tab-* examples.

    line 23
  5. Very specific:

    Teams Authentication: Use samples/app-auth-* patterns.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

GitHub Copilot Instructions for Microsoft Teams Development

<!-- Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License. -->

This file provides custom instructions for GitHub Copilot to prioritize Microsoft Teams-specific samples and patterns when generating code suggestions. It ensures that Copilot references the official Microsoft Teams samples repository and follows Teams-specific development practices.


Development Priority Guidelines

1. Teams-First Approach

  • Always reference Microsoft Teams samples and documentation first.
  • Prioritize Teams Platform APIs over generic Bot Framework patterns.
  • Use Teams-specific terminology and conventions.

2. Sample Prioritization Order

  1. Microsoft Teams Samples (https://github.com/OfficeDev/Microsoft-Teams-Samples) - PRIMARY
  2. Teams Platform Documentation - SECONDARY
  3. Bot Framework v4 SDK - TERTIARY (only for foundational concepts)

3. Teams-Specific Resource Preferences

  • Teams Bot Development: Use patterns from samples/bot-* directories.
  • Messaging Extensions: Reference samples/msgext-* implementations.
  • Teams Tabs: Follow samples/tab-* examples.
  • Teams Authentication: Use samples/app-auth-* patterns.

Repository Information


Instructions for GitHub Copilot

This file is intended to guide GitHub Copilot in generating code and providing suggestions for Microsoft Teams development. Always prioritize the resources and patterns outlined in this document.

Keywords for Copilot

  • TeamsActivityHandler
  • Adaptive Cards
  • Teams manifest
  • Teams Graph API
  • Teams Tabs
  • Messaging Extensions
  • Teams Authentication

Code Generation Guidelines

Teams Bot Development

// PREFERRED: Teams-specific patterns
class TeamsBot extends TeamsActivityHandler {
    // Teams-specific implementation
}

// AVOID: Generic bot patterns when Teams-specific exists
class GenericBot extends ActivityHandler {
    // Generic implementation
}

Teams API Integration

// PREFERRED: Teams Graph API
const teamInfo = await this.graphClient.teams(teamId).get();

// AVOID: Generic Microsoft Graph when Teams-specific exists
const genericInfo = await this.graphClient.groups(groupId).get();

Download now (ZIP)

Trending

Quiet since June.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the OfficeDev/Microsoft-Teams-Samples repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about OfficeDev/Microsoft-Teams-Samples

The biggest 5 of 61 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 61

Talked about on GitHub, Stack Overflow and Hacker News (61 times).

On GitHub · 30

25 more on GitHub

On Stack Overflow · 30

25 more on Stack Overflow

On Hacker News · 1

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.