android-design-guidelines

Overview of android-design-guidelines skill

What this skill does

The android-design-guidelines skill is a practical Android UI decision aid for Material Design 3, Jetpack Compose, and XML-based layouts. It helps you turn a rough UI task into platform-correct implementation choices for theming, navigation, accessibility, adaptive layouts, and core components.

Who should use it

Use the android-design-guidelines skill if you are building or reviewing Android screens, migrating toward Material You, or trying to avoid platform mistakes that break consistency or accessibility. It is especially useful for product teams that need guidance for android-design-guidelines for UI Design rather than abstract design theory.

What it is best at

This skill is strongest when you need concrete guidance on how Android UI should behave: dynamic color, color roles, predictive back, touch target sizing, font scaling, and responsive layout patterns. It is a better fit than a generic prompt when you need implementation-aware guidance that works across Compose and XML.

How to Use android-design-guidelines skill

Install it and locate the rule map

Run the android-design-guidelines install command used by your skills manager, then open the repository context in skills/android. Start with SKILL.md, then read AGENTS.md, metadata.json, and rules/_sections.md to understand the rule structure before asking for help on a specific screen or feature.

Give the skill a real Android task

The skill works best when you provide a screen type, API level, UI toolkit, and constraint set. For example, ask for a Compose theme for Android 12+, a navigation pattern for a tablet app, or an accessibility review of a custom component. Vague prompts like “improve this UI” produce weaker results than a focused android-design-guidelines usage request such as: “Review this Compose settings screen for Material 3 compliance, dynamic color, and TalkBack issues.”

Read the right files first

Use rules/_sections.md to jump to the relevant category, then inspect the matching rule group in SKILL.md and any notes in AGENTS.md. If you are working on theming, navigation, or accessibility, those sections usually determine whether the output is usable. This repository is light on support files, so the main value comes from the rule body and section index rather than a large reference tree.

Prompt for constraints, not just design ideas

Strong inputs mention platform version, layout form factor, and implementation style. A better prompt is: “Design a Material 3 Compose screen for a photo app on Android 14, with dynamic color, bottom navigation, large-text support, and no custom brand colors.” That gives the android-design-guidelines skill enough context to return choices that match Android conventions and avoid hidden conflicts.

android-design-guidelines skill FAQ

Is this only for design work?

No. The android-design-guidelines skill is for design decisions that affect implementation. It is useful when you need guidance that developers can apply directly in Compose or XML, especially for android-design-guidelines usage in production apps.

Should I use this instead of writing a normal prompt?

Use the skill when you want fewer Android-specific errors and more consistent platform behavior. A plain prompt can suggest UI ideas, but it often misses requirements like dynamic color fallbacks, touch target minimums, or navigation conventions.

Is it beginner-friendly?

Yes, if you are working on a specific screen or component. The skill is easiest to use when you already know the task, such as “build a settings page” or “fix this accessibility issue.” It is less helpful if you have no Android context at all.

When should I not use it?

Do not rely on it for non-Android design systems, marketing site layouts, or iOS-specific interaction patterns. It is also not the right tool if you need product strategy or visual branding exploration without platform constraints.

How to Improve android-design-guidelines skill

Start with the highest-risk rule areas

The biggest quality gains usually come from correct theming, navigation, and accessibility. When using android-design-guidelines guide, explicitly state whether you need Material You, predictive back, tablet adaptation, or screen-reader support so the skill can prioritize the rules that most affect correctness.

Provide the screen context the rules depend on

The skill gives better results when you include: Compose vs XML, target API level, phone vs tablet, dark mode requirements, and whether the screen uses custom drawing or standard Material components. That context helps it avoid generic advice and choose the right Android patterns.

Ask for a review, then iterate

A good workflow is to ask for an initial implementation plan, apply it, then request a second pass for violations such as hardcoded colors, improper text sizing, weak focus order, or bad navigation placement. This is where android-design-guidelines skill output becomes most useful: it can catch structural issues that are easy to miss in a first draft.

Use concrete inputs to get concrete fixes

Instead of “make it accessible,” provide the failure mode: “This Compose card has icon-only actions, 36dp touch targets, and custom canvas drawing; show what to change for Material 3 compliance.” Specificity improves the answer because the skill can map your issue to the actual rule set instead of guessing the intent.