copilot instructions

Copilot Instructions - Windows gecko wiki

Overview

This is the GitHub Wiki for the Windows gecko project - a desired state configuration tool for Windows devices targeting Windows Autopilot and Microsoft Intune deployments.

Conventions

• All files use UTF-8 encoding, LF line endings, 2-space indentation (see .editorconfig)
• Wiki page links use GitHub Wiki syntax: [[Page Name]]
• Page filenames use lowercase kebab-case: configuring-windows-apps.md
• The landing page is Home.md - do not rename it
• Navigation is defined in _Sidebar.md

Naming

• Always use Windows gecko (lowercase "g") - not "Windows Gecko" or "gecko"
• Always use Windows Autopatch - not just "Autopatch"
• Always use Windows Autopilot - not just "Autopilot"
• Always use Microsoft Intune - not just "Intune"
• Always use Visual Studio Code - not just "VS Code"

Documentation & Links

• Microsoft Learn URLs: Never include the /en-us/ locale segment. Use https://learn.microsoft.com/mem/... not https://learn.microsoft.com/en-us/mem/...
• Legacy domains: Use learn.microsoft.com instead of the deprecated docs.microsoft.com
• Cross-references: Link to other wiki pages using [[Page Name]] syntax, not raw markdown links

Writing Style

• Use clear, concise technical language
• Use headings (##, ###) to structure content - avoid # (reserved for the page title auto-generated by GitHub Wiki)
• Use fenced code blocks with language identifiers (e.g., ```json, ```powershell)
• Use tables for structured data (e.g., property references, parameter lists)
• Use spaced hyphens (-) instead of em dashes (—) for inline separators

JSON Examples

• Use 2-space indentation in JSON code blocks
• Include only relevant properties in examples — omit unrelated sections for clarity

Wiki Page Layout

All wiki pages follow a standard layout. GitHub Wiki auto-generates an H1 heading from the filename, so pages must never start with a # header.

Standard page structure

• No # header — GitHub Wiki generates the H1 from the filename; adding one creates a duplicate
• Bold opening sentence — the first line is a bold sentence acting as the page subtitle
• Headers never go directly into content blocks — always include a short intro sentence between a ##/### heading and bullet lists, tables, code fences, or similar block elements
• ## sections — use ## for main sections, ### for subsections; avoid deeper nesting
• Status callouts — use > [!NOTE] for modules that are in development, in review, or in preview
• Related resources — every page ends with a "Related resources" section linking to relevant docs and [[wiki pages]]

**Bold intro sentence.** Second sentence expanding on the module's purpose.

> [!NOTE]
> Optional status callout (only for non-Available modules).

## Overview

One or two paragraphs describing the module's purpose and behavior.

## Configuration

JSON example showing the module's configuration structure.

## Dataset properties

Property reference table(s) with columns: Property, Description, Type, Required.

## Reference

Optional section with useful PowerShell commands for discovery.

## Related resources

Short intro sentence before the list.

- Relevant links and cross-references

Revision date

Every wiki page ends with an italic revision date as the last line, separated from the content by a horizontal rule.

---

*Page revised: March 4, 2026*

Update the revision date whenever meaningful content changes are made to a page. Use the format *Page revised: Month Day, Year*.