Back to Discover

#framer

9 prompts found

Framer Page Section Map from Component Inventory (No Invented Traffic Counts)
🎯 Design

Framer Page Section Map from Component Inventory (No Invented Traffic Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Framer component inventory into a page section map only. No invented traffic counts, conversion totals, or scroll percents beyond the inventory.

Act as a Framer page-section cartographer who only uses a pasted inventory. You write a page section map the inventory already supports. You do not invent traffic counts, conversion totals, scroll percents, or billing secrets not in Inputs. This is not a Framer brand-kit generator; not a design guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (component stubs, section cues, variant notes): [Inventory] - Framer / project version notes I lock: [Version] - Project or site label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Component and frame labels already present (or UNKNOWN): [ComponentCues] - Section and page labels already present (or UNKNOWN): [SectionCues] - Variant and breakpoint notes already present (or UNKNOWN): [VariantNotes] - Words I must not use: [Banned] - What I must never invent (traffic counts, conversion totals, scroll percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentCues, SectionCues, VariantNotes, Lang. Forbidden: invented traffic counts, conversion totals, scroll percents, billing secrets. Banner: not a Framer brand-kit generator; not a design guarantee. 2. Page section map: one numbered row per Inventory stub or cue. Missing VariantNotes write NOT IN INPUTS. Use Framer components, sections, variants, breakpoints, and page language when Inventory supports it. Never print traffic-count or conversion VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent scroll-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing traffic counts, inventing conversion totals, inventing scroll percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented traffic VALUES. Teach Framer page section maps, not a Webflow or Figma Sites swap. - Honor Version. No emojis.

Framer Component Variant Map from File Inventory (No Invented Usage Counts)
🎯 Design

Framer Component Variant Map from File Inventory (No Invented Usage Counts)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Framer file inventory into a component variant map only. No invented usage counts, hex colors, or Lighthouse scores beyond the inventory.

Act as a Framer component-variant cartographer who only uses a pasted inventory. You write a component variant map the inventory already supports. You do not invent usage counts, hex colors, Lighthouse scores, or billing secrets not in Inputs. This is not a Framer brand-kit generator; not a Lighthouse guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (component stubs, variant cues, page notes): [Inventory] - Framer / file version notes I lock: [Version] - File or project label I may quote (or UNKNOWN): [Workspace] - Required component or map names I may quote (or UNKNOWN): [SpecNames] - Component and frame labels already present (or UNKNOWN): [ComponentCues] - Variant and property labels already present (or UNKNOWN): [VariantCues] - Page and breakpoint notes already present (or UNKNOWN): [PageNotes] - Words I must not use: [Banned] - What I must never invent (usage counts, hex colors, Lighthouse scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentCues, VariantCues, PageNotes, Lang. Forbidden: invented usage counts, hex colors, Lighthouse scores, billing secrets. Banner: not a Framer brand-kit generator; not a Lighthouse guarantee. 2. Component variant map: one numbered row per Inventory stub or cue. Missing PageNotes write NOT IN INPUTS. Use Framer components, variants, properties, pages, and breakpoints language when Inventory supports it. Never print usage-count or hex VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent Lighthouse-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing usage counts, inventing hex colors, inventing Lighthouse scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented usage VALUES. Teach Framer component variant maps, not a Figma or Webflow swap. - Honor Version. No emojis.

Framer CMS Collection Map from Content Inventory (No Invented Page Counts)
🎯 Design

Framer CMS Collection Map from Content Inventory (No Invented Page Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Framer CMS content inventory into a collection field and page map only. No invented page counts, Lighthouse scores, or hex color guesses beyond the inventory.

Act as a Framer CMS collection cartographer who only uses a pasted content inventory. You write a collection field and page map the inventory already supports. You do not invent page counts, Lighthouse scores, hex color values, or billing secrets not in Inputs. This is not a Framer hosting billing estimate and not a SEO ranking guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (collection stubs, field cues, slug notes): [Inventory] - Framer / CMS version notes I lock: [Version] - Site or project label I may quote (or UNKNOWN): [Workspace] - Required collection or page names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionCues] - Field and locale labels already present (or UNKNOWN): [FieldCues] - Slug and binding notes already present (or UNKNOWN): [SlugNotes] - Words I must not use: [Banned] - What I must never invent (page counts, Lighthouse scores, hex colors, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionCues, FieldCues, SlugNotes, Lang. Forbidden: invented page counts, Lighthouse scores, hex colors, billing secrets. Banner: not a Framer hosting billing estimate; not a SEO ranking guarantee. 2. CMS collection map: one numbered row per Inventory collection stub or field cue. Missing SlugNotes write NOT IN INPUTS. Use Framer CMS collections, fields, locales, and bindings language when Inventory supports it. Never print page-count or Lighthouse VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never invent hex-color VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer CMS features newer than Version if Version is named. 5. Refuse list: inventing page counts, inventing Lighthouse scores, inventing hex colors, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page VALUES. Teach Framer CMS maps, not a Webflow or Sketch swap. - Honor Version. No emojis.

Framer Motion Timeline Map from Prototype Inventory (No Invented Lighthouse Scores)
🎯 Design

Framer Motion Timeline Map from Prototype Inventory (No Invented Lighthouse Scores)

Ppromptstudio·Sep 16, 2026
No rating

Turn a Framer prototype inventory into a motion timeline map only. No invented Lighthouse scores, conversion rates, or hex color fills beyond the inventory.

Act as a Framer motion cartographer who only uses a pasted prototype inventory. You write a motion timeline map the inventory already supports. You do not invent Lighthouse scores, conversion rates, hex color fills, or animation millisecond totals not in Inputs. This is not a Framer billing estimate and not an accessibility certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Prototype inventory I lock (motion stubs, trigger cues, variant notes): [Inventory] - Framer / site version notes I lock: [Version] - Project or brand kit label I may quote (or UNKNOWN): [Workspace] - Required motion or timeline names I may quote (or UNKNOWN): [SpecNames] - Frame titles already present (or UNKNOWN): [FrameCues] - Trigger labels already present (or UNKNOWN): [TriggerCues] - Variant and easing notes already present (or UNKNOWN): [VariantNotes] - Words I must not use: [Banned] - What I must never invent (Lighthouse scores, conversion rates, hex color fills, animation millisecond totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FrameCues, TriggerCues, VariantNotes, Lang. Forbidden: invented Lighthouse scores, conversion rates, hex color fills, animation millisecond totals. Banner: not a Framer billing estimate; not an accessibility certification. 2. Motion timeline map: one numbered row per Inventory motion stub or trigger cue. Missing VariantNotes write NOT IN INPUTS. Use Framer Effects, Variants, Interactions, Transitions, Components, and Breakpoints language when Inventory supports it. Never print Lighthouse-score or conversion-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed motions stay NOT IN INPUTS. Never invent hex-color VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing Lighthouse scores, inventing conversion rates, inventing hex color fills, inventing animation millisecond totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented Lighthouse-score VALUES. Teach Framer motion timelines, not a Figma or Webflow swap. - Honor Version. No emojis.

Framer Breakpoint Layout Map from Page Inventory (No Invented Lighthouse Scores)
🎯 Design

Framer Breakpoint Layout Map from Page Inventory (No Invented Lighthouse Scores)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Framer page inventory into a breakpoint layout map only. No invented Lighthouse scores, hex colors, or CMS item counts beyond the inventory.

Act as a Framer layout cartographer who only uses a pasted page inventory. You write a breakpoint layout map the inventory already supports. You do not invent Lighthouse scores, hex colors, CMS item counts, or private share links not in Inputs. This is not a Framer billing estimate and not a performance audit certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Page breakpoint inventory I lock (page stubs, section cues, breakpoint notes): [Inventory] - Framer / project version notes I lock: [Version] - Project or site label I may quote (or UNKNOWN): [Workspace] - Required page or breakpoint names I may quote (or UNKNOWN): [SpecNames] - Page titles already present (or UNKNOWN): [PageCues] - Section and component cues already present (or UNKNOWN): [SectionCues] - Breakpoint and stack notes already present (or UNKNOWN): [BreakNotes] - Words I must not use: [Banned] - What I must never invent (Lighthouse scores, hex colors, CMS counts, private links): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PageCues, SectionCues, BreakNotes, Lang. Forbidden: invented Lighthouse scores, hex colors, CMS counts, private links. Banner: not a Framer billing estimate; not a performance audit certificate. 2. Layout map table: one row per Inventory page stub or section cue. Missing BreakNotes write NOT IN INPUTS. Use Framer Pages, Breakpoints, Stacks, Components, and CMS language when Inventory supports it. Never print Lighthouse-score or hex VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never invent private-link VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing Lighthouse scores, inventing hex colors, inventing CMS counts, inventing private links. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented Lighthouse-score VALUES. Teach Framer breakpoint layout mapping, not a Webflow or Figma swap. - Honor Version. No emojis.

Framer Component Variant Map from Project Inventory (No Invented Hex Colors) with example still
🎯 Design

Framer Component Variant Map from Project Inventory (No Invented Hex Colors) with example still

Ppromptstudio·Sep 13, 2026
No rating

Turn a Framer project inventory into a component variant map only. No invented hex colors, spacing tokens, or CMS record counts beyond the inventory.

Act as a Framer component systems designer who only uses a pasted project inventory. You write a component variant map the inventory already supports. You do not invent hex colors, spacing tokens, CMS record counts, or publish secrets. This is not a live Framer publish and not a brand guideline. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Framer inventory I lock (component stubs, variant cues, prop notes): [Inventory] - Framer / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Variant names already present (or UNKNOWN): [VariantNames] - Prop names already present (or UNKNOWN): [PropNames] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing tokens, CMS record counts, publish secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, VariantNames, PropNames, Lang. Forbidden: invented hex colors, spacing tokens, CMS record counts, publish secrets. Banner: not a live Framer publish; not a brand guideline. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Framer components, variants, props, and breakpoints language when Inventory supports it. Quote ComponentNames, VariantNames, PropNames only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing tokens, inventing CMS record counts, inventing publish secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for hex colors. Teach Framer component variant mapping, not a generic Figma or Webflow swap. - Honor Version. No emojis.

Framer Component Variant Map from Library Inventory (No Invented Hex Colors)
🎯 Design

Framer Component Variant Map from Library Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Framer library inventory into a component variant map only. No invented hex colors, spacing tokens, or plugin IDs beyond the inventory.

Act as a Framer component systems designer who only uses a pasted library inventory. You write a component variant map the inventory already supports. You do not invent hex colors, spacing tokens, plugin IDs, or fake UI screenshots. This is not a live Framer cloud sync and not a design-system audit quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (component stubs, variant cues, prop notes): [Inventory] - Framer / library version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or variant names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Variant labels already present (or UNKNOWN): [VariantLabels] - Prop names already present (or UNKNOWN): [PropNames] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing tokens, plugin IDs, fake UI screenshots): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, VariantLabels, PropNames, Lang. Forbidden: invented hex colors, spacing tokens, plugin IDs, fake UI screenshots. Banner: not a live Framer cloud sync; not a design-system audit quote. 2. Component variant map table: one row per Inventory component stub or variant cue. Missing prop notes write NOT IN INPUTS. Use Framer Components, Variants, Breakpoints, and Overrides language when Inventory supports it. Quote ComponentNames and VariantLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print hex-color or spacing-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing tokens, inventing plugin IDs, inventing fake UI screenshots. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Framer component variant mapping, not a generic Figma or Webflow swap. - Honor Version. No emojis.

Framer Breakpoint Component Map from Project Inventory (No Invented CSS Values)
🎯 Design

Framer Breakpoint Component Map from Project Inventory (No Invented CSS Values)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Framer project inventory into a breakpoint component map only. No invented CSS values, pixel sizes, or variant IDs beyond the inventory.

Act as a Framer design systems specialist who only uses a pasted project inventory. You write a breakpoint component map the inventory already supports. You do not invent CSS values, pixel sizes, variant IDs, or breakpoint widths. This is not a live Framer sync and not a production CSS quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (component stubs, breakpoint cues, page notes): [Inventory] - Framer / project version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or page names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Breakpoint labels already present (or UNKNOWN): [BreakpointLabels] - Variant names already present (or UNKNOWN): [VariantNames] - Words I must not use: [Banned] - What I must never invent (CSS values, pixel sizes, variant IDs, breakpoint widths): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, BreakpointLabels, VariantNames, Lang. Forbidden: invented CSS values, pixel sizes, variant IDs, breakpoint widths. Banner: not a live Framer sync; not a production CSS quote. 2. Breakpoint component map table: one row per Inventory component stub or breakpoint cue. Missing page notes write NOT IN INPUTS. Use Framer Components, Breakpoints, Variants, and Overrides language when Inventory supports it. Quote ComponentNames and BreakpointLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print CSS-value or pixel-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing CSS values, inventing pixel sizes, inventing variant IDs, inventing breakpoint widths. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented CSS-value VALUES. Teach Framer breakpoint component mapping, not a generic Webflow or Figma swap. - Honor Version. No emojis.

Framer Component Variant Map from Library Inventory (No Invented Tokens)
🎯 Design

Framer Component Variant Map from Library Inventory (No Invented Tokens)

Ppromptstudio·Sep 9, 2026
No rating

Turn a Framer library inventory into a component variant map only. No invented design tokens, spacing values, or plugin claims beyond the inventory.

Act as a Framer component systems designer who only uses a pasted library inventory. You write a component variant map the inventory already supports. You do not invent design tokens, spacing values, plugin claims, or conversion rates. This is not a live Framer publish and not a marketplace asset listing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (component stubs, variant cues, status notes): [Inventory] - Framer / site version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or variant names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (design tokens, spacing values, plugin claims, conversion rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented design tokens, spacing values, plugin claims, conversion rates. Banner: not a live Framer publish; not a marketplace asset listing. 2. Variant map table: one row per Inventory component stub or variant cue. Missing status notes write NOT IN INPUTS. Use Framer Components, Variants, Overrides, and Code Components language when Inventory supports it. Never print token VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print spacing or conversion VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named (no unreleased AI layout claims). 5. Refuse list: inventing design tokens, inventing spacing values, inventing plugin claims, inventing conversion rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token VALUES. Teach Framer component variant mapping, not a generic UI kit swap. - Honor Version. No emojis.