القائمة
Read this guideline when working on workout-spa-editor, React components, custom hooks, Zustand store, Dexie queries, or generating GCN workout targets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Read this guideline when creating commits, opening PRs, writing changeset descriptions, branching, or before running any git command that modifies history.
Read this guideline when placing new code in a layer, reviewing imports, designing a new package, adding I/O, or when files are under packages/core/src/, packages/fit/, packages/tcx/, packages/zwo/, packages/garmin/, packages/garmin-connect/, packages/cli/, packages/mcp/.
Generate a Garmin Connect (.gcn) workout file from a natural language description. Use when the user describes a training session, workout, or exercise plan and wants a .gcn file.
Read this guideline when writing tests, reviewing test code, or deciding what kind of test to write for a given layer. Also applies when files match **/*.test.{ts,tsx,js,mjs}.
Read this guideline when writing or reviewing TypeScript code, naming symbols, refactoring, deciding between type vs interface, or working with schemas, mappers, or converters.
Read this guideline when creating implementation tasks, doing TDD, deciding task order, or working on any feature with observable behavior.
| name | frontend-patterns |
| description | Read this guideline when working on workout-spa-editor, React components, custom hooks, Zustand store, Dexie queries, or generating GCN workout targets. |
| State type | Tool | Rule |
|---|---|---|
| Editor runtime (undo/redo, selection, clipboard) | Zustand (workout-store) | Never auto-persisted |
| Persisted data (workouts, templates, profiles, AI providers, sync state) | Dexie + useLiveQuery | One query per page |
| Ephemeral UI (modals, spinners) and shared runtime (bridge status) | React useState / useContext | — |
Rule: "Editor runtime → Zustand. Persisted data → Dexie. Local UI → React state."
Generic components MUST use the port/adapter pattern — never import platform-specific stores directly. A component that could be reused across contexts must receive data and callbacks via props, not by importing Zustand or Dexie internals.
zoneNumber maps to Garmin's default zones, not the user's custom zones. This causes NaN display in the Garmin Connect UI for pace and wrong zone values for HR and power.
Always use explicit targetValueOne / targetValueTwo with the zone's actual values (bpm, m/s, watts).
// WRONG
{ targetType: 'pace', zone: { zoneNumber: 2 } }
// CORRECT
{ targetType: 'pace', targetValueOne: 2.54, targetValueTwo: 2.86 }
This applies to all target types: pace, heart rate, and power.