mintlify
diff --git a/‎.claude/commands/review.md‎
Lines changed: 2 additions & 1 deletion b/‎.claude/commands/review.md‎
Lines changed: 2 additions & 1 deletion
diff --git a/‎.vale.ini‎
Lines changed: 31 additions & 0 deletions b/‎.vale.ini‎
Lines changed: 31 additions & 0 deletions
diff --git a/‎.vale/README.md‎
Lines changed: 45 additions & 0 deletions b/‎.vale/README.md‎
Lines changed: 45 additions & 0 deletions
diff --git a/‎.vale/scripts/discover-vocabulary.sh‎
Lines changed: 33 additions & 0 deletions b/‎.vale/scripts/discover-vocabulary.sh‎
Lines changed: 33 additions & 0 deletions
diff --git a/‎.vale/styles/Google/AMPM.yml‎
Lines changed: 9 additions & 0 deletions b/‎.vale/styles/Google/AMPM.yml‎
Lines changed: 9 additions & 0 deletions
diff --git a/‎.vale/styles/Google/Acronyms.yml‎
Lines changed: 64 additions & 0 deletions b/‎.vale/styles/Google/Acronyms.yml‎
Lines changed: 64 additions & 0 deletions
diff --git a/‎.vale/styles/Google/DateFormat.yml‎
Lines changed: 9 additions & 0 deletions b/‎.vale/styles/Google/DateFormat.yml‎
Lines changed: 9 additions & 0 deletions
diff --git a/‎.vale/styles/Google/Ellipses.yml‎
Lines changed: 9 additions & 0 deletions b/‎.vale/styles/Google/Ellipses.yml‎
Lines changed: 9 additions & 0 deletions
diff --git a/‎.vale/styles/Google/EmDash.yml‎
Lines changed: 13 additions & 0 deletions b/‎.vale/styles/Google/EmDash.yml‎
Lines changed: 13 additions & 0 deletions
diff --git a/‎.vale/styles/Google/Exclamation.yml‎
Lines changed: 12 additions & 0 deletions b/‎.vale/styles/Google/Exclamation.yml‎
Lines changed: 12 additions & 0 deletions
@@ -9,6 +9,7 @@ Please review the changes I'm about to commit and check:
 3. Are any code examples accurate?
 4. Is the frontmatter complete and correct?
 5. Does the content match our existing style?
-6. Are there any links that need testing?
+6. Run vale on the files being updated and make a plan to resolve any errors, warnings, and suggestions.
+7. Are there any links that need testing?
 
 $ARGUMENTS
@@ -0,0 +1,31 @@
+# Vale configuration for Mintlify documentation
+
+StylesPath = .vale/styles
+MinAlertLevel = suggestion
+IgnoredScopes = code, tt, img, url, a
+SkippedScopes = script, style, pre, figure, code
+
+Packages = Google
+
+Vocab = Mintlify
+
+# This is required since Vale doesn't officially support MDX
+[formats]
+mdx = md
+
+# MDX support
+[*.mdx]
+BasedOnStyles = Vale, Google
+Vale.Terms = NO # Enforces really harsh capitalization rules, keep off
+Vale.Avoid = NO # Too aggressive about common technical terms
+
+# Token and block ignores for MDX-specific syntax
+TokenIgnores = (?sm)((?:import|export) .+?$), \
+(?<!`)(<\w+ ?.+ ?\/>)(?!`), \
+(<[A-Z]\w+>.+?<\/[A-Z]\w+>), \
+(<[^>]*>)
+
+BlockIgnores = (?sm)^(<\w+\n .*\s\/>)$, \
+(?sm)^({.+.*})
+
+CommentDelimiters = {/*, */}
@@ -0,0 +1,45 @@
+# Vale Configuration for Mintlify Docs
+
+This directory contains the Vale linting configuration for Mintlify documentation.
+
+## Philosophy
+
+Start simple and grow incrementally as needs emerge. The current setup uses:
+
+- Core Mintlify-specific vocabulary
+- Customized rules from the Google developer documentation style guide
+
+## Vale files
+- `.vale.ini` - Main configuration file
+- `styles/config/vocabularies/Mintlify/` - Mintlify-specific terms
+- `styles/Google/` - Google developer documentation style rules customized for Mintlify docs
+
+## When to add vocabulary
+- **Mintlify terms** - New components, features, platform-specific concepts
+- **Frequent false positives** - Any terms that repeatedly trigger spelling errors, but shouldn't
+
+### Discover new vocabulary
+Use the included script to find vocabulary candidates:
+```bash
+# Discover terms from all files
+.vale/scripts/discover-vocabulary.sh
+
+# Discover from specific files
+.vale/scripts/discover-vocabulary.sh "components/*.mdx"
+```
+
+This script:
+1. Runs Vale on specified files
+2. Extracts spelling error suggestions
+3. Saves results to `.vale/vocabulary-candidates.txt`
+
+## When to add new rules
+- **Consistent patterns** - The same style issue appears frequently
+- **High-value, low-noise** - Rules that catch problems with minimal false positives
+
+### Testing new rules
+Before adding a new rule:
+1. Test locally: `vale path/to/file.mdx`
+2. Run on sample files: `vale components/*.mdx`
+3. Check false positive rate
+4. Start with `level: suggestion` then promote to `warning` or `error`
@@ -0,0 +1,33 @@
+#!/bin/bash
+# Script to discover potential vocabulary terms from Vale output
+# Usage: ./discover-vocabulary.sh [file-pattern]
+
+set -e
+
+PATTERN=${1:-"**/*.mdx"}
+OUTPUT_FILE=".vale/vocabulary-candidates.txt"
+
+echo "🔍 Discovering vocabulary candidates from Vale spelling errors..."
+echo "Pattern: $PATTERN"
+echo ""
+
+# Run Vale and extract spelling error words
+vale --no-exit $PATTERN 2>&1 | \
+grep "Vale.Spelling" | \
+sed -n "s/.*Did you really mean '\([^']*\)'.*/\1/p" | \
+sort | uniq -c | sort -nr > "$OUTPUT_FILE"
+
+if [ -s "$OUTPUT_FILE" ]; then
+    echo "Found vocabulary candidates in $OUTPUT_FILE:"
+    echo ""
+    head -20 "$OUTPUT_FILE"
+    echo ""
+    echo "Review these terms and add appropriate ones to:"
+    echo "   - .vale/styles/config/vocabularies/Mintlify/accept.txt (if valid)"
+    echo "   - .vale/styles/config/vocabularies/Mintlify/reject.txt (if misspellings)"
+    echo ""
+    echo "To clean up this file: rm $OUTPUT_FILE"
+else
+    echo "✅ No vocabulary issues found!"
+    rm -f "$OUTPUT_FILE"
+fi
@@ -0,0 +1,9 @@
+extends: existence
+message: "Use 'AM' or 'PM' (preceded by a space)."
+link: "https://developers.google.com/style/word-list"
+level: error
+nonword: true
+tokens:
+  - '\d{1,2}[AP]M\b'
+  - '\d{1,2} ?[ap]m\b'
+  - '\d{1,2} ?[aApP]\.[mM]\.'
@@ -0,0 +1,64 @@
+extends: conditional
+message: "Spell out '%s', if it's unfamiliar to the audience."
+link: 'https://developers.google.com/style/abbreviations'
+level: suggestion
+ignorecase: false
+# Ensures that the existence of 'first' implies the existence of 'second'.
+first: '\b([A-Z]{3,5})\b'
+second: '(?:\b[A-Z][a-z]+ )+\(([A-Z]{3,5})\)'
+# ... with the exception of these:
+exceptions:
+  - API
+  - ASP
+  - CLI
+  - CPU
+  - CSS
+  - CSV
+  - DEBUG
+  - DOM
+  - DPI
+  - FAQ
+  - GCC
+  - GDB
+  - GET
+  - GPU
+  - GTK
+  - GUI
+  - HTML
+  - HTTP
+  - HTTPS
+  - IDE
+  - JAR
+  - JSON
+  - JSX
+  - LESS
+  - LLDB
+  - NET
+  - NOTE
+  - NVDA
+  - OSS
+  - PATH
+  - PDF
+  - PHP
+  - POST
+  - RAM
+  - REPL
+  - RSA
+  - SCM
+  - SCSS
+  - SDK
+  - SQL
+  - SSH
+  - SSL
+  - SVG
+  - TBD
+  - TCP
+  - TODO
+  - URI
+  - URL
+  - USB
+  - UTF
+  - XML
+  - XSS
+  - YAML
+  - ZIP
@@ -0,0 +1,9 @@
+extends: existence
+message: "Use 'July 31, 2016' format, not '%s'."
+link: 'https://developers.google.com/style/dates-times'
+ignorecase: true
+level: error
+nonword: true
+tokens:
+  - '\d{1,2}(?:\.|/)\d{1,2}(?:\.|/)\d{4}'
+  - '\d{1,2} (?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)|May|Jun(?:e)|Jul(?:y)|Aug(?:ust)|Sep(?:tember)?|Oct(?:ober)|Nov(?:ember)?|Dec(?:ember)?) \d{4}'
@@ -0,0 +1,9 @@
+extends: existence
+message: "In general, don't use an ellipsis."
+link: 'https://developers.google.com/style/ellipses'
+nonword: true
+level: warning
+action:
+  name: remove
+tokens:
+  - '\.\.\.'
@@ -0,0 +1,13 @@
+extends: existence
+message: "Don't put a space before or after an em dash."
+link: "https://developers.google.com/style/dashes"
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - trim
+    - " "
+tokens:
+  - '\s[—–]\s'
+
@@ -0,0 +1,12 @@
+extends: existence
+message: "Don't use exclamation points in text."
+link: "https://developers.google.com/style/exclamation-points"
+nonword: true
+level: warning
+action:
+  name: edit
+  params:
+    - trim_right
+    - "!"
+tokens:
+  - '\w+!(?:\s|$)'