Menu
SkillsMP has collected 15 skills from Al-Qassim/Android-Studio-Lite. Open a skill to review its source and details.
Showing 15 of 15 collected skills.
Structures feature UI and domain code: thin app navigation, state-only ViewModels, Screen Context for busy screens, shallow UI trees, multi-state previews, validation in the data layer exposed via API, and user-safe errors. Use when adding or refactoring a…
Implement a piece of work from a spec or tickets. Use when the user asks to implement, build, code, or ship a feature/ticket — especially feature UI, navigation, or data layers. Mandates /structure-feature-code for screen shape.
Incremental PR delivery — one focused commit, push, then PR comment. Use when the user asks to commit/push/comment incrementally on an open PR (or to ship a review-fix slice that way).
Device-truth design review against the in-repo design system. Screenshot the running app, compare to :designsystem tokens/components and intended states, fix gaps, re-capture, post Before|After. Use when finishing UI work, before merge (Finish reviews), or…
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma',…
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark…
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write…
Independent visual critic for Figma against Int UI Kit. Use after a design author finishes a flow or Design System page, before board Ready, or when verifying Kit vs Candidate. Never run as the same agent that drew the UI.
General Figma design workflow: find the project's design contract, reuse the design system, edit via Figma MCP, finish with screenshot evidence for an independent critic. Use when making or fixing Figma designs, flows, or screens. Ignore for pure code/git…
Design ASL screens in the JetBrains New UI / Islands spirit using the Int UI Kit. Use when redesigning against JetBrains New UI, Int UI Kit, Android Studio family chrome, Islands theme, or when the locked visual direction is JetBrains.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.