maui: Instructions file for GitHub Copilot

.github/instructions/layout-system.instructions.md

maui layout-system.instructions.md is an instructions file for GitHub Copilot from dotnet/maui. It costs 400 tokens per session, scanned A, original, MIT.

Coding guidance for how .NET MAUI measures and positions controls, including how size limits move through nested layouts.

In plain words
What is it for?
Use it when changing layout panels, measurement methods, padding or borders, grid and stack behavior, or code that runs frequently during screen layout.
Why use it?
It helps prevent controls from being measured and placed with conflicting sizes, endless layout recalculations, and slow layout code.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is dotnet/maui's own configuration. It tells GitHub Copilot how to work on maui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maui configures →

About the project

.NET MAUI is a C# and XAML framework for building native mobile and desktop applications from one shared codebase. Developers use it to create apps for Android, iOS, iPadOS, macOS, and Windows. The catalogue entries provide skills, instructions, and agents for working with .NET MAUI.

dotnet/maui · 23,322 stars · on GitHub · dot.net

Reuse

Borrowing it

Nothing to install: this file belongs to dotnet/maui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/instructions/layout-system.instructions.md
Clone the repo
git clone --depth 1 https://github.com/dotnet/maui

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for maui layout-system.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dotnet/maui/layout-system/github.svg)](https://agentmods.dev/instructions/dotnet/maui/layout-system)
Your own site
<a href="https://agentmods.dev/instructions/dotnet/maui/layout-system"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/layout-system/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for maui layout-system.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dotnet/maui/layout-system"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/layout-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 400 This file is loaded in full into every session.
When invoked 400 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00400 $0.00400
Opus 5.5 $0.00160 $0.00160
Sonnet 5.5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 1mo ago against content hash c75e33a49001, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maui layout-system.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/layout-system.instructions.md · 31 lines

What it actually says

Layout System Rules

Measure/Arrange Contract

  • Measure(widthConstraint, heightConstraint) returns the desired size — it must not mutate layout state or trigger side effects
  • ArrangeChildren(bounds) positions children within the given bounds — it must respect the size returned from Measure, not compute independently
  • A child measured with widthConstraint=200 must not be arranged with width=300 — constraints must stay consistent across passes
  • Subtract padding, margin, and border thickness from constraints BEFORE passing to children

Constraint Propagation

  • Stack layouts pass double.PositiveInfinity along the stacking axis and the parent constraint along the cross axis
  • Grid cells compute per-cell constraints from column/row definitions — do not pass the full grid constraint to each child
  • MeasureContent helpers on IContentView handle inset subtraction — use them instead of manual arithmetic
  • On Windows, double.NaN represents unconstrained dimensions (WinUI convention) — do not confuse with double.PositiveInfinity (MAUI convention)

Infinite Loop Avoidance

  • Never create circular dependencies where child size depends on parent AND parent size depends on child
  • Layout invalidation (InvalidateMeasure) must not re-trigger during an active measure pass
  • ScrollView content must always be re-measured on layout trigger — do not aggressively cache child measurements in scrollable containers

Performance on Hot Paths

Layout measure/arrange methods are hot paths. All rules from performance-hotpaths.instructions.md apply — no LINQ, closures, or allocations. Additionally for layout:

  • Cache expensive computations (e.g., GridStructure) and invalidate only when inputs change
  • Bindable property change handlers should skip layout invalidation when the value has not actually changed
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 31 lines · 400 tokens per session scan A c75e33a49001

Subscribe to this mod's changes

maui layout-system.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 400 tokens to every session, about $0.0016 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.