GitHub Copilot vs Kiro | agentconfig.ing

GitHub Copilot vs KiroComparisonUpdated 2026-03-16

SUMMARY

GitHub Copilot (IDE) uses markdown configuration while Kiro (IDE) uses markdown. They differ on 2 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	GitHub Copilot	Kiro	Notes
Config format	markdown	markdown
Hierarchy support	✓	✓	Whether config files can be placed at multiple directory levels
Global config	✗	✓	User-wide configuration outside any project
Project config	✓	✓
Subdirectory scoping	✓	✗	Config files in subdirectories that apply only to that subtree
File inclusion / imports	✗	✗	Ability to include or reference other files from config
Ignore file	✗	✗
IDE integration	✓	✓
Schema / structure	Free-form (Markdown)	Free-form (Markdown)	Whether config uses structured schema or free-form content
Git committed	✓	✓	Whether primary config files are intended to be version-controlled
Encoding	UTF-8	UTF-8

FILE MAPPING

Purpose	GitHub Copilot	Kiro
Project instructions	.github/copilot-instructions.md	.kiro/steering/*.md
Project instructions	.github/instructions/*.instructions.md	AGENTS.md

SIDE-BY-SIDE CODE SAMPLES

GitHub Copilot

.github/copilot-instructions.md

markdown

# Copilot Instructions

## Code Style
- Use TypeScript strict mode for all new files
- Prefer functional components with hooks over class components
- Use named exports, not default exports

## Libraries
- Use date-fns for date manipulation (not moment.js)
- Use zod for runtime validation
- Prefer fetch over axios for HTTP requests

## Testing
- Write tests using Vitest
- Use Testing Library for component tests
- Aim for integration tests over unit tests

## Conventions
- Use camelCase for variables, PascalCase for components
- Prefix interfaces with I (e.g., IUserProps)
- Keep files under 300 lines; extract if longer

Kiro

.kiro/steering/*.md

markdown

---
inclusion: always
---

# Project Standards

## Stack
- TypeScript 5.x with Node.js 22
- AWS CDK v2 for infrastructure
- DynamoDB for data, S3 for assets

## Conventions
- Use ESM imports, not CommonJS
- Lambda handlers export a named `handler` function
- Use middy middleware for cross-cutting concerns
- All API responses follow JSON:API format

## Testing
- Unit tests with vitest
- Integration tests with aws-testing-library
- E2E tests use deployed staging environment

KEY DIFFERENCES

1. Global config

GitHub Copilot: Not supported. Kiro: Supported.

2. Subdirectory scoping

GitHub Copilot: Supported. Kiro: Not supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use GitHub Copilot, configure .github/copilot-instructions.md. If you use Kiro, configure .kiro/steering/*.md. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh

bash

# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md