Menú
Guidelines for compiling Varisankya from the CLI without Android Studio.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Guidelines for managing Varisankya releases across Beta and Production tracks.
How to safely record extra payments without advancing the Varisankya subscription next due date.
Instructions for extracting the Play Store upload keystore, Firebase JSON, and passwords from Bitwarden.
Standard operating procedure for concluding an AI agent session and ensuring workspace integrity.
How to correctly handle custom dates for extra subscription payments using MaterialDatePicker.
Guidelines for implementing M3 Expressive (M3E) animations, transitions, and touch physics in Varisankya.
| name | Headless Linux Android Builds |
| description | Guidelines for compiling Varisankya from the CLI without Android Studio. |
Varisankya is now built headlessly using the Gemini CLI on an Ubuntu environment. Android Studio is not required.
~/Android/Sdk.ANDROID_HOME is set globally in ~/.bashrc.local.properties contains sdk.dir=/home/aarsh/Android/Sdk.Run Gradle non-interactively using the CLI wrapper.
./gradlew assembleDebug (Outputs to app/build/outputs/apk/debug/app-debug.apk)./gradlew assembleRelease (Outputs to app/build/outputs/apk/release/app-release.apk)If the build fails complaining about "SDK location not found", ensure local.properties exists in the workspace root with the correct sdk.dir definition.
Always build the app completely (assembleDebug or assembleRelease) to empirically validate code changes. Do not assume syntax is correct without compilation.