Svelte Agent Rules

A compiler for building reactive web interfaces.

Overview

Svelte's 11-line AGENTS.md points to existing contributor docs, requires the full test suite before a pull request, and sends performance investigations to a dedicated skill.

Pointing at the source of truth Contribution etiquette Router files

Documents

├── 
├── .github
│   └── 
├── 
└── performance-investigation — Performance-investigation skill

Techniques in this file

01 / Pointing at the source of truth

Delegate repository detail to the contributor guide

The root file identifies CONTRIBUTING.md as the place for testing, structure, and contribution rules. That lets the short agent entry point share an authority with human contributors.

5**Important:** Read and follow [`CONTRIBUTING.md`](./CONTRIBUTING.md) as well - it contains essential information about testing, code structure, and contribution guidelines that applies here.

02 / Contribution etiquette

Make the PR template and full suite explicit gates

Before submitting a pull request, the agent must read the template and run the full test suite. Both actions are named in the same instruction.

7When submitting a PR, you **MUST** read [`PULL_REQUEST_TEMPLATE.md`](./.github/PULL_REQUEST_TEMPLATE.md) and fill it out correctly. **DO NOT** submit a PR without running the full test suite.

03 / Router files

Route performance investigations to a skill

The final sentence names a specific skill when the task is a performance investigation. The general entry file stays short while task-specific procedure lives elsewhere.

11If asked to do a performance investigation, use the `performance-investigation` skill.

Ideas for your repo

Keep shared contributor rules in one authoritative document.
Name the checks and template required before a pull request.
Route specialized investigations to task-specific guides.