Cursor rule

1# Confluence Editing Standards (Markdown Authoring)
2 
3Purpose: Ensure Markdown renders cleanly in Confluence by applying spacing, nesting, and code formatting rules during page creation/updates.
4 
5## Lists & Spacing
6- Always insert a blank line between list items.
7 
8- Use nested sub-bullets for subpoints; never concatenate multiple points on a single line.
9 
10- For ordered lists, keep each step single-purpose; add an empty line between steps when a step has sub-bullets.
11 
12## Inline vs Code Blocks
13- Prefer inline code for short, single-line commands or file paths (e.g., `composer install`).
14 
15- Use fenced code blocks only when necessary (multi-line commands, config snippets). Verify Confluence renders the block without collapsing; otherwise, convert to inline steps.
16 
17- Do not mix bullets and code blocks without a blank line before and after the block.
18 
19## Headings & Anchors
20- Keep headings concise; avoid trailing punctuation.
21 
22- When using Markdown format, avoid enabling heading anchors if they introduce ID artifacts in rendered output.
23 
24## Tables
25- Keep tables simple (5–7 columns max). Prefer bullets when content wraps heavily.
26 
27- Add a brief sentence above a large table explaining what it captures.
28 
29## Nested Structure
30- Depth guidance: limit nesting to two levels (bullet → sub-bullet). If content requires more depth, split into a new subsection.
31 
32## Check Before Publish (Quicklist)
33- Bullets have blank lines between items.
34 
35- Sub-bullets are properly indented and grouped.
36 
37- Commands are inline where possible; multi-line blocks tested for rendering.
38 
39- No anchor artifacts in headings.
40 
41- Tables are readable; consider bullets if wide.
42 
43## Optional Page Label Cue
44When editing an existing Confluence page, if the page has label `format-spaced-lists`, apply these spacing rules strictly even if the original content is inconsistent.
45 
46