菜单
Architecture and feature map for the Vant Flow Angular form platform. Use when working on DocumentDefinition schemas, builder or renderer behavior, VfFormContext logic, host integrations, example app flows, or when you need repo-specific context before changing the platform.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end workflow for adding a new Vant Flow field type or extending an existing field contract. Use when changing FieldType, DocumentField or table-column props, builder property surfaces, renderer field rendering, form-context behavior, schema examples, or tests related to field capabilities.
Builder authoring workflow guidance for Vant Flow. Use when working on VfBuilder, VfBuilderState, property editor behavior, palette options, schema import or export, preview mode, preview metadata, or script-authoring surfaces in the builder UI.
Renderer, frm scripting, validation, actions, and host integration guidance for Vant Flow. Use when working on VfRenderer, VfFormContext, client-script behavior, metadata-driven logic, action buttons, link field loading, media handlers, or runtime field and section state.
Test strategy for Vant Flow platform changes. Use when modifying builder state, property editing, renderer lifecycle, frm APIs, field rendering, host integrations, stepper behavior, schema packing, or example-driven regression coverage in the Vant Flow library.
| name | vant-flow-core |
| description | Architecture and feature map for the Vant Flow Angular form platform. Use when working on DocumentDefinition schemas, builder or renderer behavior, VfFormContext logic, host integrations, example app flows, or when you need repo-specific context before changing the platform. |
Use this skill to orient on how Vant Flow works before changing code.
references/repo-map.md to find the correct layer.references/feature-map.md if the task changes platform behavior, schema features, or public capabilities.data/docs/architecture-overview.md for cross-cutting workdata/docs/builder-architecture.md for authoring UXdata/docs/renderer-architecture.md for runtime behaviorTreat Vant Flow as one schema-driven platform with four cooperating layers:
projects/vant-flow/src/lib/models/document.model.ts defines the schema and runtime contracts.projects/vant-flow/src/lib/components/builder/* and services/builder-state.service.ts author that schema.projects/vant-flow/src/lib/components/form-renderer/*, form-field.component.ts, and services/form-context.ts execute that schema.examples/vant-flow-demo/* demonstrates real host usage, preview flows, AI scaffolding, and persistence patterns.Prefer changes that preserve that separation. Do not bury host-owned concerns inside the schema layer when they belong to renderer inputs or host callbacks.
DocumentDefinition.frm APIs additive and consistent with the existing Frappe-like naming style.vant-flow-add-field when adding a new field type, a new field property, or changing how a field behaves across builder and renderer.vant-flow-runtime for VfRenderer, VfFormContext, frm APIs, actions, validation, link fields, media hooks, or metadata-driven behavior.vant-flow-builder for builder state, property editor, preview mode, schema import/export, or authoring interactions.vant-flow-testing whenever behavior changes and tests need to be added or updated.projects/vant-flow/src/public-api.ts still make sense.