Menú
How to correctly handle custom dates for extra subscription payments using MaterialDatePicker.
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.
Guidelines for compiling Varisankya from the CLI without Android Studio.
Guidelines for implementing M3 Expressive (M3E) animations, transitions, and touch physics in Varisankya.
| name | Payment Date Prompting |
| description | How to correctly handle custom dates for extra subscription payments using MaterialDatePicker. |
When implementing custom payment entries (like "Add Extra Payment") in Varisankya, the date of the payment should never be hardcoded to Date() (today) automatically to match the standard behavior.
For standard "Mark as Paid" actions, the speed of one-tap recording is preferred. However, explicit extra payments require precision.
MaterialDatePicker.newBuilder().datePicker() initialized to MaterialDatePicker.todayInUtcMilliseconds().val calendar = Calendar.getInstance(TimeZone.getTimeZone("UTC"))
calendar.timeInMillis = timestamp
val selectedDate = calendar.time
selectedDate along with a null nextDueDate into the payment recording batch function.