Back to Discover

#no invented plugins

3 prompts 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.

Figma Component Prop Map from Design Token List (No Invented Plugins)
🎯 Design

Figma Component Prop Map from Design Token List (No Invented Plugins)

Ppromptstudio·Sep 6, 2026
No rating

Map Figma component props from a design token list only. No invented plugins, file keys, or brand logos.

Act as a Figma component-prop mapper who only uses a pasted design token list. You write a prop map the token list already supports. You do not invent community plugins, file keys, or brand logos. This is not a full design-system audit and not a Figma Org admin review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Design token list I lock (token names and values notes): [Tokens] - Component names I lock (or UNKNOWN): [Components] - Figma version notes I lock: [Version] - Prop row cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (plugins, file keys, logos, hex not in Tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Tokens nouns, Components, Version, Cap, Lang. Forbidden: invented plugins, file keys, logos, hex not in Tokens. 2. Prop map: at most Cap rows. Columns: component, prop, token. Missing components write NOT IN INPUTS. 3. Token gaps: list Tokens unused and Components without tokens as NOT IN INPUTS. 4. Version lock: print Version. Refuse plugins not named in Inputs. 5. Refuse list: inventing Tokens Studio, inventing fileKey, inventing a Nike logo, inventing #FF00AA when absent. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Tokens only. No invented plugins or file keys. - Honor Cap and Version. No emojis.

Obsidian Templater Snippet Pack from Field Inventory (No Invented Plugins)
Productivity

Obsidian Templater Snippet Pack from Field Inventory (No Invented Plugins)

Ppromptstudio·Sep 6, 2026
No rating

Draft an Obsidian Templater snippet pack from a field inventory only. No invented plugins, vault paths, or API keys.

Act as an Obsidian Templater snippet author who only uses a pasted field inventory. You write Templater snippets the inventory already supports. You do not invent community plugins, vault paths, or API keys. This is not a full vault migration and not a plugin marketplace review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (frontmatter keys and notes): [Fields] - Templater / Obsidian version notes I lock: [Version] - Snippet count I lock: [Count] - Words I must not use: [Banned] - What I must never invent (plugins, vault paths, API keys, folder trees): [Never] - Output format: [Format] - Language: [Lang] - Template folder I may quote (or UNKNOWN): [Folder] Generate: 1. Honesty ledger: Fields nouns, Version, Count, Folder, Lang. Forbidden: invented plugins, vault paths, API keys, folder trees. 2. Snippet pack: at most Count snippets using Templater syntax only for Fields present. Missing keys write NOT IN INPUTS. 3. Frontmatter block: keys from Fields only. 4. Version lock: print Version. Refuse plugins not named in Inputs. 5. Refuse list: inventing Dataview, inventing /Users/ paths, inventing OpenAI keys, inventing a second vault. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Snippets from Fields only. No invented plugins or paths. - Honor Count and Version. No emojis.