Organize Android strings, drawables, fonts, themes, localization, and concrete resource-backed Compose values such as MaterialTheme colors. Use for resource declarations and their direct UI lookup; defer design-system token architecture, network image loading, lint-rule configuration, and general Compose implementation.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
strings.xml. Use stringResource(R.string.*) in Compose.%s, %d) instead of concatenation. Use plurals (e.g., <item quantity="one">) for quantity-sensitive strings.context.getString(R.string.id, args) for dynamic lookups..xml) over RASTER images. Scale cleanly across density buckets (mdpi, hdpi, xhdpi, xxhdpi).resources.getQuantityString(R.plurals.items, count, count) for quantity-sensitive strings.Configuration.UI_MODE_NIGHT via values-night/ qualifier or MaterialTheme tokens. Never use hardcoded hex colors in Layouts/Composables.%s, %d) in strings.xml instead.When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
405cdd5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.