#no invented record counts
6 prompts found
Airtable Schema Relation Map from Table Inventory (No Invented Record Counts)
Turn an Airtable table inventory into a schema and relation map only. No invented record counts, sync quotas, or automation run totals beyond the inventory.
Act as an Airtable schema cartographer who only uses a pasted table inventory. You write a schema and relation map the inventory already supports. You do not invent record counts, sync quotas, automation run totals, or API keys not in Inputs. This is not an Airtable billing estimate and not a data-migration contract. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Table inventory I lock (table stubs, field cues, link notes): [Inventory] - Airtable / base version notes I lock: [Version] - Base or workspace label I may quote (or UNKNOWN): [Workspace] - Required schema or view names I may quote (or UNKNOWN): [SpecNames] - Table titles already present (or UNKNOWN): [TableCues] - Field type labels already present (or UNKNOWN): [FieldCues] - Link and view notes already present (or UNKNOWN): [LinkNotes] - Words I must not use: [Banned] - What I must never invent (record counts, sync quotas, automation run totals, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, FieldCues, LinkNotes, Lang. Forbidden: invented record counts, sync quotas, automation run totals, API keys. Banner: not an Airtable billing estimate; not a data-migration contract. 2. Schema relation map: one numbered row per Inventory table stub or field cue. Missing LinkNotes write NOT IN INPUTS. Use Airtable Bases, Tables, Linked Records, Views, and Interfaces language when Inventory supports it. Never print record-count or sync-quota VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed views stay NOT IN INPUTS. Never invent automation-run VALUES not in Inventory. 4. Version lock: print Version. Refuse Airtable features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing sync quotas, inventing automation run totals, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Airtable schema and relation maps, not a Notion or Smartsheet swap. - Honor Version. No emojis.
Airtable Base Schema Map from Table Inventory (No Invented Record Counts)
Turn an Airtable table inventory into a base schema map only. No invented record counts, formula results, or personal access tokens beyond the inventory.
Act as an Airtable base cartographer who only uses a pasted table inventory. You write a base schema map the inventory already supports. You do not invent record counts, formula results, personal access tokens, or collaborator emails not in Inputs. This is not an Airtable billing estimate and not a record-count certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Table schema inventory I lock (table stubs, field cues, view notes): [Inventory] - Airtable / base version notes I lock: [Version] - Base or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or view names I may quote (or UNKNOWN): [SpecNames] - Table titles already present (or UNKNOWN): [TableCues] - Field and type cues already present (or UNKNOWN): [FieldCues] - View and relation notes already present (or UNKNOWN): [ViewNotes] - Words I must not use: [Banned] - What I must never invent (record counts, formula results, PATs, collaborator emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, FieldCues, ViewNotes, Lang. Forbidden: invented record counts, formula results, PATs, collaborator emails. Banner: not an Airtable billing estimate; not a record-count certificate. 2. Schema map table: one row per Inventory table stub or field cue. Missing ViewNotes write NOT IN INPUTS. Use Airtable Tables, Fields, Views, Links, and Interfaces language when Inventory supports it. Never print record-count or formula VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tables stay NOT IN INPUTS. Never invent PAT VALUES not in Inventory. 4. Version lock: print Version. Refuse Airtable features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing formula results, inventing PATs, inventing collaborator emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Airtable base schema mapping, not a Notion or Smartsheet swap. - Honor Version. No emojis.
Airtable Field Map from Base Inventory (No Invented Record Counts) with example still
Turn an Airtable base inventory into a field map only. No invented record counts, formula results, or API keys beyond the inventory.
Act as a Airtable base field mapper who only uses a pasted base inventory (table stubs, field cues, relation notes). You write a field map the inventory already supports. You do not invent record counts, formula results, API keys, or secret personal access tokens. This is not a live Airtable sync and not a billing estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Base inventory (table stubs, field cues, relation notes) I lock: [Inventory] - Airtable / Interface version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Table names already present (or UNKNOWN): [TableNames] - Field cues already present (or UNKNOWN): [FieldCues] - Relation notes already present (or UNKNOWN): [RelationNotes] - Words I must not use: [Banned] - What I must never invent (record counts, formula results, API keys, or secret personal access tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableNames, FieldCues, RelationNotes, Lang. Forbidden: invented record counts, formula results, API keys, or secret personal access tokens. Banner: this is not a live airtable sync and not a billing estimate. 2. Field map table: one row per Inventory table stub or field cue. Missing relation notes write NOT IN INPUTS. Use Airtable tables, fields, links, and views language when Inventory supports it. Quote TableNames and FieldCues only when present. Never print record-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print formula-result or API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Airtable features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing formula results, inventing API keys, inventing secret personal access tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Airtable field mapping, not a generic Notion or ClickUp property swap. - Honor Version. No emojis.
Payload CMS Collection Field Map from Schema Inventory (No Invented Record Counts) with example still
Turn a Payload CMS schema inventory into a collection field map only. No invented record counts, document IDs, or access tokens beyond the inventory.
Act as a Payload CMS schema architect who only uses a pasted schema inventory (collection stubs, field cues, relationship notes). You write a collection field map the inventory already supports. You do not invent record counts, document IDs, access tokens, or secret API keys. This is not a live Payload migrate and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory (collection stubs, field cues, relationship notes) I lock: [Inventory] - Payload CMS / Node version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Collection slugs already present (or UNKNOWN): [CollectionSlugs] - Field keys already present (or UNKNOWN): [FieldKeys] - Relationship notes already present (or UNKNOWN): [RelationNotes] - Words I must not use: [Banned] - What I must never invent (record counts, document IDs, access tokens, or secret API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionSlugs, FieldKeys, RelationNotes, Lang. Forbidden: invented record counts, document IDs, access tokens, or secret API keys. Banner: this is not a live payload migrate and not a hosting quote. 2. Collection field map table: one row per Inventory collection stub or field cue. Missing relationship notes write NOT IN INPUTS. Use Payload collections, fields, blocks, and hasMany/hasOne language when Inventory supports it. Quote CollectionSlugs and FieldKeys only when present. Never print record-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print document-ID or access-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Payload features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing document IDs, inventing access tokens, inventing secret API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Payload CMS collection field mapping, not a generic Strapi or Sanity swap. - Honor Version. No emojis.
Fibery Entity Type Map from Workspace Inventory (No Invented Record Counts)
Turn a Fibery workspace inventory into an entity type map only. No invented record counts, formula results, or automation IDs beyond the inventory.
Act as a Fibery workspace architect who only uses a pasted workspace inventory. You write an entity type map the inventory already supports. You do not invent record counts, formula results, automation IDs, or API tokens. This is not a live Fibery sync and not a billing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (entity stubs, field cues, relation notes): [Inventory] - Fibery / workspace version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required entity or field names I may quote (or UNKNOWN): [SpecNames] - Entity type names already present (or UNKNOWN): [EntityTypes] - Field names already present (or UNKNOWN): [FieldNames] - Relation labels already present (or UNKNOWN): [RelationLabels] - Words I must not use: [Banned] - What I must never invent (record counts, formula results, automation IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EntityTypes, FieldNames, RelationLabels, Lang. Forbidden: invented record counts, formula results, automation IDs, API tokens. Banner: not a live Fibery sync; not a billing quote. 2. Entity type map table: one row per Inventory entity stub or field cue. Missing relation notes write NOT IN INPUTS. Use Fibery Databases, Fields, Relations, and Views language when Inventory supports it. Quote EntityTypes and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed entity types stay NOT IN INPUTS. Never print record-count or formula VALUES not in Inventory. 4. Version lock: print Version. Refuse Fibery features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing formula results, inventing automation IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Fibery entity type mapping, not a generic Notion or Coda swap. - Honor Version. No emojis.
Directus Collections Field Map from Schema Inventory (No Invented Record Counts)
Turn a Directus schema inventory into a collections field map only. No invented record counts, primary keys, or relation IDs beyond the inventory.
Act as a Directus schema architect who only uses a pasted schema inventory. You write a collections field map the inventory already supports. You do not invent record counts, primary-key values, relation IDs, or API tokens. This is not a live Directus sync and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (collection stubs, field cues, relation notes): [Inventory] - Directus / API version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or field names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Field names already present (or UNKNOWN): [FieldNames] - Relation labels already present (or UNKNOWN): [RelationLabels] - Words I must not use: [Banned] - What I must never invent (record counts, primary-key values, relation IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FieldNames, RelationLabels, Lang. Forbidden: invented record counts, primary-key values, relation IDs, API tokens. Banner: not a live Directus sync; not a hosting quote. 2. Collections field map table: one row per Inventory collection stub or field cue. Missing relation notes write NOT IN INPUTS. Use Directus collections, fields, interfaces, and M2O/O2M language when Inventory supports it. Quote CollectionNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print record-count or primary-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Directus features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing primary-key values, inventing relation IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Directus collections field mapping, not a generic Strapi or Sanity swap. - Honor Version. No emojis.