Praxis Manual Form AI Authoring
Use this skill for governed manual-form authoring. Manual Form AI must compile to manifest-backed component edit plans; it must not emit arbitrary JSON patches over host templates or duplicate dynamic-form/metadata-editor semantics.
For focused work, load the narrow companion first:
praxis-manual-form-rules-agentic for PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST, component edit plans, formRules, formRulesState, JSON Logic, config editor, context pack, turn flow, and registry projections.
praxis-manual-form-toolbar-metadata-bridge for toolbar/metadata bridge authoring operations and metadata-editor delegation.
praxis-manual-form-autosave-persistence for autosave operations, debounce, persistence key validation, and draft reload semantics.
praxis-manual-form-field-detection-instance for manual field targets, host-template field existence, control-type discovery, and ManualFormInstance state.
Required Source Audit
Inspect:
projects/praxis-manual-form/AGENTS.md
src/lib/components/manual-form-config-editor/manual-form-config-editor.component.ts
src/lib/ai/praxis-manual-form-authoring-manifest.ts
src/lib/ai/manual-form-ai-capabilities.ts
src/lib/ai/manual-form-ai.adapter.ts
src/lib/ai/manual-form-context-pack.ts
src/lib/ai/manual-form-agentic-authoring-turn-flow.ts
src/lib/praxis-manual-form.metadata.ts
src/public-api.ts
- README, API docs, docs manifest, and focused specs
Authoring Boundary
Manual Form authoring owns manual-form concerns:
- manual field add/remove metadata
- labels and basic field metadata patches
- host-template-aware layout configuration
- toolbar enablement and editable flags
- autosave enablement/debounce/persistence keys
- submit/reset/cancel behavior
- metadata bridge configuration
Delegate advanced FieldMetadata shape changes to @praxisui/metadata-editor. Delegate advanced FormConfig layout/config semantics to @praxisui/dynamic-form. Delegate rule graph editing to the visual rules owner when the task becomes a general rule-builder concern.
Manifest Rules
Use PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST as the executable contract.
manualField.add must verify unique field name, host-template field existence, control-type discovery, and metadata-editor delegation when advanced metadata is required.
manualField.remove is destructive and requires confirmation before metadata/layout/value loss.
manualField.label.set should write through the metadata bridge, not a host-local label map.
layout.configure must not replace the host-owned template layout.
toolbar.configure stays behind enableCustomization.
autosave.enabled.set must validate deterministic storage key composition and safe debounce.
metadataBridge.configure must preserve praxis-metadata-editor and dynamic-fields discovery ownership.
formRules is the authorable rules surface and conditions must be JSON Logic objects. Treat formRulesState as internal visual-editor round-trip state.
Classify authoring gaps before adding manifest operations or config paths:
ja-suportado-so-ux: the manifest/config path exists but editor, assistant, registry, or docs projection does not expose it well.
ja-suportado-mal-nomeado-ou-mal-materializado: the persisted shape already exists as FieldMetadata, formRules, ManualFormPersistenceOptions, or a metadata-editor patch but is named locally.
suportado-parcialmente: manifest, editor, capability, context pack, registry, or focused specs are not aligned.
lacuna-real-de-contrato: no existing manifest operation, target, config path, or governed handoff can express the decision.
AI And Registry
- Do not route prompts by keywords in the frontend.
- Use component edit plans and declared operations.
- Treat
runtimeAuthoringPolicy.canApplyLocalPatch=false as normative for agentic authoring. If the backend returns a free patch, keep canApply=false, clear pendingPatch, surface diagnostics, and ask for a componentEditPlan validated against PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST.
- Do not treat adapter-level
applyPatch(...) support as permission to apply arbitrary AI patches. It is an internal/runtime merge path; AI-facing apply must stay gated by manifest compilation, capability validation, and the component edit plan contract.
- Include
authoringManifestRef, capability refs, runtime state digest, and safe context items in assistant/session context so the model is grounded by the canonical manifest instead of host template text.
- Keep
MANUAL_FORM_AI_CAPABILITIES aligned with the manifest, config editor, and runtime behavior.
- Update AI registry ingestion when component metadata, capabilities, manifests, or docs projections change.
- Keep internal authoring text in the manual-form i18n catalogs.
Validation
Minimum gates:
- manifest:
src/lib/ai/praxis-manual-form-authoring-manifest.spec.ts
- capabilities:
src/lib/ai/manual-form-ai-capabilities.spec.ts
- turn flow:
src/lib/ai/manual-form-agentic-authoring-turn-flow.spec.ts
- config editor and Settings Panel: focused config-editor specs
- i18n:
src/lib/i18n/manual-form.i18n.spec.ts
- compile:
ng build praxis-manual-form
- registry/docs:
npm run generate:registry:ingestion only when generated AI/component registry artifacts are affected
Pair with praxis-manual-form-runtime-bridge for runtime/autosave/bridge changes and praxis-angular-validation-gates to choose the smallest proof.
1---2name: praxis-manual-form-ai-authoring3description: Use when changing or validating `@praxisui/manual-form` authoring surfaces, including `ManualFormConfigEditorComponent`, Settings Panel integration, `PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST`, `MANUAL_FORM_AI_CAPABILITIES`, agentic authoring turn flow, component edit plans, formRules JSON Logic, toolbar/autosave/submit operations, metadata bridge configuration, AI registry ingestion, docs, and round-trip validation.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-manual-form-ai-authoring6---78# Praxis Manual Form AI Authoring910Use this skill for governed manual-form authoring. Manual Form AI must compile to manifest-backed component edit plans; it must not emit arbitrary JSON patches over host templates or duplicate `dynamic-form`/`metadata-editor` semantics.1112For focused work, load the narrow companion first:1314- `praxis-manual-form-rules-agentic` for `PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST`, component edit plans, `formRules`, `formRulesState`, JSON Logic, config editor, context pack, turn flow, and registry projections.15- `praxis-manual-form-toolbar-metadata-bridge` for toolbar/metadata bridge authoring operations and metadata-editor delegation.16- `praxis-manual-form-autosave-persistence` for autosave operations, debounce, persistence key validation, and draft reload semantics.17- `praxis-manual-form-field-detection-instance` for manual field targets, host-template field existence, control-type discovery, and `ManualFormInstance` state.1819## Required Source Audit2021Inspect:2223- `projects/praxis-manual-form/AGENTS.md`24- `src/lib/components/manual-form-config-editor/manual-form-config-editor.component.ts`25- `src/lib/ai/praxis-manual-form-authoring-manifest.ts`26- `src/lib/ai/manual-form-ai-capabilities.ts`27- `src/lib/ai/manual-form-ai.adapter.ts`28- `src/lib/ai/manual-form-context-pack.ts`29- `src/lib/ai/manual-form-agentic-authoring-turn-flow.ts`30- `src/lib/praxis-manual-form.metadata.ts`31- `src/public-api.ts`32- README, API docs, docs manifest, and focused specs3334## Authoring Boundary3536Manual Form authoring owns manual-form concerns:3738- manual field add/remove metadata39- labels and basic field metadata patches40- host-template-aware layout configuration41- toolbar enablement and editable flags42- autosave enablement/debounce/persistence keys43- submit/reset/cancel behavior44- metadata bridge configuration4546Delegate advanced `FieldMetadata` shape changes to `@praxisui/metadata-editor`. Delegate advanced `FormConfig` layout/config semantics to `@praxisui/dynamic-form`. Delegate rule graph editing to the visual rules owner when the task becomes a general rule-builder concern.4748## Manifest Rules4950Use `PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST` as the executable contract.5152- `manualField.add` must verify unique field name, host-template field existence, control-type discovery, and metadata-editor delegation when advanced metadata is required.53- `manualField.remove` is destructive and requires confirmation before metadata/layout/value loss.54- `manualField.label.set` should write through the metadata bridge, not a host-local label map.55- `layout.configure` must not replace the host-owned template layout.56- `toolbar.configure` stays behind `enableCustomization`.57- `autosave.enabled.set` must validate deterministic storage key composition and safe debounce.58- `metadataBridge.configure` must preserve `praxis-metadata-editor` and dynamic-fields discovery ownership.5960`formRules` is the authorable rules surface and conditions must be JSON Logic objects. Treat `formRulesState` as internal visual-editor round-trip state.6162Classify authoring gaps before adding manifest operations or config paths:6364- `ja-suportado-so-ux`: the manifest/config path exists but editor, assistant, registry, or docs projection does not expose it well.65- `ja-suportado-mal-nomeado-ou-mal-materializado`: the persisted shape already exists as `FieldMetadata`, `formRules`, `ManualFormPersistenceOptions`, or a metadata-editor patch but is named locally.66- `suportado-parcialmente`: manifest, editor, capability, context pack, registry, or focused specs are not aligned.67- `lacuna-real-de-contrato`: no existing manifest operation, target, config path, or governed handoff can express the decision.6869## AI And Registry7071- Do not route prompts by keywords in the frontend.72- Use component edit plans and declared operations.73- Treat `runtimeAuthoringPolicy.canApplyLocalPatch=false` as normative for agentic authoring. If the backend returns a free patch, keep `canApply=false`, clear `pendingPatch`, surface diagnostics, and ask for a `componentEditPlan` validated against `PRAXIS_MANUAL_FORM_AUTHORING_MANIFEST`.74- Do not treat adapter-level `applyPatch(...)` support as permission to apply arbitrary AI patches. It is an internal/runtime merge path; AI-facing apply must stay gated by manifest compilation, capability validation, and the component edit plan contract.75- Include `authoringManifestRef`, capability refs, runtime state digest, and safe context items in assistant/session context so the model is grounded by the canonical manifest instead of host template text.76- Keep `MANUAL_FORM_AI_CAPABILITIES` aligned with the manifest, config editor, and runtime behavior.77- Update AI registry ingestion when component metadata, capabilities, manifests, or docs projections change.78- Keep internal authoring text in the manual-form i18n catalogs.7980## Validation8182Minimum gates:8384- manifest: `src/lib/ai/praxis-manual-form-authoring-manifest.spec.ts`85- capabilities: `src/lib/ai/manual-form-ai-capabilities.spec.ts`86- turn flow: `src/lib/ai/manual-form-agentic-authoring-turn-flow.spec.ts`87- config editor and Settings Panel: focused config-editor specs88- i18n: `src/lib/i18n/manual-form.i18n.spec.ts`89- compile: `ng build praxis-manual-form`90- registry/docs: `npm run generate:registry:ingestion` only when generated AI/component registry artifacts are affected9192Pair with `praxis-manual-form-runtime-bridge` for runtime/autosave/bridge changes and `praxis-angular-validation-gates` to choose the smallest proof.