Praxis Visual Builder AI Validation
Use this skill for governed AI authoring of visual-builder rules. AI operations must resolve semantic intent into declared manifest operations and validators; they must not patch arbitrary JSON or route primary intent through keywords.
Pair it with:
praxis-ai-authoring-manifests for component manifest structure, operation contracts, targets, validators, and examples.
praxis-ai-registry-ingestion when manifest changes must be discovered by the AI registry.
praxis-ai-semantic-intent when user intent resolution, grounding, or tool selection is involved.
praxis-visual-builder-graph-runtime for graph state, node identity, edges, validation errors, and registry integrity.
praxis-visual-builder-jsonlogic-roundtrip for condition.set, JSON Logic parsing, and dsl.roundTrip.validate.
praxis-visual-builder-schemas-templates for variable.add, effect.set, target schemas, field schemas, and context variables.
praxis-page-builder-ai-agentic when visual-builder AI operations are delegated from Page Builder agentic authoring or child widget config flows.
Source Audit
Before editing visual-builder AI behavior, inspect:
projects/praxis-visual-builder/AGENTS.md
projects/praxis-visual-builder/README.md
projects/praxis-visual-builder/src/lib/ai/praxis-visual-builder-authoring-manifest.ts
projects/praxis-visual-builder/src/lib/ai/visual-builder-ai.adapter.ts
projects/praxis-visual-builder/src/lib/ai/visual-builder-ai-capabilities.ts
projects/praxis-visual-builder/src/lib/ai/visual-builder-ai.context.ts
projects/praxis-visual-builder/src/lib/ai/visual-builder-context-pack.ts
projects/praxis-visual-builder/src/lib/services/rule-builder.service.ts
projects/praxis-visual-builder/src/lib/services/rule-node-registry.service.ts
projects/praxis-visual-builder/src/lib/services/context/context-management.service.ts
- manifest, adapter, AI wizard, and AI integration specs
Also inspect core AI manifest/registry contracts if operation schema, validator shape, or ingestion behavior changes.
Canonical AI Boundary
PRAXIS_VISUAL_BUILDER_AUTHORING_MANIFEST owns the agentic contract for:
- editable targets:
node, edge, variable, condition, effect, and dslDocument;
- operations:
node.add, node.remove, node.configure, edge.connect, edge.remove, variable.add, condition.set, effect.set, and dsl.roundTrip.validate;
- input schemas, identity keys, affected paths, preconditions, destructive flags, failure modes, validators, and examples;
- round-trip requirements for graph identity, JSON Logic, target property schemas, and child component ownership.
VisualBuilderAiAdapter owns guarded RuleBuilderConfig patch application for the component. It must not become a bypass around graph operations, registry integrity, JSON Logic validation, or target-property validation for persisted rules.
AI Authoring Rules
- Resolve user intent semantically into manifest operations. Do not decide intent through keyword lists, regexes, or local aliases.
- Use matching, labels, field search, and fuzzy ranking only after the semantic operation scope and canonical target kind are known.
- Every AI operation needs stable identity keys:
nodeId, source/target node IDs, variable scope/name, effect target type/targets, or round-trip format/compare mode.
- Destructive
node.remove and edge.remove require explicit confirmation when semantics can be lost.
condition.set must provide JSON Logic objects within the supported visual subset, not JavaScript strings.
effect.set must validate targetType, target IDs, governed properties, and property value types through target property schemas and RULE_PROPERTY_SCHEMA.
variable.add governs contextual/template flows; visual field-condition references to context variables remain unsupported until the canonical JSON Logic shape is defined.
- Host-provided widget/page context must enter through declared context packs, field schemas, target schemas, or variables. Do not let Page Builder or another host inject arbitrary prompt context that becomes persisted rule state.
dsl.roundTrip.validate must prove export/import stability and reject semantic drift or unstable identity.
Inventory Before New Contract
Classify AI gaps before adding manifest operations:
ja-suportado-so-ux: the operation, validator, failure mode, or example exists but the assistant/wizard does not expose it well.
ja-suportado-mal-nomeado-ou-mal-materializado: broad config patches or host-local labels are being used where manifest targets and operation IDs already exist.
suportado-parcialmente: the manifest operation exists but handler wiring, validator coverage, adapter behavior, examples, or registry ingestion is incomplete.
lacuna-real-de-contrato: no declared target, operation, input schema, validator, handler contract, or canonical runtime path can express the AI authoring decision.
Only a real gap justifies new AI operations or public authoring contracts. When adding one, define source of truth, affected paths, failure modes, examples, registry ingestion impact, docs/examples, and local validation.
Validation
Use focused local gates:
praxis-visual-builder-authoring-manifest.spec.ts for manifest shape, operations, validators, examples, and round-trip requirements;
visual-builder-ai.adapter.spec.ts for patch application, snapshot/restore, and failure behavior;
- AI wizard/integration specs when user-facing AI authoring changes;
- graph, JSON Logic, schema/template skills for operation-specific runtime validation;
- host delegation specs when AI operations are invoked through Page Builder or another component authoring surface;
praxis-ai-registry-ingestion checks when generated registry assets or catalog ingestion changes;
npm run build:praxis-visual-builder when public AI exports change.
Final audit should state whether manifest validation, adapter behavior, operation runtime effects, registry ingestion, and JSON Logic round-trip were tested locally.
1---2name: praxis-visual-builder-ai-validation3description: "Use when Codex must implement, audit, or consume @praxisui/visual-builder AI authoring surfaces: PRAXIS_VISUAL_BUILDER_AUTHORING_MANIFEST, VisualBuilderAiAdapter, VISUAL_BUILDER_AI_CATALOG, editable targets, node.add, node.remove, node.configure, edge.connect, edge.remove, variable.add, condition.set, effect.set, dsl.roundTrip.validate, validators, failure modes, context packs, or AI registry ingestion."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-visual-builder-ai-validation6---78# Praxis Visual Builder AI Validation910Use this skill for governed AI authoring of visual-builder rules. AI operations must resolve semantic intent into declared manifest operations and validators; they must not patch arbitrary JSON or route primary intent through keywords.1112Pair it with:1314- `praxis-ai-authoring-manifests` for component manifest structure, operation contracts, targets, validators, and examples.15- `praxis-ai-registry-ingestion` when manifest changes must be discovered by the AI registry.16- `praxis-ai-semantic-intent` when user intent resolution, grounding, or tool selection is involved.17- `praxis-visual-builder-graph-runtime` for graph state, node identity, edges, validation errors, and registry integrity.18- `praxis-visual-builder-jsonlogic-roundtrip` for `condition.set`, JSON Logic parsing, and `dsl.roundTrip.validate`.19- `praxis-visual-builder-schemas-templates` for `variable.add`, `effect.set`, target schemas, field schemas, and context variables.20- `praxis-page-builder-ai-agentic` when visual-builder AI operations are delegated from Page Builder agentic authoring or child widget config flows.2122## Source Audit2324Before editing visual-builder AI behavior, inspect:2526- `projects/praxis-visual-builder/AGENTS.md`27- `projects/praxis-visual-builder/README.md`28- `projects/praxis-visual-builder/src/lib/ai/praxis-visual-builder-authoring-manifest.ts`29- `projects/praxis-visual-builder/src/lib/ai/visual-builder-ai.adapter.ts`30- `projects/praxis-visual-builder/src/lib/ai/visual-builder-ai-capabilities.ts`31- `projects/praxis-visual-builder/src/lib/ai/visual-builder-ai.context.ts`32- `projects/praxis-visual-builder/src/lib/ai/visual-builder-context-pack.ts`33- `projects/praxis-visual-builder/src/lib/services/rule-builder.service.ts`34- `projects/praxis-visual-builder/src/lib/services/rule-node-registry.service.ts`35- `projects/praxis-visual-builder/src/lib/services/context/context-management.service.ts`36- manifest, adapter, AI wizard, and AI integration specs3738Also inspect core AI manifest/registry contracts if operation schema, validator shape, or ingestion behavior changes.3940## Canonical AI Boundary4142`PRAXIS_VISUAL_BUILDER_AUTHORING_MANIFEST` owns the agentic contract for:4344- editable targets: `node`, `edge`, `variable`, `condition`, `effect`, and `dslDocument`;45- operations: `node.add`, `node.remove`, `node.configure`, `edge.connect`, `edge.remove`, `variable.add`, `condition.set`, `effect.set`, and `dsl.roundTrip.validate`;46- input schemas, identity keys, affected paths, preconditions, destructive flags, failure modes, validators, and examples;47- round-trip requirements for graph identity, JSON Logic, target property schemas, and child component ownership.4849`VisualBuilderAiAdapter` owns guarded `RuleBuilderConfig` patch application for the component. It must not become a bypass around graph operations, registry integrity, JSON Logic validation, or target-property validation for persisted rules.5051## AI Authoring Rules5253- Resolve user intent semantically into manifest operations. Do not decide intent through keyword lists, regexes, or local aliases.54- Use matching, labels, field search, and fuzzy ranking only after the semantic operation scope and canonical target kind are known.55- Every AI operation needs stable identity keys: `nodeId`, source/target node IDs, variable scope/name, effect target type/targets, or round-trip format/compare mode.56- Destructive `node.remove` and `edge.remove` require explicit confirmation when semantics can be lost.57- `condition.set` must provide JSON Logic objects within the supported visual subset, not JavaScript strings.58- `effect.set` must validate `targetType`, target IDs, governed properties, and property value types through target property schemas and `RULE_PROPERTY_SCHEMA`.59- `variable.add` governs contextual/template flows; visual field-condition references to context variables remain unsupported until the canonical JSON Logic shape is defined.60- Host-provided widget/page context must enter through declared context packs, field schemas, target schemas, or variables. Do not let Page Builder or another host inject arbitrary prompt context that becomes persisted rule state.61- `dsl.roundTrip.validate` must prove export/import stability and reject semantic drift or unstable identity.6263## Inventory Before New Contract6465Classify AI gaps before adding manifest operations:6667- `ja-suportado-so-ux`: the operation, validator, failure mode, or example exists but the assistant/wizard does not expose it well.68- `ja-suportado-mal-nomeado-ou-mal-materializado`: broad config patches or host-local labels are being used where manifest targets and operation IDs already exist.69- `suportado-parcialmente`: the manifest operation exists but handler wiring, validator coverage, adapter behavior, examples, or registry ingestion is incomplete.70- `lacuna-real-de-contrato`: no declared target, operation, input schema, validator, handler contract, or canonical runtime path can express the AI authoring decision.7172Only a real gap justifies new AI operations or public authoring contracts. When adding one, define source of truth, affected paths, failure modes, examples, registry ingestion impact, docs/examples, and local validation.7374## Validation7576Use focused local gates:7778- `praxis-visual-builder-authoring-manifest.spec.ts` for manifest shape, operations, validators, examples, and round-trip requirements;79- `visual-builder-ai.adapter.spec.ts` for patch application, snapshot/restore, and failure behavior;80- AI wizard/integration specs when user-facing AI authoring changes;81- graph, JSON Logic, schema/template skills for operation-specific runtime validation;82- host delegation specs when AI operations are invoked through Page Builder or another component authoring surface;83- `praxis-ai-registry-ingestion` checks when generated registry assets or catalog ingestion changes;84- `npm run build:praxis-visual-builder` when public AI exports change.8586Final audit should state whether manifest validation, adapter behavior, operation runtime effects, registry ingestion, and JSON Logic round-trip were tested locally.