Document linter rule ID naming conventions in linter authoring docs

[Copilot]

TypeSpec linter docs explain how to define rules but did not provide guidance for naming rule IDs beyond examples, which made non-no-* rules less predictable. This PR adds concise naming conventions next to createRule({ name }) so authors can choose consistent, user-readable rule names.

• Added rule naming guidance in linter authoring docs

  • Updated website/src/content/docs/docs/extending-typespec/linters.md with a new “Naming convention” section.
  • Documented:
    • short kebab-case names
    • excluding package/library prefix from name
    • no-<thing> for prohibitions
    • use-<preferred-thing> for preferred patterns
    • subject-oriented forms for domain checks (e.g. <subject>-missing-<thing>, <subject>-invalid-<condition>)

• Clarified user-facing context for rule IDs

  • Explicitly notes rule names are surfaced in diagnostics, tspconfig.yaml, docs URLs, and suppression comments, guiding authors toward concise readable IDs.

export const rule = createRule({
  name: "use-standard-resource-model",
  // ...
});

[timotheeguerin]

@copilot use Naming convention as the heading

[Copilot]

@copilot use Naming convention as the heading

Updated in commit 8552679.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension