schema-design

Designs table and object schemas with field types, metadata, and constraints via the Frontline CLI.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill schema-design-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schema-design
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/schema-design
Command: npx skills add https://github.com/api-evangelist/frontline --skill schema-design-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right field type, metadata format, and relation structure when creating or extending Frontline tables and objects is error-prone, and mistakes like wrong select modes, invalid timezones, or immutable column types cause 400 errors and rework. ## Core Features & Use Cases - Field Type Decision Tree: Maps data kinds (text, money, dates, picks, links, files) to the correct Frontline field type and metadata payload. - Select vs Relation Guidance: Explains when to use select options versus object relations or prismaRelation user links, including required metadata keys. - Schema Patterns & Constraints: Provides ready-made patterns for status pipelines, contact info, and financial tracking, plus required/unique constraints and record-type scoping. - Use Case: Before adding an "Industry" field to a Companies object, consult this Skill to create a single-select field, then add colored options with separate option create commands. ## Quick Start Ask the AI to design a schema for a new Frontline object with currency, date, and single-select fields using the Frontline CLI.

Frequently Asked Questions about schema-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a select field with options in Frontline CLI?▼

Create the field with type select and metadata mode singleSelect or multiSelect, then add each value with a separate option create command. Passing options inline in the field-create body is rejected with a 400 error.

When should I use select vs relation fields in Frontline?▼

Use select for short, stable lists of simple labels like Status or Priority. Use relation when values are full records in another object that grow organically and carry their own fields, such as Companies or Contacts.

Can I change a Frontline field type after creation?▼

No, a field's type is fixed once created. To migrate, create a new field with the target type, copy values onto existing records, update dependent views, then delete the old field.

Why does my Frontline date field return a 400 error?▼

Date field metadata requires a timezone from a strict allowlist of IANA names such as UTC or America/New_York. Invalid timezone values or omitting timezone when metadata is present trigger a 400 validation error.

How do I add a field to only one record type in Frontline?▼

Pass record_type_id in the field create JSON payload to scope the field to a single record type. This works only on objects, not tables, and omitting it adds the field to all record types by default.