메뉴
How to correctly handle custom dates for extra subscription payments using MaterialDatePicker.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.