.vale.ini

# Vale prose linter configuration.
#
# Vale checks the Markdown docs in this repository for a basic writing bar and
# for "AI slop" tells (em-dashes, formulaic transitions, metacommentary, etc.).
# In CI it runs only on the Markdown files changed by a pull request; run it
# locally over everything with `vale sync && vale .`.
#
# The goal is helpful, not pedantic: a handful of high-noise / low-value rules
# from the upstream styles are disabled below with a note on why.

StylesPath = styles
MinAlertLevel = suggestion

# Third-party style packages, pinned so `vale sync` is reproducible.
#
#   write-good  -- basic prose linter (weasel words, wordiness, cliches).
#   ai-tells    -- flags linguistic patterns common in AI-generated prose.
#                  Tracks the latest release (the URL 302-redirects to it) so
#                  new tells are picked up on the next `vale sync`.
Packages = write-good, \
  https://github.com/tbhb/vale-ai-tells/releases/latest/download/ai-tells.zip

[*.md]
BasedOnStyles = write-good, ai-tells, DeadlineSamples

# --- write-good rules disabled as too noisy for technical reference docs ---
# E-Prime bans every use of "to be" (is/are/was); impractical for docs.
write-good.E-Prime = NO
# Passive voice is fine and often clearer in technical descriptions
# ("the adapter is uploaded to the queue").
write-good.Passive = NO
# TooWordy flags precise words like "modify", "multiple", "additional".
write-good.TooWordy = NO

# --- ai-tells rules disabled as too noisy / false-positive prone ---
# ColonUsage flags proper nouns after a colon (e.g. "Forest Pack", "Model").
ai-tells.ColonUsage = NO
# FormalRegister flags accurate technical terms ("frameworks",
# "implementation") as overly formal.
ai-tells.FormalRegister = NO