Copilot Instructions

# Copilot Instructions — copilot-learning-labs

<!--
  Repository-wide instructions for GitHub Copilot.
  Applies to all chat, edit, plan, and agent sessions in this repository.

  Rules:
  - Keep instructions specific, bounded, and non-contradictory.
  - Prefer shorter, actionable rules over long explanations.
  - Update "Verified" when you materially change this file.
  Verified: 2026-07
-->

---

## 1. Repository Purpose

This repository is a **public open course** on GitHub Copilot Pro+ in Visual Studio Code. It teaches learners to use Copilot seriously and productively, from setup through advanced multi-agent workflows. Learning is theory-first with **guided prompt examples** inside each module; the capstone is the only hands-on project.

Content types:

| Type                        | Folder              | Authoritative template                   |
| --------------------------- | ------------------- | ---------------------------------------- |
| Learning modules            | `modules/XX-slug/`  | `templates/module-readme-template.md`    |
| Module summaries            | `modules/XX-slug/summary.md` | `templates/summary-template.md` |
| Prompt library entries      | `prompts/category/` | `templates/prompt-template.md`           |
| Agent persona definitions   | `agents/`           | `templates/agent-definition-template.md` |
| Custom instruction examples | `instructions/`     | free-form markdown                       |
| Checklists                  | `checklists/`       | free-form markdown                       |

When generating content in this repository, Copilot is producing **educational material**, not production application code. The audience is an **experienced developer who has never used GitHub Copilot**.

---

## 2. Writing Style

### Voice and tone

- Use **active voice** at all times: "Configure the setting" not "The setting can be configured."
- Use **operational language**: explain what the learner does, not what a feature is.
- Write at a **professional but approachable** level — clear to a developer with 1–2 years of experience.
- Be direct. Omit preamble ("In this section we will…") and filler ("It is worth noting that…").

### Sentence and paragraph rules

- One idea per sentence. Split compound sentences where possible.
- Prefer bullet points and tables over paragraphs for lists of steps, comparisons, and options.
- Never use passive voice for instructional steps.
- Never write "simply", "just", "obviously", or "easily" — these condescend to beginners.

### Audience awareness

- Always assume the reader may be new to the specific topic, even if experienced in adjacent areas.
- Define terms on first use with `**bold**`. Do not assume familiarity with Copilot-specific terminology.
- When a step requires a prerequisite, state it explicitly: "Before this step, complete Task 2."

---

## 3. Structure Rules

### Modules (`modules/XX-slug/`)

Every module folder must contain exactly these two files — no more, no fewer: