rabee-elkholy/android-harness-kit
Instructions file CodexOpenCode
Instructions for rabee-elkholy/android-harness-kit, covering android-harness-kit — agent instructions, environment, delivery gate (do not skip), on-demand specialists and phase boundaries & high-signal chat.
rabee-elkholy/android-harness-kit
Instructions file Gemini CLI
Instructions for rabee-elkholy/android-harness-kit: Follow AGENTS.md and .agents/rules/harness-rules.md. That file wins.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when working on this Android app architecture, Compose or XML UI, Room, performance, or daily checkout facts.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use before planning non-trivial features, new screens, or major refactors to explore architectural trade-offs, compare 2-3 design options, assess complexity/risks, and gather requirements before writing an implementation plan.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when inspecting or building Jetpack Compose UI for recomposition safety, stability (@Immutable/@Stable), RTL/LTR, remember/derivedStateOf, and Lazy list keys.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when the developer asks for a commit message or PR summary. The agent never commits or opens PRs.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when Gradle builds hang, lock on Windows, or a targeted :app assemble/test is enough instead of a full rebuild.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing in this Android app.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when diagnosing this Android app bugs, crashes, or unexpected UI behavior. Requires explicit hypotheses before code changes.
rabee-elkholy/android-harness-kit
Skill Claude CodeCodex
Use when developing business logic, UseCases, Repositories, ViewModels, or reproducing and fixing bugs using strict Red-Green-Refactor cycles. Requires writing and proving a failing test before writing implementation code.