skills.rest
hardisgroupcom
hardisgroupcomOFFICIAL
Explore all skills by this author →
WebsiteGitHub

i18n-usage

Standardize i18n usage in sfdx-hardis TypeScript source files.

368|98|Updated Jan 25, 2021
Search Tags:#typescript#localization#i18n#prompts#translations#markers#uxlog
One-click install
npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill i18n-usage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-usage
Source: https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/i18n-usage
Command: npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill i18n-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides patterns and examples to ensure consistent internationalization usage across the sfdx-hardis codebase, avoiding hardcoded strings and enabling translations.

Core Features & Use Cases

  • Enforces using the i18n helper t() for user-visible strings in UX logging, prompts, and UI components.
  • Provides reusable patterns for translating common UI messages, log outputs, and table headers.
  • Covers usage patterns for uxLog, uxLogTable, prompts(), and marker strings to keep translations centralized and maintainable.

Quick Start

Replace hardcoded strings with translation keys using the t() function and ensure all UI text is sourced from i18n resources.

Frequently Asked Questions about i18n-usage

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

FAQPage Schema
How do I replace hardcoded strings with i18n translation keys in TypeScript?▼

To replace hardcoded strings with i18n translation keys in TypeScript, use the t() function from i18n utilities to source UI text from translation resources. This ensures all user-visible strings are centralized and maintainable.

What is the best way to standardize localization patterns for UX logging and prompts?▼

Standardizing localization patterns for UX logging and prompts involves enforcing the t() helper function across uxLog, uxLogTable, and prompts(). This keeps translations centralized and prevents hardcoded strings in user-facing outputs.

Can I use the i18n t() function for table headers and log outputs in TypeScript files?▼

Yes, you can use the i18n t() function for table headers and log outputs in TypeScript files. The Skill provides reusable patterns for translating common UI messages, log outputs, and table headers to maintain consistency.

When do I need to use translation markers in my codebase?▼

You need to use translation markers when defining user-visible strings in UX logging, prompts, and UI components. Markers work with the t() function to replace hardcoded strings and keep translations centralized and maintainable.

Does this i18n usage skill work without any external dependencies?▼

Yes, this i18n usage skill works without external dependencies. It provides patterns and examples to enforce consistent internationalization usage across the codebase using the built-in t() function and translation resources.

Related Skills

Explore More Software Engineering Skills→
DexploarerDexploarer
6

translation-key-extractor

Extract hardcoded strings and generate dot-notated translation keys.

Community
Intermediate
rampstackcorampstackco
523

internationalization

Plan and execute multi-language, multi-region website localization using a five-layer framework.

Official
Advanced
cyhinversecyhinverse

i18n-localization

Detect hardcoded strings and missing locale keys in React, Vue, and Python codebases.

Community
Intermediate
szejingszejing
1

i18n-translation

Translate UI strings and validation messages in the Wemotoo CRM Portal.

Community
Intermediate