Copilotインストラクションを改善する5つのコツ
GitHub公式ブログ。プロジェクト概要・技術スタック・コーディング規約・構造・リソースの5つの観点でインストラクションを改善。
# 5 Tips for Writing Better Custom Instructions for GitHub Copilot
## 1. Provide a Project Overview
Include an elevator pitch: what your app does, who the audience is, and key features.
Example: "This is a website to support pet adoption agencies."
## 2. Identify Your Tech Stack
Document backend frameworks, frontend tools, APIs, and testing suites.
List technologies like Flask, PostgreSQL, Astro, Svelte with brief notes on usage.
## 3. Spell Out Coding Guidelines
Define standards across your project: formatting preferences, type hints requirements, and testing expectations. Apply broadly across all languages in the project.
## 4. Explain Project Structure
Map out folder organization and what each contains.
Example: "server/ : Flask backend code" with sub-folders for models, routes, tests.
## 5. Point to Available Resources
List scripts, development tools, and automation resources.
Include MCP tools like Playwright or GitHub integrations that Copilot agents can leverage.
## Bonus Tip
Use Copilot itself to generate your copilot-instructions.md file by prompting it with structured guidance about your repository. こちらもおすすめ
DevOps カテゴリの他のルール
もっとルールを探す
CLAUDE.md、.cursorrules、AGENTS.md、Image Prompts の全 157 ルールをチェック。



