ArisGuimera/MobiAI-Core

alpha-skill

first community fixture skill

Source text: Undetermined

bravo-skill

second community fixture skill

Source text: Undetermined

charlie-skill

third community fixture skill

Source text: Undetermined

mobiai-update

Actualiza el binario `mobiai` a la última versión publicada en GitHub Releases. Usá esta skill cuando el banner de SessionStart muestre "MobiAI update available" o cuando el usuario pida explícitamente actualizar MobiAI.

Source text: Spanish

using-mobiai

Use when starting any conversation — establishes how to find and invoke MobiAI skills, requiring `Skill` tool invocation before ANY response including clarifying questions, git/file reads, or code exploration

android-build

test fixture

Source text: Undetermined

edge-to-edge

test fixture

Source text: Undetermined

using-mobiai

test fixture

Source text: Undetermined

ios-build

test fixture

Source text: Undetermined

kmp-shared

test fixture

Source text: Undetermined

agp-9-upgrade

Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.

migrate-xml-views-to-jetpack-compose

Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to…

navigation-3

Learn how to install and migrate to Jetpack Navigation 3, and how to implement features and patterns such as deep links, multiple backstacks, scenes (dialogs, bottom sheets, list-detail, two-pane, supporting pane), conditional navigation (such as logged-in…

play-billing-library-version-upgrade

Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

mobiai-android-architecture

Use when creating features, refactoring, or navigating an Android codebase — understand project structure, find where to make changes, follow existing patterns.

mobiai-android-build

Use when building an Android project, configuring flavors or variants, troubleshooting build failures, or managing Gradle dependencies.

mobiai-android-device

Use when interacting with an Android device or emulator — run adb commands, automate UI, capture screenshots, read logcat, manage emulators.

mobiai-android-testing

Use when writing or running tests in an Android project — unit tests, UI tests, choosing the right framework and patterns.

mobiai-analyze-crash

Use when the user shares a crash from any source (stack trace, log, screenshot, error description) and wants to find the root cause and fix it.

mobiai-brain

Use when the user asks about past decisions, workarounds, bugfixes, testing patterns or integrations specific to *this* project, OR before proposing non-trivial architecture/integration changes. MobiAI Brain is per-project living memory at…

mobiai-crashlytics

Use when the user shares a Firebase Crashlytics crash link, crash ID, or asks to investigate a Crashlytics issue in depth.

mobiai-create-pr

YOU MUST use this before ANY git push, branch push to remote, merge, or PR creation — regardless of phrasing or language. Covers all irreversible integration actions (committing, pushing, opening a PR, shipping finished work). Also triggers proactively after…

mobiai-fix-issue

You MUST use this before starting any bug fix from a ticket or issue, OR when re-opening a ticket whose previous fix attempt didn't work (user shares a commit SHA and says 'no anda' / 'didn't fix it' / 'still broken'). Fetch, understand, investigate root…

mobiai-graph

Use when the user asks about code impact, call graph, callers/callees, semantic exploration of the mobile codebase, or 'where is X used'. Routes the agent to query MobiAI Graph (mobiai graph search/callers/context) instead of grep/read. Pre-flight checks that…

Source text: Spanish

mobiai-mobile-brainstorming

You MUST use this before any creative mobile work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

mobiai-mobile-debugging

You MUST use this before proposing any fix for a mobile bug, test failure, crash, or unexpected behavior — AND when re-investigating a bug whose previous fix didn't work (user shares a commit SHA and questions whether it resolves the bug). Walks root-cause…

mobiai-mobile-executing-plans

ALWAYS invoke this when a written mobile implementation plan exists and you are about to carry it out in a fresh session. Load and critique the plan before executing any task from it.

mobiai-mobile-executing-plans-with-subagents

ALWAYS invoke this when executing a mobile implementation plan in the current session with subagent support available. Drives fresh-subagent-per-task execution with mandatory two-stage review; do not hand-execute plan tasks in-session when this workflow…

mobiai-mobile-finishing-branch

You MUST use this once mobile implementation is finished and you are about to integrate the work — merging, pushing, opening a PR, or cleaning up the branch. Do not improvise the wrap-up; this skill gates verification, presents integration options, and…

mobiai-mobile-parallel-agents

ALWAYS invoke this before dispatching agents for two or more independent mobile problems (unrelated failures, separate subsystems, disjoint investigations). Do not spawn parallel agents ad hoc — this skill defines how to isolate their context and scope.

mobiai-mobile-planning

You MUST use this whenever a mobile task spans multiple steps, files, or subsystems — before touching code. Produce a written plan the user approves; do not improvise multi-step work from memory.

mobiai-mobile-tdd

You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.

mobiai-mobile-verification

You MUST use this before declaring any mobile work done, fixed, green, or ready — and before committing, pushing, or opening a PR. No completion claim may be made without fresh verification evidence from this session.

mobiai-mobile-worktrees

You MUST use this before starting mobile work that needs isolation from the current workspace — new feature branches, parallel efforts, or any plan execution that should not contaminate the active tree. Do not create worktrees ad hoc; this skill enforces safe…

mobiai-reproduce-bug

Use when the user wants to reproduce a bug on a mobile device, emulator, or simulator using UI automation.

mobiai-review-code

Use when reviewing mobile code changes — check for lifecycle issues, memory leaks, thread safety, and platform-specific pitfalls.

mobiai-write-tests

Use when the user asks to write tests for mobile code, or after applying a fix that needs regression tests.

mobiai-writing-skills

Guide the user through creating a new MobiAI skill — generate SKILL.md with proper structure, frontmatter, and actionable instructions.

mobiai-flutter

Use when working on a Flutter or Dart project — building, testing, debugging, understanding state management and project structure.

mobiai-ios-architecture

Use when creating features, refactoring, or navigating an iOS codebase — understand project structure, find where to make changes, follow existing patterns.