rajedev
UserPracticed the claude features to build this simple app.
Categories
Indexed Skills (5)
android-development
Comprehensive coding skill for Android projects using Kotlin, Jetpack Compose, Hilt DI, multi-module Clean Architecture, and MVVM. Use this when asked to create, edit, debug, test, or refactor any Android code — including features, ViewModels, composables, repositories, use cases, Gradle files, and tests. Also use this when setting up a new Android project or module.
android-location-services
Use this skill whenever building or reviewing an Android feature that needs the device's current location — permission requesting, FusedLocationProviderClient usage, reverse geocoding (coordinates to place name), or graceful fallback when location is denied/unavailable. Trigger for ANY domain that uses "current location" as one input among others — weather, delivery/ride tracking, local search, fitness route logging, store locators — not just navigation apps. Also trigger on mentions of "use my location", "current location", "GPS", "FusedLocationProviderClient", "reverse geocode", "location permission", or "location not available" in an Android/Kotlin context. This is a feature/capability skill (the pattern for HOW to request, fetch, resolve, and degrade), not a tech-stack tutorial — pair it with whatever DI/architecture the project already uses.
android-offline-first-sync
Use this skill whenever building or reviewing an Android feature that involves offline-first data (DB as source of truth), periodic/background sync (WorkManager), cache staleness/TTL policy, or condition-based alerts/notifications (e.g. extreme weather, price drops, stock-outs, low battery). Trigger this for ANY Android app domain — weather, fitness, news, finance, IoT, delivery tracking — not just weather specifically. Also trigger when the user mentions "offline mode", "offline-first", "cache invalidation", "periodic sync", "background refresh", "stale data", "sync status", "WorkManager", or "alert system" in an Android/Kotlin context. This is a feature/capability skill (the pattern of HOW to build the behavior), not a tech-stack tutorial — pair it with whatever networking/DB/DI libraries the project already uses.
android-weather-adaptive-theming
Use this skill whenever building or extending a weather app's UI where the visual theme (colors, icon, surface tint) should reflect the current weather condition — hot, sunny, rainy, cloudy, winter/snow, night, etc. Trigger on mentions of "weather theme", "dynamic weather colors", "mood-based UI", "condition-based background/theme", or when adding a new screen/component to an existing weather app that should stay visually consistent with the app's weather-driven theming. Also trigger when the request is to add a new weather mood/condition, a new screen that displays weather data, or a widget/component that should pick up the current theme. This is a UI/design-system skill scoped to one app's theming layer — pair with whatever Compose/architecture conventions the project already uses.
openweathermap-api-integration
Use this skill whenever integrating OpenWeatherMap's free-tier API into an app — current weather, 5-day/3-hour forecast, geocoding (city name to coordinates and back), or securely configuring the API key (local.properties, BuildConfig, request interceptor). Trigger on mentions of "OpenWeatherMap", "openweathermap.org", "forecast5", "data/2.5/weather", "data/2.5/forecast", "geo/1.0/direct", "geo/1.0/reverse", "OWM", or "OpenWeatherMap API key". Also trigger for the general technique of aggregating interval-based forecast data (e.g. 3-hourly) into daily buckets, which generalizes beyond weather to any interval-sampled forecast/timeseries API. Covers the free endpoints, which name/ID-based lookups are deprecated in favor of geocoding, the client-side daily-aggregation logic the free tier requires, and safe API key storage. Not a tech-stack tutorial — pair with whatever networking/DI/caching pattern the project already uses (e.g. an offline-first caching skill).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.