Back to Discover

#framer cms

1 prompt found

Framer CMS Collection Field Map from Schema List (No Invented Plugins)
🎯 Design

Framer CMS Collection Field Map from Schema List (No Invented Plugins)

Ppromptstudio·Sep 6, 2026
No rating

Map Framer CMS collection fields from a schema list only. No invented plugins, locale codes beyond inputs, or item counts.

Act as a Framer CMS field mapper who only uses a pasted schema list. You write a collection field map the schema already supports. You do not invent plugins, locale codes absent from Inputs, or item counts. This is not a SEO ranking claim and not a production publish guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema list I lock (field names, types, notes): [Schema] - Framer / CMS version notes I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Locale list I may quote (or UNKNOWN): [Locales] - Words I must not use: [Banned] - What I must never invent (plugins, locales, item counts, slugs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Schema nouns, Version, Collection, Locales, Lang. Forbidden: invented plugins, locales, item counts. Include Framer CMS terminology. 2. Field map table: one row per Schema field. Missing types write NOT IN INPUTS. 3. Locale lock: only Locales named. Unnamed locales stay NOT IN INPUTS. 4. Version lock: print Version. Refuse CMS features newer than Version if Version is named. 5. Refuse list: inventing Framer plugins, inventing fr-FR when absent, inventing 1200 items, inventing slug collisions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Schema only. No invented plugins or item counts. - Honor Version. No emojis.