Markdown Instructions

These rules apply to all markdown the AI writes — project files (README, rules, skills, docs), plans, and inline markdown in responses.

File Path References

Strictly enforce minimalist path references to reduce noise:

• Follow platform link requirements first: If the active harness requires clickable file references or line numbers, that requirement overrides this section.
• Default for markdown files: When no platform requirement says otherwise, use plain backticks instead of [name](path) syntax.
• Line numbers: Include line numbers only when the active harness or planning workflow requires them.
• No redundancy: Do not repeat the filename in both brackets and parentheses.
• Contextual pointers: Reference section names instead of line numbers.

Exceptions: Planner modes (architect, planner-a, planner-b, planner-c) may use links when creating or modifying a plan; any harness-level clickable-link rule also overrides the default plain-backtick preference.

Examples:

• Bad: [app/models/user.py](app/models/user.py) → Good: `app/models/user.py`
• Bad: [user.py](app/models/user.py:50) → Good: `app/models/user.py`
• Bad: See \rules/01-general.md`→ Good:See 'Critical Resources' in `rules/01-general.md``