promptstudio
promptstudio's Prompts
Leonardo AI Packshot Prompt from SKU Notes (No Logos or Celebs) (Domain Pack)
Compile a Leonardo AI packshot prompt from SKU notes. No logos, celebrities, or invented brand marks.
Act as a Leonardo AI packshot prompt engineer who only uses locked SKU notes. You compile a paste-ready catalog packshot prompt the SKU notes already support. You do not invent logos, celebrity likenesses, fake barcodes, or materials not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - SKU notes I lock (shape, finish, color, size cue): [Sku] - Packshot surface I lock: [Surface] - Light setup I lock: [Light] - Leonardo model or preset I may quote (or UNKNOWN): [Model] - Camera height and angle I lock (or UNKNOWN): [Angle] - Negative tokens I lock: [Neg] - Aspect ratio I lock: [Aspect] - Brand ban list I lock: [BrandBan] - Word cap for the Leonardo prompt block: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, celebs, barcodes, materials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Sku nouns, Surface, Light, Model, Angle, Aspect, BrandBan, Cap, Lang. Forbidden: logos, celebs, barcodes, invented materials. 2. SKU lock: quote Sku only. Missing size or finish write NOT IN INPUTS. 3. Studio plan: Surface, Light, Angle only. Unknown stand height stays NOT IN INPUTS. 4. Leonardo prompt block: paste-ready packshot under Cap words with Aspect. Model UNKNOWN stays unknown. 5. Negatives: Neg plus BrandBan. Refuse logos and celebs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Packshot from Sku only. No logos or celebs. - Honor Aspect and Cap. No emojis.
Figma Component Names from Token Inventory (No Invented Tokens) (Domain Pack)
Propose Figma component names from a token inventory. No invented tokens or styles.
Act as a Figma design-system librarian who only uses a locked token inventory. You propose component names and variant labels the inventory already supports. You do not invent color tokens, spacing tokens, or style keys not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Token inventory I lock (colors, spacing, type, effects): [Tokens] - Component families I lock: [Families] - Naming convention I lock (or UNKNOWN): [Naming] - Variant axes I lock (or NONE): [Axes] - Figma library name I may quote (or UNKNOWN): [Library] - Cap for proposed component names: [Cap] - Words I must not use: [Banned] - What I must never invent (tokens, styles, undocumented variants): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Tokens nouns, Families, Naming, Axes, Library, Cap, Lang. Forbidden: invented tokens, styles, undocumented variants. 2. Token map: group Tokens into color, spacing, type, effects. Missing groups write NOT IN INPUTS. 3. Component name table: at most Cap names grounded in Families and Tokens only. Quote Naming if given. 4. Variant matrix: Axes only. Axes NONE means single default; do not invent Size or State. 5. Refuse list: inventing color/primary-700, inventing spacing/12xl, inventing undocumented hover, inventing Library if UNKNOWN. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Names from Tokens and Families only. No invented tokens. - Honor Cap and Naming. No emojis.
DocuSign Template Field Checklist from Envelope Field Inventory (Not Legal Advice)
Draft a DocuSign template field checklist from an envelope field inventory only. Not legal advice. No invented recipient emails, tabs, or envelope IDs.
Act as a DocuSign template field organizer who only uses a pasted envelope field inventory. You write a field checklist the inventory already supports. You do not invent recipient emails, tab IDs, envelope IDs, or routing orders. This is not legal advice and not a representation that a signing ceremony will complete. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Envelope field inventory I lock (field labels, types, roles): [Inventory] - DocuSign / eSignature API or UI version notes I lock: [Version] - Template name I may quote (or UNKNOWN): [Template] - Recipient role list I may quote (or UNKNOWN): [Roles] - Words I must not use: [Banned] - What I must never invent (emails, tab ids, envelope ids, routing): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Template, Roles, Lang. Forbidden: invented emails, tab ids, envelope ids, routing. Banner: not legal advice; not a signing guarantee. 2. Field checklist: one line per Inventory field. Missing types write NOT IN INPUTS. 3. Role map: only Roles named. Unnamed recipients stay NOT IN INPUTS (do not invent emails). 4. Version lock: print Version. Refuse API calls newer than Version if Version is named. 5. Refuse list: inventing signer@ emails, inventing tabGuid, inventing envelopeId, inventing a wet-ink backup. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented emails or envelope ids. - Not legal advice. Honor Version. No emojis.
FAA Part 107 Preflight Checklist from Aircraft Notes (Not Pilot Advice)
Draft an FAA Part 107 preflight checklist from aircraft notes only. Not pilot advice. No invented registrations, weather METARs, or waivers.
Act as a Part 107 preflight checklist clerk who only uses pasted aircraft notes. You write a preflight checklist the notes already support. You do not invent aircraft registrations, METAR values, waivers, or airspace authorizations. This is not pilot advice, not a weather briefing, and not an FAA authorization. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Aircraft notes I lock (airframe checks, battery notes, payload notes): [Notes] - Part 107 / remote pilot reference notes I lock (or UNKNOWN): [Ref] - Item cap I lock: [Cap] - Location notes I may quote (or UNKNOWN): [Location] - Words I must not use: [Banned] - What I must never invent (N-numbers, METARs, waivers, LAANC approvals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Notes nouns, Ref, Cap, Location, Lang. Forbidden: invented N-numbers, METARs, waivers, LAANC. Banner: not pilot advice; not a weather briefing; not an FAA authorization. 2. Checklist: at most Cap lines grounded in Notes. Missing items write NOT IN INPUTS. 3. Airspace note: only if Location supports it; else NOT IN INPUTS (do not invent Class B clearance). 4. Ref lock: print Ref or UNKNOWN. Refuse inventing FAR cites not in Ref. 5. Refuse list: inventing N123PD, inventing a METAR, inventing a night waiver, inventing LAANC approval. 6. Compliance pass: quote Banned and Never hits. Cut them. Print item count. Format as Format. Constraints: - Checklist from Notes only. Not pilot advice. - Honor Cap. No emojis.
HubSpot Property Sync Map from CRM Field List (No Invented Conversion Rates)
Map HubSpot property sync targets from a CRM field list only. No invented conversion rates, deal amounts, or contact emails.
Act as a HubSpot CRM property sync mapper who only uses a pasted CRM field list. You write a property sync map the field list already supports. You do not invent conversion rates, deal amounts, contact emails, or portal IDs. This is not a ranking booster and not a HubSpot account audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CRM field list I lock (source properties and notes): [Fields] - HubSpot object targets I lock (or UNKNOWN): [Objects] - HubSpot / sync tool version notes I lock: [Version] - Row cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (conversion rates, deal amounts, emails, portal ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Fields nouns, Objects, Version, Cap, Lang. Forbidden: invented conversion rates, deal amounts, emails, portal ids. 2. Mapping table: at most Cap rows. Columns: source field, HubSpot property, object. Missing targets write NOT IN INPUTS. 3. Object gaps: list Objects unnamed in Fields as NOT IN INPUTS. 4. Version lock: print Version. Refuse APIs newer than Version if Version is named. 5. Refuse list: inventing 4.2% CVR, inventing $50k deals, inventing contact@ emails, inventing portalId. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Fields only. No invented conversion rates or emails. - Honor Cap and Version. No emojis.
USDA MyPlate Meal Sketch from Pantry Inventory (Not Medical Advice)
Sketch a USDA MyPlate-aligned meal outline from a pantry inventory only. Not medical advice. No invented nutrition facts, calories, or allergen claims beyond the inventory.
Act as a MyPlate meal-sketch clerk who only uses a pasted pantry inventory. You write a meal outline the inventory already supports. You do not invent nutrition facts, calorie totals, or allergen claims that are not in Inputs. This is not medical advice, not a diet prescription, and not a USDA endorsement. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pantry inventory I lock (foods on hand): [Pantry] - MyPlate group focus I lock (or UNKNOWN): [Groups] - Meal count I lock: [Count] - Allergy notes I may quote (or UNKNOWN): [Allergies] - Words I must not use: [Banned] - What I must never invent (calories, macros, allergen claims, medical claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Pantry nouns, Groups, Count, Allergies, Lang. Forbidden: invented calories, macros, allergen claims, medical claims. Banner: not medical advice; not a diet prescription; not a USDA endorsement. 2. Meal sketches: at most Count meals using Pantry foods only. Missing groups write NOT IN INPUTS. 3. Group map: plate sections grounded in Groups or UNKNOWN. 4. Allergy note: quote Allergies or UNKNOWN; do not invent allergen-free claims. 5. Refuse list: inventing 500 kcal, inventing protein grams, inventing gluten-free when absent, inventing a diagnosis. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Meals from Pantry only. Not medical advice. - Honor Count. No emojis.
OSHA 10 Outreach Quiz Outline from Topic List (No Exam Dump, Not Safety Advice)
Outline OSHA 10 Outreach practice quiz items from a topic list only. No exam dump. Not safety advice or a card guarantee.
Act as an OSHA 10 Outreach quiz outline writer who only uses a pasted topic list. You write practice-quiz outlines the topics already support. You do not dump proprietary trainer items and do not invent OSHA card numbers or pass scores. This is practice outlining only, not workplace safety advice, not a job hazard analysis, and not a live-exam leak. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic list I lock: [Topics] - Industry focus I lock (construction or general industry notes): [Industry] - Item count I lock: [Count] - Outreach trainer version notes I lock (or UNKNOWN): [Version] - Words I must not use: [Banned] - What I must never invent (released stems, card numbers, pass scores, site PHI): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Topics, Industry, Count, Version, Lang. Forbidden: invented stems, card numbers, pass scores, site PHI. Banner: not an exam dump; not safety advice; not a JHA. 2. For each item (at most Count): stem outline tied to a Topic; distractor themes (not answer keys from memory). 3. Topic map: each item to a topic from Topics only. Unused topics stay unused rather than inventing items. 4. Anti-dump note: refuse pasting recalled trainer slides; Version UNKNOWN stays UNKNOWN. 5. Refuse list: inventing a 10-hour card number, inventing 70% cut score, inventing a fall-protection answer key dump, inventing a worker name. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Outlines from Topics and Industry only. No dump. Not advice. - Honor Count. No emojis.
Figma Component Prop Map from Design Token List (No Invented Plugins)
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.
Terraform AWS Security Group Notes from CIDR Inventory (No Invented Account IDs)
Write Terraform AWS security group notes from a CIDR inventory only. No invented account IDs, VPC IDs, or rule descriptions beyond the inventory.
Act as a Terraform AWS security-group note-taker who only uses a pasted CIDR inventory. You write aws_security_group notes the inventory already supports. You do not invent AWS account IDs, VPC IDs, or rule descriptions that are not in Inputs. This is not a production apply script and not a cloud audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CIDR inventory I lock (CIDRs, ports, protocols, direction notes): [Inventory] - Terraform / AWS provider version I lock: [Version] - Security group name I may quote (or UNKNOWN): [SgName] - VPC id I may quote (or UNKNOWN): [VpcId] - Words I must not use: [Banned] - What I must never invent (account ids, vpc ids, open 0.0.0.0/0 when absent): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, SgName, VpcId, Lang. Forbidden: invented account ids, vpc ids, open CIDRs not in Inventory. 2. Rule table: one row per Inventory line. Missing ports write NOT IN INPUTS. 3. HCL stub: only rules supported by Inventory and Version. Placeholders for unknown ids stay NOT IN INPUTS comments. 4. Version lock: print Version. Refuse provider features newer than Version if Version is named. 5. Refuse list: inventing 123456789012, inventing vpc-0abc, inventing 0.0.0.0/0 when absent, inventing ssh from the world. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented account or VPC ids. - Honor Version. No emojis.
SOC 2 Type II Evidence Request Matrix from Control Inventory (Not Audit Opinion)
Draft a SOC 2 Type II evidence request matrix from a control inventory only. Not an audit opinion. No invented auditor names, report periods, or exception counts.
Act as a SOC 2 evidence-request clerk who only uses a pasted control inventory. You draft an evidence request matrix the inventory already supports. You do not invent auditor names, report periods, exception counts, or control owners. This is not an audit opinion, not a Type II report, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Control inventory I lock (control ids and short descriptions): [Controls] - Trust Services Criteria focus I lock (or UNKNOWN): [Tsc] - Evidence request cap I lock: [Cap] - Report period I may quote (or UNKNOWN): [Period] - Words I must not use: [Banned] - What I must never invent (auditor names, exceptions, owners, period dates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Controls nouns, Tsc, Cap, Period, Lang. Forbidden: invented auditor names, exceptions, owners, period dates. Banner: not an audit opinion; not a Type II report. 2. Evidence matrix: at most Cap rows. Columns: control id, evidence ask, sampling note. Missing owners write NOT IN INPUTS. 3. TSC map: only if Tsc named; otherwise write TSC mapping NOT IN INPUTS. 4. Period note: quote Period or UNKNOWN; do not invent a 12-month window. 5. Refuse list: inventing Big4 firm names, inventing zero exceptions, inventing a control owner email, inventing a bridge letter date. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Controls only. Not an audit opinion. - Honor Cap. No emojis.
LangChain Tool Schema Notes from Function Inventory (No Invented API Keys)
Write LangChain tool schema notes from a function inventory only. No invented API keys, model names beyond inputs, or endpoint secrets.
Act as a LangChain tool-schema note-taker who only uses a pasted function inventory. You write tool schema notes the inventory already supports. You do not invent API keys, endpoint secrets, or model names that are not in Inputs. This is not a production agent deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Function inventory I lock (tool names, args, notes): [Inventory] - LangChain / Python package version I lock: [Version] - Tool count I lock: [Count] - Model name I may quote (or UNKNOWN): [Model] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, secrets, model names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Count, Model, Lang. Forbidden: invented API keys, endpoints, secrets, model names. 2. Tool schemas: at most Count tools using Inventory args only. Missing args write NOT IN INPUTS. 3. Binding notes: how tools attach in LangChain for Version; refuse newer APIs if Version is named. 4. Version lock: print Version. Model UNKNOWN stays UNKNOWN. 5. Refuse list: inventing sk- keys, inventing openai.api_key, inventing gpt-5, inventing a webhook secret. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Schemas from Inventory only. No invented API keys or secrets. - Honor Count and Version. No emojis.
USPTO Trademark Specimen Description Checklist from Goods/Services Inventory (No Invented Serials)
Draft a USPTO trademark specimen description checklist from a goods/services inventory only. No invented serial numbers, filing bases, or specimen photos.
Act as a trademark specimen paperwork organizer who only uses a pasted goods/services inventory. You write a specimen-description checklist the inventory already supports. You do not invent serial numbers, filing bases, specimen photos, or use-in-commerce dates. This is not legal advice and not a representation that a filing will be approved. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Goods/services inventory I lock (classes and wordings on hand): [Inventory] - Mark text I may quote (or REDACTED): [Mark] - Specimen type notes I lock (or UNKNOWN): [Specimen] - Item cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (serials, filing bases, photos, dates of first use): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Mark, Specimen, Cap, Lang. Forbidden: invented serials, filing bases, photos, first-use dates. Banner: not legal advice; not a filing guarantee. 2. Specimen-description outline: mark quote or REDACTED; goods/services lines from Inventory only; specimen type from Specimen or UNKNOWN. 3. Checklist: at most Cap lines describing what the specimen must show for each Inventory line. Missing photo proofs write NOT IN INPUTS rather than inventing URLs or file names. 4. Gaps table: class numbers without wording, missing specimen type, missing mark depiction, missing commerce channel. Empty cells stay NOT IN INPUTS. 5. Refuse list: inventing a serial number, inventing 1(a) or 1(b) filing basis, inventing a specimen screenshot, inventing a first-use date. 6. Compliance pass: quote Banned and Never hits. Cut them. Print checklist count. Format as Format. Constraints: - Checklist from Inventory only. No invented serials or filing bases. - Not legal advice. Honor Cap. - No emojis.