coding-markdown

Markdown Instructions

Vertical Spacing

• Minimal empty lines between sections
• No empty lines between related list items
• Headers immediately followed by content
• Single empty line between major sections only

Formatting Rules

Strictly enforce the following formatting for all file paths and references to reduce noise:

• No Markdown Links: Never use name syntax. Use plain backticks only.
• No Line Numbers: Strip all line number suffixes (e.g., :22).
• No Redundancy: Do not repeat the filename in brackets and parentheses.
• Contextual Pointers: When referencing specific sections, name the section instead of using line numbers. Examples: Bad: app/models/user.py Good: app/models/user.py Bad: user.py Good: app/models/user.py Bad: See .roo/rules/01-general.md Good: See Critical Resources in .roo/rules/01-general.md

Formatting Standards

Strictly enforce the following minimalist formatting rules. Style & Typography

• References: Use inline code backticks (e.g., file.py) for files and code. Never use brackets or links.
• Indentation: Use exactly 4 spaces for nested items. Lists & Spacing
• Numbering: Use ) as the separator (e.g., 1), 2)). Never use periods (1.).
• Density: No empty lines between list items. Group related items tightly.
• Headers: Content must start on the very next line after a header. Do not insert an empty line. Examples Bad (Wrong list style, extra spacing):

## Analysis

**Points**:

1. First item

2. Second item

Good (Compact, correct list style):

## Analysis
**Points**:
1) First item
    - Nested detail
2) Second item