jkkn-terminologies

The terminology validator scans multiple file types including source code, markdown documentation, UI strings, and templates to identify prohibited terms, outputting a report with specific file, line, and replacement details for each instance found.

Yes, you can automatically fix inconsistent terminology using the optional auto-fix feature, which replaces critical prohibited terms with encouraged terms from the dictionary to enforce brand consistency during development and reviews.

Terminology standardization enforces consistent vocabulary across source code, documentation, and UI strings by applying a critical-term and encouraged-term dictionary, ensuring all text content uses approved, learner-friendly terms before release.

The terminology linter works with markdown docs, source code, UI strings, and templates, scanning these multiple file types to identify and replace prohibited terms while supporting bulk scanning across real-world project workflows.

The best way to audit for brand consistency is running an automated terminology scan that checks all content against a centralized standard dictionary, optionally auto-fixing critical terms to ensure approved vocabulary is used consistently.

You need to run a terminology check during development and code reviews when your repository touches JKKN branding, ensuring that source code, markdown docs, and UI strings consistently use approved terms before release.