docs(markdown): centralize clickable link guidance

- Add a global Markdown rule for clickable navigational URLs
- Point documentation-specific guidance back to the shared rule
- Update the rule index description to surface the link guidance

Clarifies where clickable-link guidance lives so Markdown and
documentation rules stay consistent instead of drifting apart.

Author: d-padmanabhan

rules/800-markdown.mdc

@@ -1,6 +1,6 @@
 ---
 title: Markdown & Diagramming Style Guide
-description: Standardized rules for generating Markdown files using GitHub-flavored alerts and Mermaid diagrams for visual documentation.
+description: Standardized rules for generating Markdown files using GitHub-flavored alerts, clickable links, and Mermaid diagrams for visual documentation.
 priority: 800
 alwaysApply: true
 files:
@@ -470,12 +470,35 @@ All documents should follow this structure:
 4. Use logical heading hierarchy (H2, H3, etc.)
 5. Incorporate **GitHub alerts** where they add value
 6. Use **Mermaid diagrams** to visualize complex concepts
-7. Use proper markdown formatting (lists, code blocks, links, emphasis)
+7. Use proper markdown formatting (lists, code blocks, links, emphasis); navigational URLs must be Markdown links, not backticks (see **Links and URLs** below)
 8. **Avoid decorative emojis** - use professional, clean formatting
 9. End with conclusion or next steps if applicable
 
 ---
 
+## Links and URLs
+
+This applies to **all** Markdown and MDX in the workspace (READMEs, rules, docs, ADRs, PR bodies when using Markdown, etc.).
+
+### Navigational links must be clickable
+
+Use standard Markdown links so URLs render as clickable in GitHub, IDEs, and common static-site renderers. Prefer descriptive link text.
+
+- **Preferred**: `[AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)`
+- **Avoid for navigation**: bare URLs in running text when a short label reads better (still use `https://...` in link target)
+- **Do not** wrap URLs that readers should **click** in backticks: `` `https://docs.aws.amazon.com/lambda/` `` — inline code styling often prevents click-through and copies poorly.
+
+### When backticks around a URL are correct
+
+Wrap a URL in backticks only when it is a **literal value**, not a navigation affordance—for example: configuration samples, CLI transcripts, log lines, schema defaults, or strings inside code-oriented examples.
+
+### Paths and anchors
+
+- Use relative paths for same-repo docs when practical: `[Contributing](../CONTRIBUTING.md)`
+- For file paths shown as literals (not links), backticks remain appropriate: `` `src/app.ts` ``
+
+---
+
 ## Emoji Guidelines
 
 **Do NOT use emojis in professional technical documentation.**
@@ -564,7 +587,7 @@ Emojis MAY be used in:
 
 ### General Markdown
 - Use code blocks with syntax highlighting
-- Include links to external resources
+- Use Markdown links for external resources and internal docs (**Links and URLs**)
 - Use tables for structured data
 - Add horizontal rules (`---`) to separate sections
 - Maintain consistent formatting

rules/810-documentation.mdc

@@ -348,13 +348,7 @@ Success!
 
 ### Links Must Be Clickable
 
-In documentation, prefer Markdown links so URLs render clickable in GitHub and common renderers.
-
-- **Preferred**: `[AWS Lambda docs](https://docs.aws.amazon.com/lambda/)`
-- **NEVER USE** backticks for links that should be clickable: `` `https://docs.aws.amazon.com/lambda/` ``
-
-> [!NOTE]
-> Wrap URLs in backticks only when the URL is being treated as a literal code value (for example, config, CLI output, or sample strings).
+Follow the global rule in **[800-markdown.mdc](800-markdown.mdc)** under **Links and URLs** (Markdown links for navigation; no backticks on clickable URLs except when the URL is a literal value).
 
 ## API Documentation
 

rules/INDEX.md

@@ -82,7 +82,7 @@ Quick lookup table for all Cursor rules files in `rules/`.
 
 | File | Description | Priority | Always Apply |
 |------|-------------|----------|--------------|
-| [800-markdown.mdc](800-markdown.mdc) | Standardized rules for generating Markdown files using GitHub-flavored alerts and Mermaid diagrams for visual documentation. | 800 | Yes |
+| [800-markdown.mdc](800-markdown.mdc) | Markdown/MDX style: GitHub alerts, **clickable Markdown links** (no backticks on navigational URLs), and Mermaid diagrams. | 800 | Yes |
 | [810-documentation.mdc](810-documentation.mdc) | Patterns for creating effective documentation including documentation websites and markdown best practices. | 810 | No |
 | [820-open-source.mdc](820-open-source.mdc) | Best practices for open source projects including contribution guidelines, documentation, and community management. | 820 | No |
 

skills/documentation-standards/references/markdown-mermaid.md

@@ -89,10 +89,12 @@ flowchart TD
 
 #### Use Markdown links (not backticks) for clickable URLs
 
+Canonical guidance: **800-markdown.mdc** → **Links and URLs** (global rule for all `.md` / `.mdx`).
+
 In documentation, backticks render URLs as code and they are often **not clickable**.
 
 - **Preferred**: `[AWS doc](https://docs.aws.amazon.com/vpc-lattice/latest/ug/auth-policies.html)`
-- **NEVER USE** backticks for links that should be clickable: `` `https://docs.aws.amazon.com/vpc-lattice/latest/ug/auth-policies.html` ``
+- **Do not** wrap navigational URLs in backticks: `` `https://docs.aws.amazon.com/vpc-lattice/latest/ug/auth-policies.html` ``
 
 ### Sequence Diagram