fluent-syntax-terms

Define and reference Fluent terms in FTL for consistent branding.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package --skill fluent-syntax-terms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fluent-syntax-terms
Source: https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package/tree/main/skills/source/fluent-syntax/fluent-syntax-terms
Command: npx skills add https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package --skill fluent-syntax-terms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fluent terms (-term-name) are internal vocabulary used to ensure brand consistency and prevent direct runtime access to terms. This skill clarifies how to define, reference, and constrain terms within Fluent Translation Language (FTL) to avoid exposing internal identifiers in applications.

Core Features & Use Cases

  • Define reusable terms with a hyphen prefix (e.g., -brand-name) and reference them in messages.
  • Support parameterized terms with named arguments for grammatical variations and localization grammars.
  • Attach term attributes to drive FTL-based selectors without exposing attributes in runtime APIs.
  • Use in scenarios like brand names, product vocabularies, or multilingual UI copy to maintain consistency across locales.

Quick Start

Define -brand-name = Firefox and reference it in a message as { -brand-name } to ensure consistent branding.

Frequently Asked Questions about fluent-syntax-terms

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

FAQPage Schema
How do I define and reference Fluent terms in FTL for consistent branding?

Define Fluent terms with a hyphen prefix like -brand-name = Firefox, then reference them in messages using { -brand-name } syntax. This ensures consistent branding across locales and prevents direct runtime access to internal vocabulary identifiers in your application.

What are Fluent terms and when do I need them in localization workflows?

Fluent terms are internal vocabulary prefixed with a hyphen used to ensure brand consistency and prevent direct runtime access to internal identifiers. You need them when maintaining consistent product names, brand vocabulary, or multilingual UI copy across different locales.

Can I use parameterized terms with named arguments for grammatical variations?

Yes, Fluent terms support parameterized definitions with named arguments to handle grammatical variations and localization grammars. This allows terms to adapt their form based on context while keeping internal identifiers hidden from runtime APIs.

How do term attributes work for FTL selectors without exposing them at runtime?

Term attributes can be attached to Fluent terms to drive FTL-based selectors within translation files. These attributes remain internal to the localization system and are not exposed through runtime APIs, keeping your application layer clean and secure.

Does this approach work for multilingual UI copy across different locales?

Yes, Fluent terms are designed specifically for scenarios like brand names, product vocabularies, and multilingual UI copy. They maintain consistency across locales while enforcing term grammar and safe referencing within Fluent localization workflows.

Why should I use Fluent terms instead of exposing internal identifiers directly?

Fluent terms prevent runtime exposure of internal identifiers by keeping them internal to the FTL localization layer. This protects your application architecture while ensuring brand consistency and vocabulary standardization across all supported locales.