vnext-ai-toolkit

Create, edit, and validate vNext workflow domain components (Schemas, Workflows, Tasks, Views, Functions, Extensions) in a @burgan-tech/vnext-template project. Use whenever the user wants to add or change a component JSON file under the domain directory, asks about the required component fields (key/version/domain/ flow/flowVersion/tags/attributes), or hits schema-validation errors from `npm run validate`.

Use when the user wants to create a vNext Function — a REST endpoint exposed by the runtime. Fetches function.json schema first, walks scope (D/F/I) and task composition (single-task vs multi-task), scaffolds the IMapping or IOutputHandler .csx using contracts from csx-contracts.md.

Use when the user wants to create a vNext Mapping (sys-mappings) component — a reusable C# helper/code class (e.g. a crypto or JSON helper) that other components reference via scripts.helpers or encoding REF. Fetches mapping-definition.schema.json first, scaffolds the Mappings/{key}.json envelope + the .csx static class, and explains wiring it into consumers.

Use when the user wants to create or modify a vNext Schema component. Interactively gathers fields, types, validation rules, localization (x-labels), field-level access (x-roles), and query metadata (x-filterOperators/x-sortable/x-displayFormat) before producing JSON Schema draft 2020-12 at the path resolved from vnext.config.json.

Use when the user asks to validate components or fix validation errors, or before committing. Runs `npm run validate`, categorizes failures, queries the docs for the relevant rule, and proposes targeted fixes with user approval before applying.

Use when the user wants to create a new vNext Workflow end-to-end. Plans the state/transition graph, scaffolds the workflow JSON + .csx mapping files + .http test file, and chains to view-design / schema-design as needed.

Use when the user wants to create a vNext Extension — automatic instance data enrichment on workflow reads. Fetches extension.json schema first, walks the type × scope matrix from the schema, warns on performance impact (especially Global × Everywhere).

Use when the user wants to create a new vNext Task component (HTTP, Script, SOAP, Dapr, Notification, GetInstances, etc.). Fetches task.json schema first, drives type and config selection from the schema enum, scaffolds a .csx mapping if needed, suggests a matching MockLab seed.

Use after a workflow is scaffolded (or to add coverage to an existing one). Generates an xUnit integration test class against the official VNext.Testing.Sdk that asserts the workflow's lifecycle — start, transitions, final state. If no test project exists, scaffolds one with the official VNext.Testing.Template (dotnet new vnext-integration-test) or hands off to /vnext-init.

Use when the user wants to create or modify a vNext View component. Asks for the renderer first (pseudo-ui recommended), loads vocabulary if pseudo-ui, then generates the view JSON at the correct path resolved from vnext.config.json.