filemaker-field-xmllisted

Use this skill whenever the user wants to work with FileMaker schema definition XML — field definitions, table definitions, or value list definitions. This includes generating paste-ready field definitions (fmxmlsnippet type FMObjectList containing Field elements) for the Fields tab, complete tables (BaseTable elements) for the Tables tab, or value list definitions (ValueList elements) for Manage Value Lists; reviewing any of these for silent paste-handler failures; or analysing them from Save as XML (SaXML) exports. Trigger any time the user mentions FileMaker fields, tables, value lists, Manage Database paste, BaseTable, ValueList, auto-enter, field validation, calculation fields, summary fields, or schema scaffolding. Do not attempt FileMaker schema XML from memory alone.
andykear/FileMaker-XML-field-definitions · ★ 7 · Data & Documents · score 66

Install: claude install-skill andykear/FileMaker-XML-field-definitions

# FileMaker Schema Definition XML Skill A deterministic, empirically verified foundation for generating and analysing FileMaker's three schema-definition XML catalogs, all carried in the `fmxmlsnippet type="FMObjectList"` clipboard format: - **Field definitions** — `<Field>` elements, pasted on the **Fields tab** of Manage Database. - **Table definitions** — `<BaseTable>` elements wrapping complete tables, pasted on the **Tables tab**. - **Value list definitions** — `<ValueList>` elements, pasted into **Manage Value Lists**. Created by Andrew Kear of Clockwork Creative Technology and shared openly with the FileMaker/Claris community. Licence: CC BY 4.0. ## Critical rules (enforced before generating) 1. **Unique field IDs, scoped per table.** Assign unique sequential `id` values (from 1) within each table. Duplicate IDs within a table cause silent drops when calculation auto-enter fields reference each other. In multi-table snippets, sibling `<BaseTable>` elements each restart at `id="1"` — that is FileMaker's own format, not an error. 2. **Field→value-list references.** The `<ValueList>` child element inside a field's validation is only preserved when the referenced value list ID exists in the target file at paste time. When the target file is unknown, omit it and tell the user to assign the value list manually after pasting. (This is the field-side *reference*; the value list *definition* format is a separate catalog — see the value list spec.) 3. **Furigana dependency.