Praxis Cron Schedule Authoring
Use this skill when the task is about schedule meaning, not just widget rendering. Treat ScheduleAuthoringConfig as the canonical Praxis schedule intent model inside @praxisui/cron-builder.
Source Audit
Before editing code or guidance, inspect:
projects/praxis-cron-builder/AGENTS.md
projects/praxis-cron-builder/README.md
projects/praxis-cron-builder/src/lib/schedule-contract.ts
projects/praxis-cron-builder/src/lib/schedule-normalizer.ts
projects/praxis-cron-builder/src/lib/schedule-authoring-runtime.ts
projects/praxis-cron-builder/src/lib/cron-runtime.ts
projects/praxis-cron-builder/src/lib/ai/praxis-cron-builder-authoring-manifest.ts
- focused
schedule-*, cron-runtime, and AI manifest specs
Canonical Boundary
schedule-contract.ts owns the public schedule vocabulary:
ScheduleAuthoringConfig
ScheduleKind
ScheduleRecurrence
ScheduleWindow
ScheduleExecutionPolicy
ScheduleGovernance
ScheduleDiagnostic
CronDialect
CRON_DIALECTS
schedule-normalizer.ts owns compatibility from legacy CRON strings to canonical schedule config. schedule-authoring-runtime.ts owns compile, validation, and preview orchestration. cron-runtime.ts owns expression parsing, humanization, and occurrence generation.
Do not create parallel host DTOs for schedule kind, dialect, timezone, preview, diagnostics, or execution policy when these contracts already carry the semantics.
Authoring Rules
- Model business schedule intent as
kind plus recurrence whenever possible.
- Use
kind='customCron' and expression.cron only when the user explicitly requires a raw expression or an unsupported recurrence.
- Preserve legacy string compatibility through
normalizeScheduleValue; do not delete the compatibility path unless the public contract is intentionally migrated.
- Compile structured recurrence with
compileScheduleExpression before writing a canonical expression or compatibility value.
- Run
validateScheduleAuthoringConfig before accepting recurrence, expression, window, timezone, or execution policy changes.
- Use
createSchedulePreview for preview and diagnostics; do not manually recompute next occurrences in consumers.
- Use
CRON_DIALECTS for field count, seconds/year support, named months/weekdays, question mark, last/nth weekday support, timezone mode, and day-of-month/day-of-week rules.
- Preserve dialect differences between Unix, Quartz, AWS EventBridge, Kubernetes CronJob, GitHub Actions schedule, and Google Cloud Scheduler.
- Keep one-time schedules explicit. Do not pretend
kind='once' has a portable CRON representation when diagnostics say it does not.
- Keep timezone as IANA timezone metadata unless the selected dialect has fixed UTC or host-local semantics.
Inventory Before New Contract
Classify requested behavior before adding fields:
ja-suportado-so-ux: existing diagnostics, preview, recurrence, window, or governance data is not surfaced clearly.
ja-suportado-mal-nomeado-ou-mal-materializado: a consumer stores CRON strings or local fields that should normalize to ScheduleAuthoringConfig.
suportado-parcialmente: existing config carries the intent but compile, preview, i18n, docs, or form projection needs completion.
lacuna-real-de-contrato: no current schedule config, dialect definition, execution policy, governance, diagnostics, or manifest operation can represent the required semantic decision.
For real contract gaps, name the canonical owner, affected package exports, consumers, docs/examples, AI manifest changes, and minimum proof before editing.
Validation
Use the smallest reliable proof:
schedule-normalizer.spec.ts
schedule-authoring-runtime.spec.ts
cron-runtime.spec.ts
pdx-cron-builder.component.spec.ts when compile/preview affects CVA round-trip
- AI manifest/adapter specs when operations or diagnostics change
npm run build:praxis-cron-builder when public types or exports change
Report exactly which dialects, schedule kinds, and invalid cases were covered.
Companion Skills
- Use
praxis-cron-builder-runtime for component UI, CVA, metadata, and preview rendering.
- Use
praxis-cron-builder-form-field for metadata-driven form integration and submit payload shape.
- Use
praxis-cron-builder-ai-validation for agentic operations, read-only validate/preview behavior, and registry contracts.
- Use
praxis-core-runtime-contracts only if schedule semantics are intentionally promoted from the package to shared core.
1---2name: praxis-cron-schedule-authoring3description: Use when Codex must model, change, audit, or validate Praxis schedule semantics around `@praxisui/cron-builder`, including `ScheduleAuthoringConfig`, `CronDialect`, `CRON_DIALECTS`, recurrence intent, `normalizeScheduleValue`, `compileScheduleExpression`, `validateScheduleAuthoringConfig`, `createSchedulePreview`, legacy CRON string compatibility, timezone, locale, diagnostics, or canonical schedule authoring decisions.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-cron-schedule-authoring6---78# Praxis Cron Schedule Authoring910Use this skill when the task is about schedule meaning, not just widget rendering. Treat `ScheduleAuthoringConfig` as the canonical Praxis schedule intent model inside `@praxisui/cron-builder`.1112## Source Audit1314Before editing code or guidance, inspect:1516- `projects/praxis-cron-builder/AGENTS.md`17- `projects/praxis-cron-builder/README.md`18- `projects/praxis-cron-builder/src/lib/schedule-contract.ts`19- `projects/praxis-cron-builder/src/lib/schedule-normalizer.ts`20- `projects/praxis-cron-builder/src/lib/schedule-authoring-runtime.ts`21- `projects/praxis-cron-builder/src/lib/cron-runtime.ts`22- `projects/praxis-cron-builder/src/lib/ai/praxis-cron-builder-authoring-manifest.ts`23- focused `schedule-*`, `cron-runtime`, and AI manifest specs2425## Canonical Boundary2627`schedule-contract.ts` owns the public schedule vocabulary:2829- `ScheduleAuthoringConfig`30- `ScheduleKind`31- `ScheduleRecurrence`32- `ScheduleWindow`33- `ScheduleExecutionPolicy`34- `ScheduleGovernance`35- `ScheduleDiagnostic`36- `CronDialect`37- `CRON_DIALECTS`3839`schedule-normalizer.ts` owns compatibility from legacy CRON strings to canonical schedule config. `schedule-authoring-runtime.ts` owns compile, validation, and preview orchestration. `cron-runtime.ts` owns expression parsing, humanization, and occurrence generation.4041Do not create parallel host DTOs for schedule kind, dialect, timezone, preview, diagnostics, or execution policy when these contracts already carry the semantics.4243## Authoring Rules4445- Model business schedule intent as `kind` plus `recurrence` whenever possible.46- Use `kind='customCron'` and `expression.cron` only when the user explicitly requires a raw expression or an unsupported recurrence.47- Preserve legacy string compatibility through `normalizeScheduleValue`; do not delete the compatibility path unless the public contract is intentionally migrated.48- Compile structured recurrence with `compileScheduleExpression` before writing a canonical expression or compatibility value.49- Run `validateScheduleAuthoringConfig` before accepting recurrence, expression, window, timezone, or execution policy changes.50- Use `createSchedulePreview` for preview and diagnostics; do not manually recompute next occurrences in consumers.51- Use `CRON_DIALECTS` for field count, seconds/year support, named months/weekdays, question mark, last/nth weekday support, timezone mode, and day-of-month/day-of-week rules.52- Preserve dialect differences between Unix, Quartz, AWS EventBridge, Kubernetes CronJob, GitHub Actions schedule, and Google Cloud Scheduler.53- Keep one-time schedules explicit. Do not pretend `kind='once'` has a portable CRON representation when diagnostics say it does not.54- Keep timezone as IANA timezone metadata unless the selected dialect has fixed UTC or host-local semantics.5556## Inventory Before New Contract5758Classify requested behavior before adding fields:5960- `ja-suportado-so-ux`: existing diagnostics, preview, recurrence, window, or governance data is not surfaced clearly.61- `ja-suportado-mal-nomeado-ou-mal-materializado`: a consumer stores CRON strings or local fields that should normalize to `ScheduleAuthoringConfig`.62- `suportado-parcialmente`: existing config carries the intent but compile, preview, i18n, docs, or form projection needs completion.63- `lacuna-real-de-contrato`: no current schedule config, dialect definition, execution policy, governance, diagnostics, or manifest operation can represent the required semantic decision.6465For real contract gaps, name the canonical owner, affected package exports, consumers, docs/examples, AI manifest changes, and minimum proof before editing.6667## Validation6869Use the smallest reliable proof:7071- `schedule-normalizer.spec.ts`72- `schedule-authoring-runtime.spec.ts`73- `cron-runtime.spec.ts`74- `pdx-cron-builder.component.spec.ts` when compile/preview affects CVA round-trip75- AI manifest/adapter specs when operations or diagnostics change76- `npm run build:praxis-cron-builder` when public types or exports change7778Report exactly which dialects, schedule kinds, and invalid cases were covered.7980## Companion Skills8182- Use `praxis-cron-builder-runtime` for component UI, CVA, metadata, and preview rendering.83- Use `praxis-cron-builder-form-field` for metadata-driven form integration and submit payload shape.84- Use `praxis-cron-builder-ai-validation` for agentic operations, read-only validate/preview behavior, and registry contracts.85- Use `praxis-core-runtime-contracts` only if schedule semantics are intentionally promoted from the package to shared core.