string-resource-inline-comments

Add inline XML comments above touched Android string resources for translator context.

51|6|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/AniTrend/anitrend-v2 --skill string-resource-inline-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: string-resource-inline-comments
Source: https://github.com/AniTrend/anitrend-v2/tree/main/.agents/skills/string-resource-inline-comments
Command: npx skills add https://github.com/AniTrend/anitrend-v2 --skill string-resource-inline-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Android string resources include clear, inline XML comments so POEditor translators have the exact context needed to translate accurately.

Core Features & Use Cases

  • Translator-context comments for every touched resource: Adds an XML comment immediately above each touched <string>, including the on-screen purpose and any tone or constraints.
  • Placeholder and formatting clarity: Documents placeholder variables like %1$s and describes what they represent to prevent mistranslation.
  • Reliable scope across resource types: Extends guidance to styled text, arrays, escaping, plurals, and other Android string resource features referenced in the skill instructions.

Quick Start

Use this skill to audit a strings.xml change and add a specific translator-context comment directly above each touched string resource block.

Frequently Asked Questions about string-resource-inline-comments

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

FAQPage Schema
How do I add translator context comments to Android strings.xml resources?

To add translator context to strings.xml, insert an XML comment immediately above each touched resource block documenting screen usage, tone, and placeholder variables like %1$s to provide POEditor translators with necessary localization context.

Why do POEditor translators need inline XML comments for Android string resources?

POEditor translators need inline XML comments because Android string resources often contain placeholders and formatting that lack context. Comments document what %1$s variables represent and describe on-screen purpose, preventing mistranslation.

What's the best way to document Android string placeholders for localization?

The best way to document Android string placeholders for localization is adding an inline XML comment directly above each resource block that describes the variable type, such as %1$s, and explains its meaning within the screen context.

Does adding strings.xml comments work with plurals and string arrays?

Yes, adding strings.xml comments works with plurals, string arrays, and styled text. The process extends to all Android string resource features by placing context comments above each touched block to ensure translator clarity.

When do I need to add inline comments to strings.xml during development?

You need to add inline comments to strings.xml when auditing or editing any resource entries during development. Validate that no touched resources remain uncommented to maintain consistent localization quality for POEditor translators.