form-designer

form-designer

Design, read, and normalize SmartCMP Angular form schema JSON only. It does not submit requests or save changes.

Current Page Interaction

When this Skill is selected by a SmartCMP form editor Context:

1. Call smartcmp_read_current_form_schema before proposing any change. Do not ask the user for the page URL or form ID.
2. Treat the returned saved schema as the source of truth. Apply only the user's requested changes and preserve unrelated fields, field order, JavaScript strings, unknown keys, visibility rules, and model dependencies.
3. Pass the complete updated schema through smartcmp_design_form_schema with mode=modify before answering.
4. Return the complete normalized replacement schema. Never use ellipses, snippets, diffs, or summaries in place of unchanged schema content.
5. State that the output is for manual review and copying back to CMP. Do not claim that the form was saved, updated, or published.

Boundaries

• No submit/approve/status workflows.
• No CMP form writes: no POST, PUT, PATCH, DELETE, publish, save, or delete.
• Form URLs are read-only source material.
• In an embedded form editor, any explicit form_url must identify the same form as the server-owned page Context. The URL tools reject a different form before issuing a Provider request. Ordinary non-embedded Chat URL workflows remain supported through the selected Provider instance.

Workflow

• New form: if the user gave enough fields, do not read CMP or call datasource tools. Build complete schema_json, then call smartcmp_design_form_schema with mode=new.
• Bare form edit/design URL: inspect only. Call smartcmp_read_form_schema; do not design.
• URL plus full field-set or schema-shape changes: treat this as new-form generation with one extra read step. First call smartcmp_read_form_schema to understand the current form, then generate a fresh complete replacement schema from the user's latest requirements and call design with mode=regenerate. Use the old schema only as context; do not patch, splice, or preserve existing fields/JavaScript unless the user explicitly asks to keep them.
• URL plus deterministic projection/composition changes: after the read step, call smartcmp_design_form_schema with mode=modify, form_url, and value_expressions_json. This lets the tool load the source schema and replace the target expression with the hardened runtime expression instead of asking the LLM to hand-copy the old schema or JavaScript.
• mode=modify is only for complete caller-provided JSON, deterministic catalog_fields_json insertion, or deterministic value_expressions_json updates into a supplied schema_json or form_url source. Never call mode=modify with only mode or only insertion/update JSON; that would create an incomplete replacement schema.
• If a read result warns that a field expression is not function(model, sourceParams, schema, unused, cfg), do not answer by hand-writing a replacement schema_json with another legacy signature such as function(formInRet, schemas, widget, injection). For catalog/model value rewrites, use value_expressions_json; for custom JavaScript, provide a complete modern-signature expression that writes model[fieldKey].
• If read/design output reports designMode, modelKeys, or componentCount, tell the user the source form has visual-designer/model state that can preserve stale runtime values even when the schema expression changes. The generated schema is still a manual replacement draft; SmartCMP persistence and visual designer state must be reviewed in CMP.