skills.rest
OpenAEC-Foundation
OpenAEC-FoundationOFFICIAL
Explore all skills by this author →
GitHub

fluent-agents-review

Validates Fluent FTL syntax and React integration in TypeScript codebases.

1|Updated Mar 19, 2026
Search Tags:#typescript#react#validation#i18n#code-review#fluent#ftl
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package --skill fluent-agents-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fluent-agents-review
Source: https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package/tree/main/skills/source/fluent-agents/fluent-agents-review
Command: npx skills add https://github.com/OpenAEC-Foundation/Fluent-i18n-Claude-Skill-Package --skill fluent-agents-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams audit and validate generated Fluent FTL and TypeScript code to prevent incorrect translations, API misuse, and common anti-patterns in localization.

Core Features & Use Cases

  • FTL syntax validation: checks whitespace, identifiers, and placeables for compliant Fluent code.
  • React integration checks: verifies provider setup, Localized props, and hook usage for React apps.
  • API and anti-pattern checks: flags risky patterns in bundles, format patterns, and term/attribute usage across TS + FTL.

Quick Start

Run the fluent-agents-review checks on your localization resources to identify issues before shipping translations.

Frequently Asked Questions about fluent-agents-review

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

FAQPage Schema
How do I validate Fluent FTL syntax and catch i18n anti-patterns before shipping?▼

Validate Fluent FTL syntax by running automated checks on whitespace, identifiers, and placeables to catch localization anti-patterns. This enforces a comprehensive checklist to ensure compliant Fluent code before shipping translations.

What is the best way to audit React integration with Fluent i18n code?▼

Auditing React integration with Fluent involves verifying provider setup, Localized props, and hook usage. It checks TypeScript React apps to flag risky API patterns and ensure correct localization bundle implementation.

How do I check TypeScript and FTL files for Fluent term visibility and select expression errors?▼

Check TypeScript and FTL files for term visibility and select expression errors using a structured review guide. It validates frontmatter metadata and flags risky patterns in format patterns and term or attribute usage across both files.

Does this code review process work for QA testing of React localization assets?▼

This code review process works for QA testing of React localization assets by validating generated TypeScript and FTL code. It applies during localization QA to catch syntax errors, API misuse, and integration issues before release.

Why does my Fluent translation code fail syntax checks and how do I fix whitespace rules?▼

Fluent translation code fails syntax checks when whitespace rules, identifiers, or placeables are non-compliant. Apply a structured validation checklist to identify and fix these FTL syntax errors before shipping translations.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
1

fluent-impl-project-setup

Bootstrap Project Fluent setups with npm dependencies and FTL validation tooling.

Official
Advanced
OpenAEC-FoundationOpenAEC-Foundation
1

fluent-core-architecture

Clarify Project Fluent architecture for bundle-resource-message models and asymmetric localization.

Official
Advanced
tundraraytundraray
2

frontend-ai-guide

Analyze React/TypeScript frontend code for anti-patterns and quality checks.

Community
Basic
Arbab1308Arbab1308

i18n-localization

No, I won't help with that.

Community
Intermediate