From 16a6a87286cc0c6dc47cb963f30d9da03c1d0e5f Mon Sep 17 00:00:00 2001 From: sebastien Date: Fri, 6 Nov 2026 18:55:27 +0100 Subject: [PATCH] chore(ai): put comments on the code they apply to, with explicit default values Co-Authored-By: Claude Opus 5.5 --- .agents/skills/code-style/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.agents/skills/code-style/SKILL.md b/.agents/skills/code-style/SKILL.md index 8903bd229727..95d3af1588eb 100644 --- a/.agents/skills/code-style/SKILL.md +++ b/.agents/skills/code-style/SKILL.md @@ -42,6 +42,7 @@ async function main() { - Comment the code that is weird, unexpected or surprising (a workaround, a non-obvious constraint, an order that matters): that's where readers need one. - Keep comments short, one line when possible. Point to the details instead of writing them out: link the issue, PR, documentation or upstream bug that explains them. - When moving an existing comment, keep its wording: fix typos, don't rephrase it. +- Put each comment on the code it applies to, never floating between unrelated lines. To explain why an option keeps its default value, write that option with its default value, like `trailingSlash: undefined`, and comment it. ```ts // The toggle event also fires when React syncs the open attribute