b2c-android-string-resource

Enforce string resource conventions and snake_case prefixes in B2C Android apps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-android-string-resource
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-android-string-resource
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-Android/string-resource
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-android-string-resource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and centralizes string resources for B2C Android multi-module projects, preventing hard-coded text and inconsistent naming.

Core Features & Use Cases

  • Enforces string resource conventions across feature modules (strings.xml placement by feature, and shared core/ common strings).
  • Guides replacement of hard-coded text with stringResource calls to support localization and consistency.
  • Use Case: When adding UI text for new features, follow the {feature}{screen}{purpose} naming, and place strings in the appropriate strings.xml file, avoiding duplication.

Quick Start

Place your first string following the convention and ensure it resides in the target module's strings.xml.

Frequently Asked Questions about b2c-android-string-resource

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

FAQPage Schema
How do I standardize Android string resources across multiple feature modules?

Standardize Android string resources by applying naming conventions like {feature}_{screen}_{purpose} and centralizing text in feature-specific or shared core strings.xml files to prevent hard-coded values.

What is the naming convention for strings.xml entries in B2C Android apps?

The naming convention for strings.xml entries uses a {feature}_{screen}_{purpose} format with snake_case prefixes, ensuring consistent string identification and reuse across shared core and feature modules.

How do I replace hard-coded text with stringResource calls for Android localization?

Replace hard-coded text by moving UI strings into the target module's strings.xml file and referencing them with stringResource calls, supporting i18n and consistency across the Android app.

Does this string resource convention work for multi-module Android projects?

The convention works for multi-module Android projects by separating strings.xml placement by feature and managing shared common strings, ensuring consistent resource management across all modules.

Where should I place shared string resources in an Android multi-module architecture?

Place shared string resources in core or common strings.xml files, while feature-specific text goes into the respective feature module's strings.xml to maintain separation and prevent duplication.