brewing-terminology-checker

Validate German and English brewing terminology consistency across project files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jonsdoesch87-ai/craft-beer-wizard --skill brewing-terminology-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brewing-terminology-checker
Source: https://github.com/jonsdoesch87-ai/craft-beer-wizard/tree/main/.cursor/skills/brewing-terminology-checker
Command: npx skills add https://github.com/jonsdoesch87-ai/craft-beer-wizard --skill brewing-terminology-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures the consistent and correct use of German and English brewing terminology, preventing errors in documentation and translations.

Core Features & Use Cases

  • Terminology Validation: Checks for correct usage of brewing terms across languages.
  • Consistency Enforcement: Ensures uniform application of terms for brewing phases, mash steps, ingredients, hop additions, yeast types, and units.
  • Use Case: Ideal for internationalization (i18n) checks or when updating documentation to maintain accuracy and professionalism in craft beer content.

Quick Start

Use the brewing-terminology-checker skill to verify the consistency of brewing terms in the provided documentation files.

Frequently Asked Questions about brewing-terminology-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure consistent English and German brewing terminology across documentation files?

You can ensure consistent English and German brewing terminology by validating project files to enforce correct, uniform usage of brewing phases, mash steps, ingredients, hop additions, yeast types, and units for documentation accuracy.

What is the best way to check craft beer translation consistency for internationalization?

Checking craft beer translation consistency for internationalization involves identifying and correcting language-specific term usage and unit inconsistencies across bilingual documentation to maintain professional accuracy.

How do I validate brewing terms in i18n documentation to prevent translation errors?

Validating brewing terms in i18n documentation requires scanning project files to identify and correct language-specific term usage and unit inconsistencies, enforcing uniform application of craft beer vocabulary across translations.

Does terminology validation support both language-specific brewing terms and measurement units?

Yes, terminology validation supports both language-specific brewing terms and measurement units, enforcing the correct and uniform application of ingredients, mash steps, and units across English and German project files.

Can I check documentation for inconsistent mash step and yeast type terminology across different languages?

Yes, you can check documentation for inconsistent terminology by scanning files to enforce the correct and uniform application of mash steps, yeast types, and hop additions across different languages.

Why does my brewing documentation show inconsistent term usage between English and German translations?

Inconsistent term usage between English and German translations occurs when language-specific brewing vocabulary and units are not uniformly enforced, requiring validation to identify and correct documentation inaccuracies.