[Style Guide] Add rules against LLM-written content patterns

[mvvmm]

Summary

Adds explicit rules to the agent style guide reference and the human-facing admonitions page covering patterns that appear frequently in LLM-generated docs:

• Emoji used as inline admonition substitutes (💡 Tip:, ⚠️ Warning:) instead of :::note/:::caution/:::tip directives
• A catch-all "avoid obviously LLM-written patterns" rule with concrete examples (em dashes, "simply"/"just", throat-clearing intros, ✅/❌ table columns, manual TOCs, etc.)

Documentation checklist

• The change adheres to the documentation style guide.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
*	@cloudflare/product-owners
/src/content/docs/style-guide/	@dcpena, @caley-b, @cloudflare/product-owners

[ask-bonk]

1 issue needs fixing before merge.

CRITICAL — and contain unrelated dependency bumps (astro, vitest, wrangler, typescript-eslint, etc.) that are not mentioned in the PR title or description. Remove these files from the PR to avoid scope creep and unintended side effects.

LOW — Posted 1 inline suggestion for grammar consistency in the agent reference.

Out of scope — The PR description lists many LLM anti-patterns, but the human-facing style guide only reflects the emoji-as-admonition rule. Consider whether rules like "no throat-clearing introductions" and "avoid condescending qualifiers" should also appear in the human-facing writing guidelines.

[ask-bonk]

Fix grammar to match imperative style of surrounding bullets:

Suggested change

	- **"We" and "let's".** Use imperative ("Run the command") or second person ("You can configure..."). Not "Let's run" or "We will configure".
	- **Use em dashes sparingly.** An occasional em dash for a sharp aside is fine; using them in every other sentence is a sign the sentence should be restructured. Prefer a period or a comma.

[ask-bonk]

Correction to my review above: The filenames got mangled by shell escaping. The files that need to be removed from this PR are package.json and pnpm-lock.yaml.

[ask-bonk]

I've completed the review for PR #31269.

Labels applied: documentation, content:edit

Summary of changes

• Adds 12 new anti-LLM writing rules to .agents/references/style-guide.md (LLM-filler phrases, condescending qualifiers, throat-clearing introductions, summary paragraphs, "we"/"let's", "note that", "ensure", "as mentioned above", em dashes, emojis in prose/tables, manual TOCs, and bold misuse).
• Adds a matching emoji-as-admonition rule to the human-facing page src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx.
• Accidentally includes dependency bumps in package.json and pnpm-lock.yaml (astro, vitest, wrangler, typescript-eslint, etc.) totaling ~900 lines of diff.

Issues flagged

• CRITICAL — package.json and pnpm-lock.yaml contain unrelated dependency bumps not mentioned in the PR title or description. These should be removed from the PR to avoid scope creep and unintended side effects.
• LOW — Posted 1 inline suggestion on .agents/references/style-guide.md line 86: "Em dashes sparingly" should be "Use em dashes sparingly" to match the imperative style of the surrounding bullets.
• Out of scope note — The PR description lists many LLM anti-patterns, but the human-facing style guide only reflects the emoji-as-admonition rule. Consider whether rules like "no throat-clearing introductions" and "avoid condescending qualifiers" should also appear in the human-facing writing guidelines (e.g. writing-guidelines.mdx).

github run

[github-actions]

Preview URL: https://54ffadcb.preview.developers.cloudflare.com
Preview Branch URL: https://style-guide-emoji-admonitions.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/style-guide/formatting/notes-and-other-notation-types/	https://style-guide-emoji-admonitions.preview.developers.cloudflare.com/style-guide/formatting/notes-and-other-notation-types/

[mvvmm]

/bonk re-review

[ask-bonk]

1 issue needs fixing before merge.

LOW — .agents/references/style-guide.md line 81: The em dashes bullet does not use imperative mood, which is inconsistent with the other top-level writing style bullets.

Posted 1 inline suggestion.

[ask-bonk]

Use imperative mood to match the surrounding bullets:

Suggested change

	- **Em dashes overused.** One per page is a sign of good writing. One per paragraph is not. Restructure or use a comma or period.
	- **Use em dashes sparingly.** One per page is a sign of good writing. One per paragraph is not. Restructure or use a comma or period.

[ask-bonk]

Posted the re-review on PR #31269.

What I found:

• The package.json and pnpm-lock.yaml files were successfully removed — that critical issue is resolved.
• One grammar issue remains from the previous review: .agents/references/style-guide.md line 81 ("Em dashes overused.") still doesn't match the imperative mood used by the surrounding top-level bullets. I posted an inline suggestion to change it to "Use em dashes sparingly."
• The new rules against LLM-written patterns and emoji admonitions are otherwise clear and well-placed.

github run