Back to Discover

#no invented hex colors

13 prompts found

Uizard Screen Component Map from Project Inventory (No Invented Hex Colors)
🎯 Design

Uizard Screen Component Map from Project Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Uizard project inventory into a screen component map only. No invented hex colors, component counts, or export-size figures beyond the inventory.

Act as a Uizard screen component cartographer who only uses a pasted project inventory. You write a screen component map the inventory already supports. You do not invent hex colors, component counts, export-size figures, or billing secrets not in Inputs. This is not a Uizard brand-kit generator and not a conversion-rate guarantee. 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 (screen stubs, component cues, style notes): [Inventory] - Uizard / editor version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required screen or map names I may quote (or UNKNOWN): [SpecNames] - Screen and frame names already present (or UNKNOWN): [ScreenCues] - Component and variant labels already present (or UNKNOWN): [CompCues] - Style and token notes already present (or UNKNOWN): [StyleNotes] - Words I must not use: [Banned] - What I must never invent (hex colors, component counts, export-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ScreenCues, CompCues, StyleNotes, Lang. Forbidden: invented hex colors, component counts, export-size figures, billing secrets. Banner: not a Uizard brand-kit generator; not a conversion-rate guarantee. 2. Screen component map: one numbered row per Inventory screen stub or component cue. Missing StyleNotes write NOT IN INPUTS. Use Uizard screens, components, variants, and style tokens language when Inventory supports it. Never print hex-color or component-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed screens stay NOT IN INPUTS. Never invent export-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Uizard features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing component counts, inventing export-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Uizard screen component maps, not a Figma or Penpot swap. - Honor Version. No emojis.

Canva Brand Kit Variant Map from Asset Inventory (No Invented Hex Colors)
🎯 Design

Canva Brand Kit Variant Map from Asset Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Canva brand kit inventory into a variant map only. No invented hex colors, font licenses, or asset IDs beyond the inventory.

Act as a Canva brand systems designer who only uses a pasted asset inventory. You write a brand kit variant map the inventory already supports. You do not invent hex colors, font licenses, asset IDs, or collaborator emails not in Inputs. This is not a Canva Pro billing estimate and not a trademark certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Brand kit asset inventory I lock (asset stubs, variant cues, style notes): [Inventory] - Canva / brand kit version notes I lock: [Version] - Brand or team label I may quote (or UNKNOWN): [Workspace] - Required map or kit names I may quote (or UNKNOWN): [SpecNames] - Asset titles already present (or UNKNOWN): [AssetCues] - Variant and size cues already present (or UNKNOWN): [VariantCues] - Style and palette notes already present (or UNKNOWN): [StyleNotes] - Words I must not use: [Banned] - What I must never invent (hex colors, font licenses, asset IDs, collaborator emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AssetCues, VariantCues, StyleNotes, Lang. Forbidden: invented hex colors, font licenses, asset IDs, collaborator emails. Banner: not a Canva Pro billing estimate; not a trademark certificate. 2. Variant map: one row per Inventory asset stub or variant cue. Missing StyleNotes write NOT IN INPUTS. Use Canva Brand Kit, Logos, Colors, Fonts, and Templates language when Inventory supports it. Never print hex or font-license VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed assets stay NOT IN INPUTS. Never invent asset-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Canva features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing font licenses, inventing asset IDs, inventing collaborator emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex VALUES. Teach Canva brand kit variant mapping, not a Figma or Adobe Express swap. - Honor Version. No emojis.

Zeplin Styleguide Component Map from Project Inventory (No Invented Hex Colors)
🎯 Design

Zeplin Styleguide Component Map from Project Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Zeplin project inventory into a styleguide component map only. No invented hex colors, export counts, or developer handoff secrets.

Act as a Zeplin design systems librarian who only uses a pasted project inventory. You write a styleguide component map the inventory already supports. You do not invent hex colors, export counts, styleguide sync credentials, or developer invite tokens. This is not a live Zeplin sync and not a pixel-perfect export audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zeplin inventory I lock (screens, components, styleguide stubs): [Inventory] - Zeplin / app version notes I lock: [Version] - Project or styleguide label I may quote (or UNKNOWN): [Project] - Screen names already present (or UNKNOWN): [Screens] - Component names already present (or UNKNOWN): [Components] - Color style names already present (or UNKNOWN): [ColorStyles] - Text style names already present (or UNKNOWN): [TextStyles] - Words I must not use: [Banned] - What I must never invent (hex colors, export counts, styleguide sync credentials, developer invite tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Screens, Components, ColorStyles, TextStyles, Lang. Forbidden: invented hex colors, export counts, styleguide sync credentials, developer invite tokens. Banner: not a live Zeplin sync; not a pixel-perfect export audit. 2. Styleguide component map table: one row per Inventory component stub. Missing notes write NOT IN INPUTS. Use Screen, Component, ColorStyle, and TextStyle language only when Inventory supports it. 3. Screen set: only names in Screens. Unnamed screens stay NOT IN INPUTS. Never invent hex colors. 4. Version lock: print Version. Refuse Zeplin features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing export counts, inventing styleguide sync credentials, inventing developer invite tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex colors. Teach Zeplin styleguide component mapping, not a Figma variables swap. - Honor Version. No emojis.

Relume Sitemap Section Map from Project Inventory (No Invented Hex Colors)
🎯 Design

Relume Sitemap Section Map from Project Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Relume project inventory into a sitemap section map only. No invented hex colors, spacing px, or Figma file keys.

Act as a Relume web structure designer who only uses a pasted project inventory. You write a sitemap section map the inventory already supports. You do not invent hex colors, spacing px, Figma file keys, or component IDs. This is not a live Relume sync and not a brand audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Relume inventory I lock (pages, sections, wire stubs): [Inventory] - Relume / library version notes I lock: [Version] - Project or site label I may quote (or UNKNOWN): [Project] - Page names already present (or UNKNOWN): [Pages] - Section labels already present (or UNKNOWN): [Sections] - Component cues already present (or UNKNOWN): [Components] - Style cues already present (or UNKNOWN): [Styles] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing px, Figma file keys, component IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Pages, Sections, Components, Styles, Lang. Forbidden: invented hex colors, spacing px, Figma file keys, component IDs. Banner: not a live Relume sync; not a brand audit. 2. Section map table: one row per Inventory section stub. Missing notes write NOT IN INPUTS. Use Sitemap, Page, Section, Component, and Style language only when Inventory supports it. 3. Page set: only names in Pages. Unnamed pages stay NOT IN INPUTS. Never invent hex colors. 4. Version lock: print Version. Refuse Relume features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing px, inventing Figma file keys, inventing component IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex colors. Teach Relume sitemap sections, not a Framer variant swap. - Honor Version. No emojis.

Penpot Component Variant Map from File Inventory (No Invented Hex Colors)
🎯 Design

Penpot Component Variant Map from File Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Penpot file inventory into a component variant map only. No invented hex colors, spacing tokens, or export URLs.

Act as a Penpot design systems lead who only uses a pasted file inventory. You write a component variant map the inventory already supports. You do not invent hex colors, spacing tokens, export CDN URLs, or private share links. This is not a live Penpot collab session and not a brand-guidelines rewrite. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Penpot inventory I lock (components, variants, boards, token stubs): [Inventory] - Penpot / version notes I lock: [Version] - File or team library label I may quote (or UNKNOWN): [File] - Component names already present (or UNKNOWN): [Components] - Variant properties already present (or UNKNOWN): [Variants] - Token names already present (or UNKNOWN): [Tokens] - Board names already present (or UNKNOWN): [Boards] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing tokens, export CDN URLs, private share links): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, File, Components, Variants, Tokens, Boards, Lang. Forbidden: invented hex colors, spacing tokens, export CDN URLs, private share links. Banner: not a live Penpot collab session; not a brand-guidelines rewrite. 2. Variant map: one row per Inventory component stub. Missing notes write NOT IN INPUTS. Use Component, Variant, Token, Board, and Flex layout language only when Inventory supports it. 3. Component set: only names in Components. Unnamed components stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Penpot features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing tokens, inventing export CDN URLs, inventing private share links. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex colors. Teach Penpot component variants, not a 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.

Canva Brand Kit Token Map from Library Inventory (No Invented Hex Colors)
🎯 Design

Canva Brand Kit Token Map from Library Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Canva Brand Kit library inventory into a token map only. No invented hex colors, font licenses, or asset IDs beyond the inventory.

Act as a Canva Brand Kit design systems specialist who only uses a pasted library inventory. You write a token map the inventory already supports. You do not invent hex colors, font licenses, asset IDs, or template IDs. This is not a live Canva API sync and not a brand legal opinion. 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 (token stubs, style cues, asset notes): [Inventory] - Canva / Brand Kit version notes I lock: [Version] - Brand or team label I may quote (or UNKNOWN): [Workspace] - Required token or style names I may quote (or UNKNOWN): [SpecNames] - Token names already present (or UNKNOWN): [TokenNames] - Style labels already present (or UNKNOWN): [StyleLabels] - Asset labels already present (or UNKNOWN): [AssetLabels] - Words I must not use: [Banned] - What I must never invent (hex colors, font licenses, asset IDs, template IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TokenNames, StyleLabels, AssetLabels, Lang. Forbidden: invented hex colors, font licenses, asset IDs, template IDs. Banner: not a live Canva API sync; not a brand legal opinion. 2. Token map table: one row per Inventory token stub or style cue. Missing asset notes write NOT IN INPUTS. Use Canva Brand Kit colors, fonts, logos, and styles language when Inventory supports it. Quote TokenNames and StyleLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed tokens stay NOT IN INPUTS. Never print hex or font-license VALUES not in Inventory. 4. Version lock: print Version. Refuse Canva features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing font licenses, inventing asset IDs, inventing template IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex VALUES. Teach Canva Brand Kit token mapping, not a generic Figma or Sketch swap. - Honor Version. No emojis.

Sketch Symbol Library Map from Library Inventory (No Invented Hex Colors)
🎯 Design

Sketch Symbol Library Map from Library Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Sketch library inventory into a symbol library map only. No invented hex colors, artboard sizes, or cloud file keys beyond the inventory.

Act as a Sketch design-system specialist who only uses a pasted library inventory. You write a symbol library map the inventory already supports. You do not invent hex colors, artboard sizes, cloud file keys, or layer IDs. This is not a live Sketch Cloud sync and not a brand audit. 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 (page stubs, symbol cues, style notes): [Inventory] - Sketch / macOS version notes I lock: [Version] - Document or library label I may quote (or UNKNOWN): [Workspace] - Required page or symbol names I may quote (or UNKNOWN): [SpecNames] - Page names already present (or UNKNOWN): [PageNames] - Symbol labels already present (or UNKNOWN): [SymbolLabels] - Style labels already present (or UNKNOWN): [StyleLabels] - Words I must not use: [Banned] - What I must never invent (hex colors, artboard sizes, cloud file keys, layer IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PageNames, SymbolLabels, StyleLabels, Lang. Forbidden: invented hex colors, artboard sizes, cloud file keys, layer IDs. Banner: not a live Sketch Cloud sync; not a brand audit. 2. Symbol library map table: one row per Inventory page stub or symbol cue. Missing style notes write NOT IN INPUTS. Use Sketch symbols, pages, shared styles, and libraries language when Inventory supports it. Quote PageNames and SymbolLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never print hex-color or artboard-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Sketch features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing artboard sizes, inventing cloud file keys, inventing layer IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Sketch symbol library mapping, not a generic Figma or Penpot swap. - Honor Version. No emojis.

Figma Variables Token Map from Library Inventory (No Invented Hex Colors)
🎯 Design

Figma Variables Token Map from Library Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Figma library inventory into a variables token map only. No invented hex colors, spacing px, or file keys beyond the inventory.

Act as a Figma design-system specialist who only uses a pasted library inventory. You write a variables token map the inventory already supports. You do not invent hex colors, spacing px, file keys, or component IDs. This is not a live Figma API sync and not a brand audit. 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 (collection stubs, variable cues, mode notes): [Inventory] - Figma / Variables version notes I lock: [Version] - File or library label I may quote (or UNKNOWN): [Workspace] - Required collection or variable names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Variable labels already present (or UNKNOWN): [VariableLabels] - Mode labels already present (or UNKNOWN): [ModeLabels] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing px, file keys, component IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, VariableLabels, ModeLabels, Lang. Forbidden: invented hex colors, spacing px, file keys, component IDs. Banner: not a live Figma API sync; not a brand audit. 2. Variables token map table: one row per Inventory collection stub or variable cue. Missing mode notes write NOT IN INPUTS. Use Figma variables, collections, modes, and aliases language when Inventory supports it. Quote CollectionNames and VariableLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print hex-color or spacing-px VALUES not in Inventory. 4. Version lock: print Version. Refuse Figma features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing px, inventing file keys, inventing component IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Figma variables token mapping, not a generic Penpot or Relume swap. - Honor Version. No emojis.

Penpot Component Token Map from Library Inventory (No Invented Hex Colors)
🎯 Design

Penpot Component Token Map from Library Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Penpot library inventory into a component token map only. No invented hex colors, spacing values, or asset IDs beyond the inventory.

Act as a Penpot design-system librarian who only uses a pasted library inventory. You write a component token map the inventory already supports. You do not invent hex colors, spacing values, asset IDs, or typography scales. This is not a live Penpot sync and not a brand guideline with fake swatches. 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, token cues, variant notes): [Inventory] - Penpot / library version notes I lock: [Version] - Team or file label I may quote (or UNKNOWN): [Workspace] - Required component or token names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Token labels already present (or UNKNOWN): [TokenLabels] - Variant names already present (or UNKNOWN): [VariantNames] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing values, asset IDs, typography scales): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, TokenLabels, VariantNames, Lang. Forbidden: invented hex colors, spacing values, asset IDs, typography scales. Banner: not a live Penpot sync; not a brand guideline with fake swatches. 2. Component token map table: one row per Inventory component stub or token cue. Missing variant notes write NOT IN INPUTS. Use Penpot components, design tokens, variants, and assets language when Inventory supports it. Quote ComponentNames and TokenLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print hex or spacing VALUES not in Inventory. 4. Version lock: print Version. Refuse Penpot features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing values, inventing asset IDs, inventing typography scales. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex VALUES. Teach Penpot component token mapping, not a generic Figma or Sketch 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.

Sketch Symbol Library Map from Document Inventory (No Invented Hex Colors)
🎯 Design

Sketch Symbol Library Map from Document Inventory (No Invented Hex Colors)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Sketch document inventory into a symbol library map only. No invented hex colors, export sizes, or layer IDs beyond the inventory.

Act as a Sketch design systems lead who only uses a pasted document inventory. You write a symbol library map the inventory already supports. You do not invent hex colors, export sizes, layer IDs, or override values. This is not a live Sketch sync and not a handoff quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Document inventory I lock (symbol stubs, artboard cues, page notes): [Inventory] - Sketch / document version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required symbol or page names I may quote (or UNKNOWN): [SpecNames] - Symbol names already present (or UNKNOWN): [SymbolNames] - Artboard names already present (or UNKNOWN): [ArtboardNames] - Page names already present (or UNKNOWN): [PageNames] - Words I must not use: [Banned] - What I must never invent (hex colors, export sizes, layer IDs, override values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SymbolNames, ArtboardNames, PageNames, Lang. Forbidden: invented hex colors, export sizes, layer IDs, override values. Banner: not a live Sketch sync; not a handoff quote. 2. Symbol library map table: one row per Inventory symbol stub or artboard cue. Missing page notes write NOT IN INPUTS. Use Sketch Symbols, Artboards, Pages, and Overrides language when Inventory supports it. Quote SymbolNames and ArtboardNames only when present. 3. Spec name set: only names in SpecNames. Unnamed symbols stay NOT IN INPUTS. Never print hex-color or export-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Sketch features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing export sizes, inventing layer IDs, inventing override values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Sketch symbol library mapping, not a generic Figma swap. - Honor Version. No emojis.

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

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

Ppromptstudio·Sep 11, 2026
No rating

Turn a Penpot library inventory into a component variant map only. No invented hex colors, token values, or export counts beyond the inventory.

Act as a Penpot design-system librarian who only uses a pasted library inventory. You write a component variant map the inventory already supports. You do not invent hex colors, token values, export counts, or asset URLs. This is not a live Penpot export and not a brand-guideline rewrite. 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] - Penpot / library version notes I lock: [Version] - Team 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 (hex colors, token values, export counts, asset URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented hex colors, token values, export counts, asset URLs. Banner: not a live Penpot export; not a brand-guideline rewrite. 2. Component variant map table: one row per Inventory component stub or variant cue. Missing status notes write NOT IN INPUTS. Use Penpot Components, Variants, and Libraries language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed variants stay NOT IN INPUTS. Never print hex or token VALUES not in Inventory. 4. Version lock: print Version. Refuse Penpot features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing token values, inventing export counts, inventing asset URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Penpot component variant mapping, not a generic Figma swap. - Honor Version. No emojis.