Documentation and output

July 8, 2026 · View on GitHub

  1. Update the docs for every new or changed rule, decorator, option, or command — a feature without docs is incomplete. Write them in Markdown.
  2. Keep user-facing output (logs, messages, errors) clear, non-technical, and actionable.
  3. Use clear and concise language in all documentation.
  4. Use semantic line breaks in Markdown files (preferably splitting sentences into separate lines).