android-studio
Android Studio IDE with emulator and profiler. Use for Android development.
Best use case
android-studio is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Android Studio IDE with emulator and profiler. Use for Android development.
Teams using android-studio should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-studio/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-studio Compares
| Feature / Agent | android-studio | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Android Studio IDE with emulator and profiler. Use for Android development.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android Studio Android Studio is built on IntelliJ IDEA. 2025 versions (Narwhal/Otter) feature **Gemini** for code generation and crash analysis. ## When to Use - **Android Apps**: Native Android development (Kotlin/Java). - **Compose**: "Live Edit" allows UI updates in real-time on devices/emulators. - **Profiling**: Inspecting memory leaks and battery usage. ## Core Concepts ### Gradle The build system. `build.gradle.kts` (Kotlin DSL) is the standard in 2025. ### Emulator Virtual Android device. 2025 emulators are resizable and support foldable postures. ### Logcat v2 The logging window. Colored, filterable, and queryable logic. ## Best Practices (2025) **Do**: - **Use Gemini**: "Explain this crash" in Logcat sends the stack trace to Gemini for analysis. - **Use Baseline Profiles**: Generate profiles to improve app startup time. - **Use App Quality Insights**: View Crashlytics issues directly in the IDE code editor. **Don't**: - **Don't hardcode Strings**: Use `strings.xml`. The IDE warns you for a reason. ## References - [Android Studio User Guide](https://developer.android.com/studio/intro)
Related Skills
visual-studio
Visual Studio IDE for Windows with debugging and profiling. Use for .NET development.
android-sdk
Android SDK development tools. Use for native Android.
template
Expert [skill-name] assistance covering [feature 1], [feature 2], and [feature 3]. Use when [working with X], [debugging Y], or [implementing Z].
zsh
Zsh shell with oh-my-zsh. Use for terminal shell.
zed
Zed high-performance collaborative editor. Use for fast editing.
xcode
Xcode Apple development IDE with simulators. Use for iOS/macOS development.
webstorm
WebStorm JavaScript IDE with debugging. Use for web development.
webpack
Webpack module bundler with loaders and plugins. Use for bundling.
warp
Warp modern terminal with AI. Use for terminal work.
vscode
Visual Studio Code editor with extensions and debugging. Use for code editing.
vite
Vite fast build tool with HMR. Use for modern frontend builds.
vim
Vim text editor with motions, macros, and plugins. Use for terminal editing.