Praxis Editorial Forms Agentic Authoring
Use this skill when editorial experiences are authored by AI, tools, or visual editors. Editorial authoring must compile to manifest-backed operations over the editorial runtime document; it must not emit arbitrary JSON patches or collapse the domain into dynamic-form config.
Source Audit
Inspect before editing:
projects/praxis-editorial-forms/AGENTS.md
projects/praxis-editorial-forms/README.md
projects/praxis-editorial-forms/docs/editorial-authoring-playbook.md
projects/praxis-editorial-forms/docs/editorial-authoring-plan.md
projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.ts
projects/praxis-editorial-forms/src/lib/editorial-form-runtime.metadata.ts
projects/praxis-editorial-forms/src/lib/praxis-editorial-forms.ts
projects/praxis-editorial-forms/src/public-api.ts
- manifest, component metadata, registry, docs, lab, and E2E specs for the affected path
Canonical Boundary
PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST is the executable authoring contract for EditorialRuntimeInput. Component metadata and providePraxisEditorialForms() publish the runtime to dynamic widget composition. Registry ingestion and docs are derived projections; they must not redefine editorial semantics.
Use domain operations, not free patches:
snapshot.set
fallback.configure
presentation.configure
adapter.bind
dataBlock.add
dataBlock.remove
fieldBinding.set
Authoring Rules
snapshot.set must preserve diagnostics and validate solution, journey, and step existence.
fallback.configure must be explicit and diagnostic-backed; fallback is derived, not domain truth.
presentation.configure writes only under solution.presentation and must not mutate journeys, blocks, FormConfig, FieldMetadata, or runtime data.
adapter.bind validates adapter registry existence, support, component inputs, fallback policy, and event forwarding.
dataBlock.add and dataBlock.remove operate on stable journey/step/block ids; destructive removal requires confirmation and must reject live field-binding references.
fieldBinding.set governs runtimeContext.formData paths and delegates FieldMetadata changes to metadata-editor.
- Rich/narrative blocks must use canonical rich-content contracts when the authored payload is a
RichContentDocument; do not create an editorial-only rich text dialect.
- Dynamic-page/page-builder embedding must use component metadata ports and
providePraxisEditorialForms(), not local component registries.
- Do not route editorial intent through frontend keyword lists, regexes, or aliases. Use semantic intent, manifest operations, context packs, registry docs, and declared tools.
Registry And Docs Rules
- Keep
EDITORIAL_FORM_RUNTIME_COMPONENT_METADATA aligned with public inputs, outputs, ports, layout hints, and dynamic widget id praxis-editorial-form-runtime.
- Review
docs/praxis-docs.manifest.json, README, architecture docs, labs, and generated registry docs when public authoring/runtime behavior changes.
- Run registry ingestion only when component metadata, authoring manifest, generated AI assets, or docs projections are affected.
- Keep labs honest:
/lab/editorial-runtime and experimental cases are technical validation hosts, not final product UX.
Inventory Before New Contract
Classify requested changes:
ja-suportado-so-ux: manifest/component metadata exists but editor, registry, docs, or lab projection is incomplete.
ja-suportado-mal-nomeado-ou-mal-materializado: a consumer describes an operation as a page-builder/dynamic-form edit while the editorial manifest already owns it.
suportado-parcialmente: operation, validator, metadata, docs, registry, or focused spec exists but is not aligned.
lacuna-real-de-contrato: no existing manifest operation, target, validator, component port, registry field, or delegated owner can express the authoring decision.
Only a real gap justifies a new manifest operation, target, validator, public metadata port, or generated registry contract.
Validation
Use focused local proof:
- manifest:
src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts
- component metadata/provider:
src/lib/editorial-form-runtime.metadata.spec.ts
- runtime round-trip:
src/lib/editorial-form-runtime.component.spec.ts
- adapter operations: adapter registry and dynamic-form adapter specs
- docs/registry:
npm run generate:registry:ingestion only when generated registry artifacts are affected
- build:
npm run build:praxis-editorial-forms
- labs/E2E: focused
test-dev/e2e/*.playwright.spec.ts when host experiments or labs change
Pair with praxis-editorial-forms-journey-snapshot-runtime, praxis-editorial-forms-presentation-diagnostics, and praxis-editorial-forms-data-collection-adapters according to the operation being authored.
1---2name: praxis-editorial-forms-agentic-authoring3description: Use when implementing or auditing `@praxisui/editorial-forms` AI authoring, `PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST`, component edit plans, snapshot/fallback/presentation operations, adapter binding, data block add/remove, field binding, registry ingestion, component metadata, docs, labs, and governed handoff to dynamic-form, metadata-editor, rich-content, or page-builder.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-editorial-forms-agentic-authoring6---78# Praxis Editorial Forms Agentic Authoring910Use this skill when editorial experiences are authored by AI, tools, or visual editors. Editorial authoring must compile to manifest-backed operations over the editorial runtime document; it must not emit arbitrary JSON patches or collapse the domain into dynamic-form config.1112## Source Audit1314Inspect before editing:1516- `projects/praxis-editorial-forms/AGENTS.md`17- `projects/praxis-editorial-forms/README.md`18- `projects/praxis-editorial-forms/docs/editorial-authoring-playbook.md`19- `projects/praxis-editorial-forms/docs/editorial-authoring-plan.md`20- `projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.ts`21- `projects/praxis-editorial-forms/src/lib/editorial-form-runtime.metadata.ts`22- `projects/praxis-editorial-forms/src/lib/praxis-editorial-forms.ts`23- `projects/praxis-editorial-forms/src/public-api.ts`24- manifest, component metadata, registry, docs, lab, and E2E specs for the affected path2526## Canonical Boundary2728`PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST` is the executable authoring contract for `EditorialRuntimeInput`. Component metadata and `providePraxisEditorialForms()` publish the runtime to dynamic widget composition. Registry ingestion and docs are derived projections; they must not redefine editorial semantics.2930Use domain operations, not free patches:3132- `snapshot.set`33- `fallback.configure`34- `presentation.configure`35- `adapter.bind`36- `dataBlock.add`37- `dataBlock.remove`38- `fieldBinding.set`3940## Authoring Rules4142- `snapshot.set` must preserve diagnostics and validate solution, journey, and step existence.43- `fallback.configure` must be explicit and diagnostic-backed; fallback is derived, not domain truth.44- `presentation.configure` writes only under `solution.presentation` and must not mutate journeys, blocks, `FormConfig`, `FieldMetadata`, or runtime data.45- `adapter.bind` validates adapter registry existence, support, component inputs, fallback policy, and event forwarding.46- `dataBlock.add` and `dataBlock.remove` operate on stable journey/step/block ids; destructive removal requires confirmation and must reject live field-binding references.47- `fieldBinding.set` governs `runtimeContext.formData` paths and delegates `FieldMetadata` changes to metadata-editor.48- Rich/narrative blocks must use canonical rich-content contracts when the authored payload is a `RichContentDocument`; do not create an editorial-only rich text dialect.49- Dynamic-page/page-builder embedding must use component metadata ports and `providePraxisEditorialForms()`, not local component registries.50- Do not route editorial intent through frontend keyword lists, regexes, or aliases. Use semantic intent, manifest operations, context packs, registry docs, and declared tools.5152## Registry And Docs Rules5354- Keep `EDITORIAL_FORM_RUNTIME_COMPONENT_METADATA` aligned with public inputs, outputs, ports, layout hints, and dynamic widget id `praxis-editorial-form-runtime`.55- Review `docs/praxis-docs.manifest.json`, README, architecture docs, labs, and generated registry docs when public authoring/runtime behavior changes.56- Run registry ingestion only when component metadata, authoring manifest, generated AI assets, or docs projections are affected.57- Keep labs honest: `/lab/editorial-runtime` and experimental cases are technical validation hosts, not final product UX.5859## Inventory Before New Contract6061Classify requested changes:6263- `ja-suportado-so-ux`: manifest/component metadata exists but editor, registry, docs, or lab projection is incomplete.64- `ja-suportado-mal-nomeado-ou-mal-materializado`: a consumer describes an operation as a page-builder/dynamic-form edit while the editorial manifest already owns it.65- `suportado-parcialmente`: operation, validator, metadata, docs, registry, or focused spec exists but is not aligned.66- `lacuna-real-de-contrato`: no existing manifest operation, target, validator, component port, registry field, or delegated owner can express the authoring decision.6768Only a real gap justifies a new manifest operation, target, validator, public metadata port, or generated registry contract.6970## Validation7172Use focused local proof:7374- manifest: `src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts`75- component metadata/provider: `src/lib/editorial-form-runtime.metadata.spec.ts`76- runtime round-trip: `src/lib/editorial-form-runtime.component.spec.ts`77- adapter operations: adapter registry and dynamic-form adapter specs78- docs/registry: `npm run generate:registry:ingestion` only when generated registry artifacts are affected79- build: `npm run build:praxis-editorial-forms`80- labs/E2E: focused `test-dev/e2e/*.playwright.spec.ts` when host experiments or labs change8182Pair with `praxis-editorial-forms-journey-snapshot-runtime`, `praxis-editorial-forms-presentation-diagnostics`, and `praxis-editorial-forms-data-collection-adapters` according to the operation being authored.