**/*.md: Lists should be surrounded by blank lines.
Use numbered lists for sequential steps, procedures, or prioritized items; use bullet lists for non-sequential items.
Begin each item in a list with a capital letter, unless it is a command or code block.
Do not use semicolons, commas, or conjunctions at the end of list items.
Do not use a period at the end of list items unless they are complete sentences.
Write content in a flowing text style in Markdown files; if not, adjust to flowing text.
Do not use tables in documentation; use lists instead, as tables do not render well on mobile devices.
Use the commonmark specification for Markdown.
Use Markdown for writing content; avoid HTML where possible.
When using code fenced code blocks, specify the language for syntax highlighting.
Contents of a code fenced code block must never exceed 80 character line length.
Use ATX style heading syntax (use '#' for headings) in Markdown files.
Ensure header increments are correct and do not skip any levels; the page title in front matter is the first level heading, so all content below should be at least a second level heading.
Use '-' for unordered lists and '.' for ordered lists in Markdown.
Use '_' for italic text and '**' for bold text in Markdown.
Use backticks when referring to file paths, file names, variable names, or text entered in a field.
Use Liquid syntax for templating in Jekyll within Markdown files.
To indicate a location in the UI, use the 'My link' Liquid tag.
To reference glossary terms, use the '{% term %}' Liquid tag.
Avoid using abbreviations and acronyms; if used, add an abbreviation tag to show the full term as a tooltip.
To refer to an icon in the UI, use the Iconify library via the '{% icon %}' Liquid tag.
Use the '{% details %}' Liquid block for collapsible text blocks; do not use the HTML5 variant.
Use '{% tip %}', '{% note %}', and '{% important %}' Liquid blocks for highlighting recommendations and important sections.
Use Markdown syntax to add images; use HTML only for images with captions.
Use the specified HTML syntax for embedding YouTube videos.
For YAML examples, use 2 spaces for indentation.
Only allow 'true' and 'false' (lowercase) as boolean values in YAML examples.
YAML comments must match the current indentation level, start with a capital letter, and have a space after the hash.
Prefer block style sequences in YAML; avoid flow style sequences.
If flow style sequences are used in YAML, ensure a space after each comma and no whitespace before brackets.
Only allow block style mappings in YAML; do not use flow style mappings.
Null values in YAML should be implicitly marked; avoid explicit null values ('~' and 'null').
Strings in YAML are preferably quoted with double quotes (").
For multi-line strings in YAML, use literal (|) or folded (>) style; avoid '\n' or long single-line strings.
Do not include configuration options with default values in YAML examples unless specifically educating about that option.
Entity IDs, attributes, device IDs, area IDs, platform types, condition types, trigger types, action names, device classes, event names, and hardcoded values are exempt from double-quoting in YAML.
Use service action targets in YAML examples for Home Assistant service calls; do not specify entity_id at the action or data level.
Do not use comma-separated strings or flow style for lists of scalar values in YAML; use block style lists.
If a property accepts a mapping or a list of mappings in YAML, always use a list of mappings, even for a single item.
Avoid using templates in YAML examples if a pure YAML version is available.
Templates in YAML must be double-quoted, with single quotes used inside the template.
Avoid long lines in YAML templates; split across multiple lines for readability.
Prefer shorthand style templates in YAML over the expressive format.
Require spacing around the filter pipe marker ' | ' in YAML templates.
Do not use the states object directly in YAML templates; use helper methods like states(), is_state(), state_attr(), is_state_attr().
Remove empty conditions, default 'mode: single', and empty 'data' sections from automation and script YAML examples.
Textual contents in YAML parameters (like 'title') should follow the same writing style as the documentation, including sentence-style capitalization.

📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)

List of files the instruction was applied to:

• source/_includes/integrations/remove_device_service_steps.md
• source/_includes/common-tasks/beta_version.md

[uncategorized] ~96-~96: Consider adding a hyphen.
Context: ... %} and select the area card. 2. In the top right corner, select the three dots {% icon "...

(TOP_LEFT_CORNER)

[uncategorized] ~45-~45: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...fore* trying to add the new entry. - In the top right of Devices & services...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)

[uncategorized] ~45-~45: You might be missing the article “the” here.
Context: ...the new entry. - In the top right of Devices & services page, select the t...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

40-40: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)