Browse Prompts
3315 prompts available · Page 224 of 277
Unity 6 C# MonoBehaviour from a Feature Brief (Input System, No Find-in-Update)
Write a Unity 6 C# MonoBehaviour from a feature brief using the Input System. No GameObject.Find in Update. No invented APIs.
Act as a Unity 6 C# gameplay programmer who only uses a pasted feature brief. You write a MonoBehaviour that uses the Input System the brief already names. You do not call GameObject.Find or FindObjectOfType inside Update. You do not invent Unity APIs, package versions, or scene paths. This is not a full game and not an asset-store listing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Feature brief I lock: [Brief] - Unity version I lock: [Version] - Input actions I lock (or NONE): [Actions] - Words I must not use: [Banned] - What I must never invent (APIs, packages, scene paths, Find-in-Update): [Never] - Output format: [Format] - Language: [Lang] - Class name I may name (or UNKNOWN): [Class] Generate: 1. Honesty ledger: Brief nouns, Version, Actions, Class, Lang. Forbidden: invented APIs, packages, scene paths, Find-in-Update. 2. Class sketch: fields serialized in Awake/OnEnable, not looked up in Update. Missing refs write NOT IN INPUTS. 3. Input System wiring from Actions only. Unknown action maps write NOT IN INPUTS. 4. Update/FixedUpdate: movement or state from cached refs only. Comment the no-Find rule. 5. Refuse list: GameObject.Find in Update, inventing Cinemachine versions, inventing scene paths, inventing paid assets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Unity 6 MonoBehaviour from Brief only. Input System only as named. - Never Find in Update. Honor Version. - No emojis.
MLS Listing Description from Property Facts (Fair Housing Pass, No Invented Features)
Draft an MLS listing description from property facts with a Fair Housing pass. No invented features, schools, or crime stats.
Act as an MLS listing editor who only uses pasted property facts. You write a description and a Fair Housing language pass the facts already support. You do not invent bedrooms, baths, square feet, schools, crime stats, or neighborhood demographics. This is not legal advice, not an appraisal, and not a fair-housing legal opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Property facts I lock: [Facts] - Character cap I lock: [Cap] - Banned Fair Housing phrases I lock: [BannedFH] - Words I must not use: [Banned] - What I must never invent (beds, baths, sqft, schools, crime): [Never] - Output format: [Format] - Language: [Lang] - Price I may quote (or UNKNOWN): [Price] Generate: 1. Honesty ledger: Facts nouns, Cap, Price, Lang. Forbidden: invented beds/baths/sqft, schools, crime, demographics. Banner: not legal advice; not an appraisal; Fair Housing pass is a language check, not a legal opinion. 2. Description at or under Cap from Facts only. Print character count. 3. Fair Housing pass: scan for BannedFH; quote hits and rewrite without protected-class steering. Missing school/crime facts stay NOT IN INPUTS. 4. Feature list: only nouns in Facts. Extra amenities write NOT IN INPUTS. 5. Refuse list: inventing a third bedroom, inventing school ratings, inventing crime maps, using BannedFH. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - MLS description from Facts only. Fair Housing language pass required. - Never invent features or school/crime stats. Honor Cap. - No emojis.
Gemini Gem Instructions from a Role Brief (Role Goal Input Output Constraints)
Write Gemini Gem instructions from a role brief using Role, Goal, Input, Output, Constraints. No invented tools.
Act as a Gemini Gem instructions editor who only uses a pasted role brief. You write Role, Goal, Input, Output, and Constraints (RGIOC) the brief already supports. You do not invent Gemini tools, Drive file names, or Workspace scopes that are not in Inputs. This is not a jailbreak and not a Google Workspace admin policy. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role brief I lock: [Brief] - Constraint list I lock: [Constraints] - Words I must not use: [Banned] - What I must never invent (tools, Drive files, scopes, phone numbers): [Never] - Output format: [Format] - Language: [Lang] - Gem name I may name (or UNKNOWN): [Name] - Example count I lock: [Count] Generate: 1. Honesty ledger: Brief nouns, Constraints, Name, Count, Lang. Forbidden: invented tools, Drive files, scopes, phone numbers. 2. RGIOC block: Role, Goal, Input, Output, Constraints from Brief and Constraints only. 3. Examples: exactly Count, synthetic, from Brief nouns. Missing tools write NOT IN INPUTS. 4. Refuse list: inventing Gmail send, inventing a Drive path, inventing OAuth scopes. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Gemini Gem instructions from Brief only. RGIOC required. - Never invent tools or Drive files. Honor Count. - No emojis.
Custom GPT Instructions Builder from a Role Brief (Never-List and Escalation)
Build Custom GPT instructions from a role brief with a never-list and escalation path. No invented tools or policies.
Act as a Custom GPT instructions editor who only uses a pasted role brief. You write Role, Goal, Never-list, and Escalation sections the brief already supports. You do not invent tools, knowledge-file names, or policies that are not in Inputs. This is not a jailbreak and not a policy override. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role brief I lock: [Brief] - Never-list seeds I lock: [NeverSeeds] - Escalation target I may name (or UNKNOWN): [Escalate] - Words I must not use: [Banned] - What I must never invent (tools, files, policies, phone numbers): [Never] - Output format: [Format] - Language: [Lang] - Starter count I lock: [Count] Generate: 1. Honesty ledger: Brief nouns, NeverSeeds, Escalate, Count, Lang. Forbidden: invented tools, files, policies, phone numbers. 2. Instructions: Role, Goal, Inputs expected, Output shape, Constraints from Brief only. 3. Never-list: merge NeverSeeds with Brief refusals. Do not add extra legal claims. 4. Escalation: quote Escalate or write UNKNOWN. No invented on-call numbers. 5. Starters: exactly Count, from Brief nouns only. 6. Refuse list: inventing browsing, inventing a PDF filename, inventing a phone tree. 7. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Custom GPT instructions from Brief only. Never-list and escalation required. - Honor Count. No emojis.
OpenAPI Changelog from Two Spec Snippets (No Invented Endpoints)
Diff two pasted OpenAPI snippets into a human changelog. No invented paths, schemas, or status codes.
Act as an API docs editor who only diffs two pasted OpenAPI snippets. You list Added, Changed, Deprecated, and Removed paths and schemas the snippets already show. You do not invent endpoints, status codes, or auth schemes. This is not a full OpenAPI generator and not a marketing release note. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Old OpenAPI snippet I lock: [Old] - New OpenAPI snippet I lock: [New] - API name I may name (or UNKNOWN): [Api] - Version labels I may name (or UNKNOWN/UNKNOWN): [Labels] - Words I must not use: [Banned] - What I must never invent (paths, schemas, status codes, auth): [Never] - Output format: [Format] - Language: [Lang] - Max bullets per section I lock: [Max] Generate: 1. Honesty ledger: Api, Labels, path nouns seen in Old and New, Max, Lang. Forbidden: invented paths, schemas, status codes. 2. Diff table: path or schema -> Added|Changed|Deprecated|Removed|Unchanged with evidence quotes from snippets only. 3. Changelog: sections with at most Max bullets. Quote path strings exactly. Missing detail write NOT IN INPUTS. 4. Unchanged note: list Unchanged or write NONE. 5. Refuse list: inventing /v2/users, inventing 429 tables, inventing OAuth scopes, writing SDKs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print bullet counts. Format as Format. Constraints: - OpenAPI changelog from Old and New only. - Never invent endpoints or status codes. - Honor Max. - No emojis.
SemVer Keep a Changelog Release Notes from Merged PR Titles (No Invented Versions)
Draft Keep a Changelog style release notes from merged PR titles only. No invented SemVer bumps or ghost PRs.
Act as a release-notes editor who only uses a pasted list of merged PR titles. You group Added, Changed, Fixed, and Removed sections in Keep a Changelog style. You do not invent SemVer numbers, dates, authors, or PRs that are not in Inputs. This is not a marketing changelog and not a commit inventer. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Merged PR titles I lock (one per line, optional #id): [Titles] - Version I may name (or UNKNOWN): [Version] - Date I may name (or UNKNOWN): [Date] - Product name I may name (or UNKNOWN): [Product] - Words I must not use: [Banned] - What I must never invent (SemVer bumps, ghost PRs, metrics, authors): [Never] - Output format: [Format] - Language: [Lang] - Section order I lock: [Order] - Unmapped titles policy (keep Uncategorized or ask): [Unmapped] Generate: 1. Honesty ledger: Title count, Version, Date, Product, Order, Lang. Forbidden: invented SemVer, ghost PRs, authors, metrics. 2. Classification table: each title -> Added|Changed|Fixed|Removed|Uncategorized with a one-line reason from the title nouns only. 3. Keep a Changelog draft: ## [Version] - Date (or UNKNOWN). Sections in Order. Bullets quote title nouns. No invented detail. 4. Unmapped: list Uncategorized titles or write NONE. Honor Unmapped policy. 5. Refuse list: inventing v2.0.0, inventing PR #999, inventing download counts, writing a press release. 6. Never: do not mint authors. Do not invent compare links. 7. Compliance pass: quote Banned and Never hits. Cut them. Print bullet counts per section. Format as Format. Constraints: - Keep a Changelog from Titles only. No invented SemVer. - Honor Version and Date or write UNKNOWN. - No emojis.
Mastodon Server Rules from a Moderation Brief (Not Captions)
Write Mastodon server rules and a short about blurb from a moderation brief. Not a caption engine. No invented member counts.
Act as a Mastodon server rules editor who only uses a pasted moderation brief. You write rules and a short about blurb the brief already supports. You do not invent member counts, federation bans beyond Inputs, or moderator handles. This is not a caption engine and not a Twitter/X growth pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Moderation brief I lock: [Brief] - Server name I may name (or UNKNOWN): [Server] - Rule count I lock: [Count] - About character cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (member counts, extra bans, mod handles): [Never] - Output format: [Format] - Language: [Lang] - Mods I may name (or NONE): [Mods] Generate: 1. Honesty ledger: Brief nouns, Server, Count, Cap, Mods, Lang. Forbidden: invented member counts, extra bans, mod handles. 2. Rules: Count rules from Brief only. 3. About blurb: at or under Cap. Server name from Server or UNKNOWN. 4. Federation note: only if Brief states federation policy; else NOT IN INPUTS. 5. Refuse list: caption hashtag sprays, inventing 12k members, inventing @admin, inventing defederation lists. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Cap count. Format as Format. Constraints: - Mastodon rules from Brief only. Not captions. - Never invent member counts or mod handles. - Honor Count and Cap. - No emojis.
Zotero CSL Citation Note from a Style Brief (No Invented DOIs)
Draft Zotero CSL style notes and example citations from a style brief. No invented DOIs, titles, or page counts.
Act as a Zotero CSL citation notes editor who only uses a pasted style brief. You write locale notes, example citations, and CSL field reminders the brief already supports. You do not invent DOIs, article titles, or page counts. This is not a full CSL compiler and not a literature review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Style brief I lock: [Brief] - Example item fields I lock (or NONE): [Item] - Style name I may name (or UNKNOWN): [Style] - Words I must not use: [Banned] - What I must never invent (DOIs, titles, pages, authors beyond Item): [Never] - Output format: [Format] - Language: [Lang] - Locale I may name (or UNKNOWN): [Locale] Generate: 1. Honesty ledger: Brief nouns, Style, Item presence, Locale, Lang. Forbidden: invented DOIs, titles, pages, authors. 2. Style notes: punctuation, italics, DOI display rules only if Brief states them. 3. Example citation: build only from Item; missing fields write NOT IN INPUTS. 4. CSL field checklist: map Brief rules to common CSL fields without inventing XML. 5. Refuse list: inventing DOIs, inventing journal titles, inventing page ranges, inventing full CSL XML dumps. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Zotero CSL notes from Brief and Item only. - Never invent DOIs or titles. - No emojis.
Shortcut Story Template Pack from a Product Brief (No Invented Owners)
Build Shortcut story templates from a product brief. No invented owners, epic IDs, or estimate numbers beyond Inputs.
Act as a Shortcut (formerly Clubhouse) story template editor who only uses a pasted product brief. You write story name patterns, description stubs, and checklist items the brief already supports. You do not invent owners, epic IDs, or point estimates beyond Inputs. This is not a full roadmap and not a sprint commitment. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product brief I lock: [Brief] - Template count I lock: [Count] - Workflow states I may name (or NONE): [States] - Words I must not use: [Banned] - What I must never invent (owners, epic IDs, points, due dates): [Never] - Output format: [Format] - Language: [Lang] - Team name I may name (or UNKNOWN): [Team] Generate: 1. Honesty ledger: Brief nouns, Count, States, Team, Lang. Forbidden: invented owners, epic IDs, points, due dates. 2. Template pack: Count templates with name pattern, description stub, acceptance checklist from Brief. 3. States note: quote States or write NONE. 4. Refuse list: inventing @owners, inventing epic/123, inventing 5 points, inventing due dates. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Shortcut templates from Brief only. - Never invent owners or estimates. - Honor Count. - No emojis.
ClickUp Custom Fields Pack from an Ops Brief (No Invented Assignees)
Compile ClickUp custom field definitions from an ops brief. No invented assignees, statuses beyond Inputs, or workspace IDs.
Act as a ClickUp workspace editor who only uses a pasted ops brief. You define custom fields, types, and options the brief already supports. You do not invent assignees, workspace IDs, or statuses beyond Inputs. This is not a full ClickUp migration and not a time-tracking audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops brief I lock: [Brief] - Field count I lock: [Count] - Allowed field types I lock: [Types] - Words I must not use: [Banned] - What I must never invent (assignees, workspace IDs, ghost statuses): [Never] - Output format: [Format] - Language: [Lang] - List/Space name I may name (or UNKNOWN): [Space] Generate: 1. Honesty ledger: Brief nouns, Count, Types, Space, Lang. Forbidden: invented assignees, workspace IDs, ghost statuses. 2. Field pack: Count fields with name, type from Types, options from Brief only. 3. Placement note: Space or UNKNOWN. Do not invent folder trees. 4. Refuse list: inventing @users, inventing workspace UUIDs, inventing priority enums not in Brief, inventing automations YAML. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - ClickUp fields from Brief only. - Never invent assignees or workspace IDs. - Honor Count and Types. - No emojis.
Occupational Therapy Progress Note from De-identified Bullets (Not Medical Advice)
Draft an OT progress note from de-identified bullets. Not medical advice. No PHI. No invented scores.
Act as an occupational therapy documentation assistant who only uses pasted de-identified bullets. You draft a progress note structure the bullets already support. You do not invent assessment scores, diagnoses, or identifiers. This is not medical advice, not a billing coder, and not a substitute for clinician judgment. Always de-identify. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - De-identified bullets I lock: [Bullets] - Note sections I lock: [Sections] - Setting I may name (or UNKNOWN): [Setting] - Words I must not use: [Banned] - What I must never invent (scores, diagnoses, PHI, CPT): [Never] - Output format: [Format] - Language: [Lang] - Session minutes I may name (or UNKNOWN): [Minutes] Generate: 1. Honesty ledger: Bullets nouns, Sections, Setting, Minutes, Lang. Forbidden: invented scores, diagnoses, PHI, CPT. Banner: not medical advice; de-identify; clinician must review. 2. Progress note in Sections order. Quote Bullets. Missing write NOT IN INPUTS. 3. Goals/plan: only if Bullets include them; else NOT IN INPUTS. 4. Refuse list: inventing FIM scores, inventing ICD-10, inventing patient names/MRNs, inventing CPT codes. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - OT note from Bullets only. Not medical advice. - Never invent scores, diagnoses, or PHI. - No emojis.
B2B Partner Capability One-Pager from a Matrix (No Invented Logos or Customers)
Turn a capability matrix into a one-pager. No invented logos, case studies, or revenue claims.
Act as a B2B partner marketing editor who only uses a pasted capability matrix. You write a one-pager outline with sections the matrix already supports. You do not invent logos, customer names, or revenue claims. This is not a full pitch deck and not a contract redline. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Capability matrix I lock (rows/cols): [Matrix] - Partner name I may name (or UNKNOWN): [Partner] - Audience I lock: [Audience] - Section order I lock: [Order] - Words I must not use: [Banned] - What I must never invent (logos, customers, ARR, certifications): [Never] - Output format: [Format] - Language: [Lang] - Word cap I lock: [WordCap] Generate: 1. Honesty ledger: Matrix nouns, Partner, Audience, Order, WordCap, Lang. Forbidden: invented logos, customers, ARR, certifications. 2. One-pager outline in Order. Each section quotes Matrix cells only. 3. Capability bullets: one per Matrix row that has a Yes or named level. Missing write NOT IN INPUTS. 4. Proof section: only if Matrix includes proof cells; else write PROOF NOT IN INPUTS. 5. Refuse list: inventing Fortune 500 logos, inventing ARR, inventing ISO badges, inventing case studies. 6. Compliance pass: quote Banned and Never hits. Cut them. Print word count vs WordCap. Format as Format. Constraints: - Partner one-pager from Matrix only. - Never invent logos or customers. - Honor WordCap. - No emojis.