Android Resources Agent Skill

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.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

536

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill android-resources

What comes with it

4 036 bytes besides the instruction

evals/evals.json

references/implementation.md

The instruction itself

8 sections, as written by the author

Android Resources Standards

Priority: P2 (MEDIUM)

Implementation Guidelines

Strings & Localization

Define in XML: All UI text must in strings.xml. Use stringResource(R.string.*) in Compose.
Formatting: Use format args (%s, %d) instead of concatenation. Use plurals (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_NIGHT via values-night/ qualifier or MaterialTheme tokens. 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 defined in strings.xml.

References

XML Structure

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

Other skills for the same job

different authors, same section of the catalogue

Theme Factory

by anthropics

vendor ×16

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts

Web Artifacts Builder

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

How to use it

Copy the folder

Take hoangnguyen0403/android-resources from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.