add-mobile-string
Use when the user asks to add a new Android string resource with translations to the CommCare Android project, given a string resource name and English text
What this skill does
# Add Android String Resource ## Overview Add a new `<string>` entry to all locale `strings.xml` files in the CommCare Android project, given a resource name and English text. ## Discovering Locales The English source lives at `app/res/values/strings.xml`. Translated locales live in sibling directories matching `app/res/values-*/strings.xml` (e.g., `values-es`, `values-fr`). Always enumerate the current set at runtime — do not assume a fixed list, since locales may be added or removed over time. Run this to list every locale `strings.xml` file: ```bash ls app/res/values*/strings.xml ``` The directory suffix after `values-` is the BCP 47 / Android locale code (e.g., `es` = Spanish, `fr` = French, `pt` = Portuguese). Translate accordingly. ## Workflow 1. **Enumerate locales:** Run the `ls` command above to get the full current set of locale files. 2. **Locate insertion point:** Grep for a nearby existing string with a similar prefix in `values/strings.xml` to find the right neighborhood. Place the new string near related entries. 3. **Read context around insertion point** in each locale file (the same neighboring strings may appear at different line numbers per locale). 4. **Add the English string** to `values/strings.xml`. 5. **Translate and add** to every other locale file discovered in step 1. Translate the English text into each language, matching the tone and style of surrounding strings in that file. 6. **Every locale gets the string** — do not skip any locale, even ones that have fewer existing strings. ## Format ```xml <string name="resource_name">Translated text here</string> ``` - Escape apostrophes with `\'` in XML. - Preserve any `%d`, `%s`, or other format specifiers exactly as in the English source. ## Common Mistakes - Skipping locales that have fewer translated strings — always include every locale returned by the discovery step, regardless of how sparse the file is. - Hard-coding a list of locales from memory instead of running the discovery command — the set of supported locales changes over time. - Placing the string at the end of the file instead of near related strings. - Forgetting to escape special XML characters in translations.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.