Harness i18n Process

Inject i18n considerations into brainstorming, planning, and review workflows.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-i18n-process
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Harness i18n Process
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-i18n-process
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-i18n-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

i18n considerations are frequently overlooked during brainstorming, planning, and reviews, which can lead to missed translations, locale-specific formatting issues, and layout problems. Harness i18n Process ensures localization needs are raised and addressed at every stage by adapting prompts based on project configuration, locale targets, and industry context.

Core Features & Use Cases

  • Adaptive prompt-mode nudges to surface i18n questions during brainstorming, planning, and review.
  • Gate-mode validation that enforces i18n requirements when i18n.enabled is true, using target locales and strictness to determine severity.
  • Context-aware guidance drawn from harness.config.json and knowledge bases to tailor localization prompts by industry and locales.
  • Non-intrusive integration that respects workflows and does not scan source code directly; relies on artifacts like specs, plans, and reviews.
  • Real-world scenario: when planning a new checkout flow, prompts surface which strings need translation and where RTL considerations apply.

Quick Start

Run harness skill run harness-i18n-process to begin injecting localization considerations into your current workflow.

Frequently Asked Questions about Harness i18n Process

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

FAQPage Schema
How do I include localization considerations in brainstorming and planning workflows?

To include localization in brainstorming and planning, use adaptive prompt-mode nudges that surface i18n questions based on project configuration, target locales, and industry context. This ensures translation needs are addressed early without source code scanning.

What is gate-mode validation for i18n requirements?

Gate-mode validation enforces i18n requirements when i18n.enabled is true. It uses configured target locales and strictness settings to determine severity, ensuring localization needs are met during workflow reviews rather than just suggesting them.

Does i18n workflow integration scan source code directly?

No, i18n workflow integration does not scan source code directly. It relies on harness-i18n and knowledge bases, operating on artifacts like specs, plans, and reviews to inject localization considerations non-intrusively into existing processes.

How do I enforce RTL considerations when planning a checkout flow?

To enforce RTL considerations during checkout flow planning, enable gate mode with target locales configured. Context-aware guidance will surface specific string translation and layout requirements for those locales automatically.

Can I use harness.config.json to tailor localization prompts by industry?

Yes, you can use harness.config.json to tailor localization prompts. The skill draws context-aware guidance from this configuration file and knowledge bases to adapt i18n questions for specific industries and target locales.