菜单
Offline and degraded network behavior in TryRamadan. Covers cache-first prayer times, API failure/timeout for Aladhan and location/timezone, and what works offline (fasting log, journal, meals). Use when adding features that call external APIs or read/write cached data.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
TryRamadan app overview, performance optimizations, and resources. Use when making cross-cutting changes, adding dependencies, or optimizing build/runtime.
Fact-check and verify culture pages, traditions, and recipes; add and validate hyperlink sources; test authenticity of cultural and culinary claims. Use when adding or editing cultural-traditions.json, recipes.json, country pages, recipe pages, or any tradition/food/recipe content in TryRamadan.
Onboarding and re-onboarding flows in TryRamadan. Covers step order, persistence (draft vs final preferences), redirect to dashboard, and edge cases (abandonment, skip location, Muslim vs Non-Muslim path). Use when changing onboarding steps, routes, or completion logic.
Web performance and Core Web Vitals (LCP, INP, CLS) in TryRamadan. Covers critical path, lazy loading, images/fonts, and layout stability. Use when changing above-the-fold content, images, fonts, or heavy components on the main route.
Writing clear bug reports and converting bugs into regression tests in TryRamadan. Covers precise title, environment, numbered steps, expected vs actual, missing information, and BUG-<AREA>-<ID> test naming. Use when writing or rewriting bug reports, or when adding regression tests from a fixed bug.
Ramadan calendar (start/end, day number, year boundary), fasting states (completed/skipped/broken), streak and todayOverride in TryRamadan. Use when editing src/lib/ramadan.ts, fasting state transitions, streak calculation, or Ramadan day labels.
| name | offline-and-degraded-network |
| description | Offline and degraded network behavior in TryRamadan. Covers cache-first prayer times, API failure/timeout for Aladhan and location/timezone, and what works offline (fasting log, journal, meals). Use when adding features that call external APIs or read/write cached data. |
Use this skill when adding or changing API usage, caching, or location/timezone so the app behaves correctly offline and when APIs fail or time out.
| Dependency | API / source | Cache key / storage | Used for |
|---|---|---|---|
| Prayer times (today) | Aladhan GET /v1/timings/{date}?latitude=&longitude= | tryramadan-prayer-times-cache (date + lat + lng) | Suhoor end / Iftar, countdown, prayer strip |
| Prayer times (Ramadan month) | Aladhan calendar | tryramadan-ramadan-prayers (lat, lng, Ramadan year), 7-day max age | Schedule .ics export |
| Location (auto-detect) | geolocation → reverse geocode or ipapi.co | None (result in preferences) | lat/lng for prayer API |
| Location (search) | Nominatim | None | City search |
| Timezone | timeapi.io by coordinates | None (stored with location) | Display "today" and countdown |
Fasting progress, journal, meals: Local only (localStorage). Logging fast, complete/skipped/broken, journal, meals work offline once the app is loaded.
tryramadan-prayer-times-cache before fetch. If hit (same date, same lat/lng), use cache and do not call API. Ramadan month: read from tryramadan-ramadan-prayers; if valid cache exists, use it and do not fetch.docs/OFFLINE-AND-DEGRADED-NETWORK-FLOWS.md (flows, cache miss, first open offline, API failure, actions possible offline).