بنقرة واحدة
android-15-standards
Guidelines for maintaining strict Android 15 (SDK 35) compliance in Varisankya.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Guidelines for maintaining strict Android 15 (SDK 35) compliance in Varisankya.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
How to correctly handle custom dates for extra subscription payments using MaterialDatePicker.
استنادا إلى تصنيف SOC المهني
| name | Android 15 Standards |
| description | Guidelines for maintaining strict Android 15 (SDK 35) compliance in Varisankya. |
Varisankya is a showcase of modern Android development, strictly enforcing minSdk = 35 (Android 15). This skill outlines the technical and architectural reasons for this decision and the standards it imposes.
Android 15 makes edge-to-edge layout mandatory. Varisankya embraces this proactively:
fitsSystemWindows.WindowCompat.setDecorFitsSystemWindows(window, false) and enableEdgeToEdge() in BaseActivity.Targeting SDK 35 allows us to use the strictest security defaults without backward compatibility layers:
androidx.credentials exclusively for authentication (Google Sign-In). Legacy GoogleSignInClient is banned.androidx.biometric with strict BIOMETRIC_STRONG requirements.The minSdk 35 requirement is a strategic choice to avoid technical debt:
HapticFeedbackConstants introduced in newer APIs (e.g., CONFIRM, REJECT) freely.