菜单
Read this guideline when working with KRD schemas, writing converters or mappers, designing specs that reference KRD fields, or generating GCN/FIT/TCX output. Also read when files are under packages/core/src/domain/schemas/ or contain KRD field references.
用 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 | krd-format |
| description | Read this guideline when working with KRD schemas, writing converters or mappers, designing specs that reference KRD fields, or generating GCN/FIT/TCX output. Also read when files are under packages/core/src/domain/schemas/ or contain KRD field references. |
KRD (Kaiord Representation Definition) is the canonical format. All conversions MUST pass through KRD. Direct format-to-format conversion is forbidden.
MIME type: application/vnd.kaiord+json
Normative reference: openspec/specs/krd-format/spec.md. Live Zod schemas: packages/core/src/domain/schemas/.
version (required)
type (required)
metadata (required)
sessions (optional)
laps (optional)
records (optional)
events (optional)
extensions (optional)
type enumOne of: "structured_workout" | "recorded_activity" | "course"
Adding a new value is a breaking change and requires a migration plan.
| Layer | Field names | Enum values |
|---|---|---|
| KRD (domain) | camelCase — subSport, durationType, heartRate | snake_case — "indoor_cycling", "lap_swimming" |
| Adapters (internal) | camelCase allowed | MUST emit snake_case in KRD output |
Access enum values via .enum: subSportSchema.enum.indoor_cycling
Reserved: extensions.structured_workout, extensions.fit, extensions.course, extensions.course_points
Adapters MUST NOT drop unknown namespaces silently. They MUST either round-trip them unchanged or fail with a descriptive error. Per-namespace payload shapes: openspec/specs/krd-format/spec.md, Requirement: Extension Namespaces.
| Field | Tolerance |
|---|---|
| Time | ±1 second |
| Power | ±1 watt or ±1% FTP |
| Heart Rate | ±1 bpm |
| Cadence | ±1 rpm |
| Distance | ±1 meter |
Every converter that touches a numeric field MUST have round-trip tests within these tolerances.
packages/core/src/domain/schemas/ — exported via @kaiord/core. Import schemas from there; never re-declare them in adapter packages.