Praxis Editorial Forms Adapters AI
Use this skill for optional data block adapters and AI-governed editorial authoring. Editorial Forms may bind to generic engines, but the editorial domain remains canonical.
For focused work, load the narrow companion first:
praxis-editorial-forms-data-collection-adapters for adapter token/registry, dataCollection state, dynamic-form adapter, outlet rendering, config lookup, adapter events, and runtime form data.
praxis-editorial-forms-agentic-authoring for PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST, component edit plans, snapshot/fallback/presentation operations, adapter binding, data block add/remove, field binding, registry ingestion, and docs.
praxis-editorial-forms-presentation-diagnostics when adapter authoring changes fallback, diagnostics, or operational events.
praxis-editorial-forms-journey-snapshot-runtime when adapter or authoring changes affect resolved snapshots, journeys, blocks, or provenance.
Required Source Audit
Inspect:
projects/praxis-editorial-forms/AGENTS.md
docs/architecture.md
docs/editorial-authoring-playbook.md
src/lib/adapters/editorial-data-block-adapter.ts
src/lib/adapters/editorial-data-block-adapter-registry.ts
src/lib/adapters/editorial-data-collection-block-outlet.component.ts
src/lib/adapters/dynamic-form/editorial-dynamic-form.adapter.ts
src/lib/ai/praxis-editorial-forms-authoring-manifest.ts
src/lib/editorial-form-runtime.metadata.ts
src/public-api.ts
- adapter, manifest, renderer, and registry specs for the affected path
Adapter Boundary
dataCollection is an editorial block kind. The concrete form engine is optional.
- Register adapters through
EDITORIAL_DATA_BLOCK_ADAPTER and provideEditorialDataBlockAdapter.
- Use
EditorialDataBlockAdapterRegistry to distinguish missing, incompatible, and resolved adapters.
- Use
provideEditorialDynamicFormAdapter({ component: PraxisDynamicForm }) only as an optional bridge.
- The host still owns
GenericCrudService, endpoint configuration, remote schema access, and submit behavior required by Dynamic Form.
- Validate adapter components expose required inputs such as
config, formId, and editorialContext.
- Missing or incompatible adapters must produce diagnostics, fallback state, and operational events; do not hide them behind successful-looking fallback UI.
Authoring Manifest Rules
Use PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST as the executable contract.
snapshot.set patches inputs and preserves diagnostics.
fallback.configure must be explicit and diagnostic-backed.
presentation.configure may affect visual presentation only.
adapter.bind validates provider binding and fallback policy.
dataBlock.add and dataBlock.remove operate on stable journey/step/block ids.
fieldBinding.set writes governed runtime context bindings and delegates FieldMetadata changes to metadata-editor.
Do not author FieldMetadata inside editorial-forms. Use praxis-metadata-editor-ai-validation and dynamic-fields discovery when the field shape changes. Use praxis-form-ai-rules-validation or dynamic-form skills when data collection form semantics change.
Use praxis-rich-content-integration-adapters and praxis-rich-content-ai-security-validation when adapter or AI work materializes RichContentDocument in editorial blocks, previews, or generated examples.
Classify gaps before extending the manifest or adapter API:
ja-suportado-so-ux: adapter/manifest evidence exists but docs, registry, lab, or outlet feedback is weak.
ja-suportado-mal-nomeado-ou-mal-materializado: a host models adapter binding as local dynamic-form setup while EditorialDataBlockAdapterRegistry already owns resolution.
suportado-parcialmente: operation, validator, adapter component input validation, fallback policy, or registry projection is incomplete.
lacuna-real-de-contrato: no adapter hook, manifest operation, validator, block state, or delegated owner can express the decision.
AI And Registry
- Do not route editorial intent by frontend keyword lists.
- Keep assistant operations scoped to declared manifest operations and validators.
- Keep component metadata and
praxis-editorial-form-runtime registry docs aligned with providePraxisEditorialForms.
- Run or require AI registry ingestion when manifest, component docs, metadata, or packaged AI assets change.
Validation
Minimum gates:
- adapter registry:
src/lib/adapters/editorial-data-block-adapter-registry.spec.ts
- dynamic-form adapter:
src/lib/adapters/dynamic-form/editorial-dynamic-form.adapter.spec.ts
- data collection outlet/rendering:
src/lib/renderers/editorial-data-collection-block-outlet.component.spec.ts
- manifest:
src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts
- runtime fallback/snapshot when adapter diagnostics change
- compile:
npm run build:praxis-editorial-forms
- registry/docs:
npm run generate:registry:ingestion when generated registry artifacts are affected
Pair with praxis-editorial-forms-runtime for snapshot/fallback/presentation runtime behavior and praxis-angular-validation-gates to choose the smallest proof.
1---2name: praxis-editorial-forms-adapters-ai3description: Use when changing or validating `@praxisui/editorial-forms` optional adapters and AI authoring, including `EDITORIAL_DATA_BLOCK_ADAPTER`, `EditorialDataBlockAdapterRegistry`, `provideEditorialDynamicFormAdapter`, `dataCollection` blocks, adapter diagnostics, `PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST`, field binding, presentation/fallback operations, registry ingestion, docs, and dynamic-form/metadata-editor delegation.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-editorial-forms-adapters-ai6---78# Praxis Editorial Forms Adapters AI910Use this skill for optional data block adapters and AI-governed editorial authoring. Editorial Forms may bind to generic engines, but the editorial domain remains canonical.1112For focused work, load the narrow companion first:1314- `praxis-editorial-forms-data-collection-adapters` for adapter token/registry, `dataCollection` state, dynamic-form adapter, outlet rendering, config lookup, adapter events, and runtime form data.15- `praxis-editorial-forms-agentic-authoring` for `PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST`, component edit plans, snapshot/fallback/presentation operations, adapter binding, data block add/remove, field binding, registry ingestion, and docs.16- `praxis-editorial-forms-presentation-diagnostics` when adapter authoring changes fallback, diagnostics, or operational events.17- `praxis-editorial-forms-journey-snapshot-runtime` when adapter or authoring changes affect resolved snapshots, journeys, blocks, or provenance.1819## Required Source Audit2021Inspect:2223- `projects/praxis-editorial-forms/AGENTS.md`24- `docs/architecture.md`25- `docs/editorial-authoring-playbook.md`26- `src/lib/adapters/editorial-data-block-adapter.ts`27- `src/lib/adapters/editorial-data-block-adapter-registry.ts`28- `src/lib/adapters/editorial-data-collection-block-outlet.component.ts`29- `src/lib/adapters/dynamic-form/editorial-dynamic-form.adapter.ts`30- `src/lib/ai/praxis-editorial-forms-authoring-manifest.ts`31- `src/lib/editorial-form-runtime.metadata.ts`32- `src/public-api.ts`33- adapter, manifest, renderer, and registry specs for the affected path3435## Adapter Boundary3637`dataCollection` is an editorial block kind. The concrete form engine is optional.3839- Register adapters through `EDITORIAL_DATA_BLOCK_ADAPTER` and `provideEditorialDataBlockAdapter`.40- Use `EditorialDataBlockAdapterRegistry` to distinguish missing, incompatible, and resolved adapters.41- Use `provideEditorialDynamicFormAdapter({ component: PraxisDynamicForm })` only as an optional bridge.42- The host still owns `GenericCrudService`, endpoint configuration, remote schema access, and submit behavior required by Dynamic Form.43- Validate adapter components expose required inputs such as `config`, `formId`, and `editorialContext`.44- Missing or incompatible adapters must produce diagnostics, fallback state, and operational events; do not hide them behind successful-looking fallback UI.4546## Authoring Manifest Rules4748Use `PRAXIS_EDITORIAL_FORMS_AUTHORING_MANIFEST` as the executable contract.4950- `snapshot.set` patches inputs and preserves diagnostics.51- `fallback.configure` must be explicit and diagnostic-backed.52- `presentation.configure` may affect visual presentation only.53- `adapter.bind` validates provider binding and fallback policy.54- `dataBlock.add` and `dataBlock.remove` operate on stable journey/step/block ids.55- `fieldBinding.set` writes governed runtime context bindings and delegates `FieldMetadata` changes to metadata-editor.5657Do not author `FieldMetadata` inside editorial-forms. Use `praxis-metadata-editor-ai-validation` and dynamic-fields discovery when the field shape changes. Use `praxis-form-ai-rules-validation` or dynamic-form skills when data collection form semantics change.58Use `praxis-rich-content-integration-adapters` and `praxis-rich-content-ai-security-validation` when adapter or AI work materializes `RichContentDocument` in editorial blocks, previews, or generated examples.5960Classify gaps before extending the manifest or adapter API:6162- `ja-suportado-so-ux`: adapter/manifest evidence exists but docs, registry, lab, or outlet feedback is weak.63- `ja-suportado-mal-nomeado-ou-mal-materializado`: a host models adapter binding as local dynamic-form setup while `EditorialDataBlockAdapterRegistry` already owns resolution.64- `suportado-parcialmente`: operation, validator, adapter component input validation, fallback policy, or registry projection is incomplete.65- `lacuna-real-de-contrato`: no adapter hook, manifest operation, validator, block state, or delegated owner can express the decision.6667## AI And Registry6869- Do not route editorial intent by frontend keyword lists.70- Keep assistant operations scoped to declared manifest operations and validators.71- Keep component metadata and `praxis-editorial-form-runtime` registry docs aligned with `providePraxisEditorialForms`.72- Run or require AI registry ingestion when manifest, component docs, metadata, or packaged AI assets change.7374## Validation7576Minimum gates:7778- adapter registry: `src/lib/adapters/editorial-data-block-adapter-registry.spec.ts`79- dynamic-form adapter: `src/lib/adapters/dynamic-form/editorial-dynamic-form.adapter.spec.ts`80- data collection outlet/rendering: `src/lib/renderers/editorial-data-collection-block-outlet.component.spec.ts`81- manifest: `src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts`82- runtime fallback/snapshot when adapter diagnostics change83- compile: `npm run build:praxis-editorial-forms`84- registry/docs: `npm run generate:registry:ingestion` when generated registry artifacts are affected8586Pair with `praxis-editorial-forms-runtime` for snapshot/fallback/presentation runtime behavior and `praxis-angular-validation-gates` to choose the smallest proof.