Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/aws-samples/sample-well-architected-skills-and-steering/llms.txt

Use this file to discover all available pages before exploring further.

GitHub Copilot picks up repository-level instructions from .github/copilot-instructions.md and applies them automatically across all Copilot interactions in that project. Copying the Well-Architected instructions file into your repository gives Copilot always-on awareness of all six WA pillars, design principles, and trade-off guidance — no additional setup required.
GitHub Copilot does not have a separate skill or playbook mechanism. All Well-Architected guidance is embedded directly in copilot-instructions.md rather than being split across steering and skill files. This means the full WA context is always active, but there are no step-by-step multi-phase review flows like those available in tools that support a dedicated skills directory.

What gets installed

.github/copilot-instructions.md

A single instructions file that inlines all six Well-Architected pillars, design principles, trade-off guidance, and response formatting rules. GitHub Copilot reads this file automatically for every conversation in the repository.

Installation

1

Clone or download the source repo

If you haven’t already, clone the sample repository to a local path you can reference:
git clone https://github.com/aws-samples/sample-well-architected-skills-and-steering.git
2

Copy the instructions file into your project

Run the commands below from the root of your project directory, substituting path/to/this-repo with the actual clone location.
mkdir -p .github
cp path/to/this-repo/adapters/github-copilot/.github/copilot-instructions.md .github/
3

Verify the layout

Your project should now contain:
.github/
  copilot-instructions.md

Install via script

If you prefer the one-command approach from a local clone, the install script handles directory creation and copying automatically:
./install.sh ~/my-project --tool github-copilot

Usage

Once .github/copilot-instructions.md is committed to your repository, GitHub Copilot applies Well-Architected principles automatically whenever you discuss architecture in Copilot Chat or ask for infrastructure code suggestions in the IDE. No explicit invocation is needed.
What Well-Architected considerations should I address in this design?
Copilot will group findings by pillar and use severity labels (🔴 High Risk, 🟡 Medium Risk, 🟢 Best Practice) as instructed by the guidance file.
Because all guidance is inlined, the WA context is always present without you needing to prompt for it. Copilot will proactively surface relevant pillar considerations when you ask about infrastructure, deployment, or system design topics.

What’s covered in the instructions file

The copilot-instructions.md file embeds the following guidance that Copilot applies to every interaction:
SectionContent
RoleAWS Well-Architected advisor persona
Six pillarsOperational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability
Design principlesManaged services, design for failure, decoupling, multi-AZ, least privilege, IaC, observability
Trade-off guidanceSecurity vs. latency, availability vs. cost, performance vs. portability, cost vs. resilience
Response formatPillar grouping, severity labels, “why it matters” context, concrete next steps

Build docs developers (and LLMs) love