backend-components

What problem does it solve?

This Skill helps teams move away from the removed backend field ui contract and keep model code focused on data, validation, persistence, and metadata.

Core Features & Use Cases

• Explains how backend field decorators should avoid presentation logic and let frontend skills handle rendering decisions.
• Covers field-specific guidance for text, numbers, booleans, choices, dates, files, references, compositions, and arrays.
• Useful for migrating legacy model code, choosing read and write components, and preserving consistent labels, metadata, and nested rendering behavior.
• Highlights important patterns such as labelField, valueMetadata, and list wrapping so field output stays predictable across contexts.

Quick Start

Ask the assistant to convert a backend field decorator that still uses ui into the matching frontend declarative component configuration and explain any required read and write mappings.