> android-resources
Manage Strings, Drawables, and Localization resources on Android. Use when managing Android resources, drawables, or adding localization support. (triggers: strings.xml, **/*Screen.kt, stringResource, plurals, R.string)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/android-resources?format=md"Android Resources Standards
Priority: P2
Implementation Guidelines
Strings & Localization
- Define in XML: All UI text must be in
strings.xml. UsestringResource(R.string.*)in Compose. - Formatting: Use format args (
%s,%d) instead of concatenation. Useplurals(e.g.,<item quantity="one">) for quantity-sensitive strings. - Parity: Maintain Localizable.strings (iOS) parity where possible for shared features.
- Dynamic Access: Use
context.getString(R.string.id, args)for dynamic lookups.
Assets / Drawables
- Formats: Prefer VectorDrawables (
.xml) over RASTER images. Scale cleanly across density buckets (mdpi, hdpi, xhdpi, xxhdpi). - Plurals: Use
resources.getQuantityString(R.plurals.items, count, count)for quantity-sensitive strings. - Dark Mode: Support
Configuration.UI_MODE_NIGHTvia thevalues-night/qualifier orMaterialThemetokens. Never use hardcoded hex colors in Layouts/Composables. - Themes: Map all colors to Design Tokens (primary, surface, error) for consistent skinning.
Anti-Patterns
- No String Concatenation in UI: Use format args (
%s,%d) in strings.xml instead. - No Hardcoded UI Text: All visible strings must be defined in strings.xml.
References
> related_skills --same-repo
> common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app. (triggers: generate changelog, app store notes, play store release, what's new, release notes, ve
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)