Product Terminology

You can maintain consistent terminology by using a centralized domain glossary that tracks definitions, rationales, and forbidden synonyms to prevent terminology drift across your project. It serves as a single source of truth for all team members.

The best way to prevent naming conflicts is through conflict-aware updates that proactively identify existing synonyms and naming collisions during the addition process. This stops terminology drift before it enters your codebase or documentation.

You set up a shared domain glossary by accessing your project session state to locate and maintain a dedicated markdown file. This file acts as the central repository for your domain vocabulary, definitions, and aliases.

Yes, the terminology management tool requires the pyyaml dependency to operate. It also requires access to the project session state to locate and update the glossary markdown file.

You need a domain-driven glossary for onboarding to eliminate ambiguity and communication silos. It ensures new team members use identical language for the same concepts, preventing confusion caused by using different names across features.

Yes, you can track forbidden synonyms and aliases in the project glossary. The system manages defined terms, their rationales, and explicitly forbidden synonyms to enforce a strict, shared domain vocabulary across your codebase.