Guidance for coding agents that prepare pull requests against plotly.js. Start at the root AGENTS.md, which lists the rule documents in this folder and says when to read each one.

Read the root AGENTS.md and boundaries.md at the start of every task. Read the other documents when the task reaches the topic they cover. Each document states rules, not background. Follow the links for the reason behind a rule.

These documents describe commands and paths that change over time. If you find a rule that the repository contradicts, say so in your response. Do not silently work around a stale rule.

When you learn something that the next agent needs, add it here. A trap you hit once costs the next agent the same time. Keep the addition to the rule and the reason, and put it in the document that already covers the topic.

Propose the update in its own pull request. A documentation change mixed into a code change hides both, and the two need different reviewers.