OpenParable
Skip to content
← Back to skills

I18n Vue Template

Development
i18n-vue-template

I18n Vue Template is an Agent Skill for development published in the rundeck/rundeck repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Internationalize Vue component templates by replacing all hardcoded strings with $t() calls and adding translations to i18n.ts or en_US.js. Use when asked to internationalize, i18n, or translate strings in Vue templates.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/rundeck/rundeck/blob/HEAD/.claude/skills/i18n-vue-template/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/i18n-vue-template, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Internationalize Vue Template Strings

Systematically replace all hardcoded strings in Vue component templates with i18n translation keys.


Phase 1: Audit

  1. Read the target Vue component fully
  2. Identify all hardcoded strings in:
    • Template: text within HTML tags (<p>Text</p>, <button>Click me</button>)
    • Template: bare interpolation without $t() ({{ 'hardcoded' }})
    • Script: data() properties containing display strings
  3. Document the count: "Found X hardcoded strings to internationalize"

Do not internationalize: CSS class names, HTML attributes, test IDs, prop values, dynamic content from variables.


Phase 2: Add Translation Keys

  1. Locate the translation file:
    • Within ui-trellis: find the nearest en_US.js file
    • Elsewhere: find the nearest i18n.ts file
  2. Add new keys under an appropriate namespace using camelCase
  3. Provide translations for all supported languages present in the file (at minimum English)
  4. Key naming examples:
    • "Search for a step" → searchForStep
    • "Node Steps" → nodeSteps

Phase 3: Replace in Template and Script

  • Template text: <p>Text</p> → <p>{{ $t('namespace.key') }}</p>
  • Data properties with display strings → move to computed, use this.$t()
// Before
data() {
  return { options: [{ name: 'Node Steps', value: 'step' }] }
}

// After
computed: {
  options() {
    return [{ name: this.$t('message.nodeSteps'), value: 'step' }]
  }
}

Phase 4: Verify

  1. Count remaining hardcoded strings — must be 0
  2. Run verification grep:
    grep -E '<(p|button|span)>[^{<]*[A-Z][a-z]+ [a-z]+[^}>]*</(p|button|span)>' [file]
    
  3. Report: "Internationalization complete: 0 hardcoded strings remaining (from X)"