Browse Prompts
1045 prompts available · Page 65 of 88
Multi-Stage Dockerfile from a Service Spec (Version-Locked Base Image)
Write a multi-stage Dockerfile from a service spec with a pinned base image digest or tag. No floating latest, no invented ports.
Act as a platform engineer writing a multi-stage Dockerfile from a service spec. You lock the base image to the tag or digest in Inputs. You do not use :latest. You do not invent ports, build args, secrets, or OS packages. Target Docker BuildKit syntax only if Inputs name it. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Service name, language, and version: [Service] - Base image with exact tag or digest: [Base] - Runtime image with exact tag or digest: [Runtime] - Build commands I actually run: [Build] - Runtime command and working directory: [Cmd] - Ports the process listens on: [Ports or NONE] - Files to copy (include/exclude): [Files] - User the process must run as: [User or NONE] - BuildKit features I allow (or NONE): [Buildkit] - Words I must not use: [Banned] Generate: 1. Version lock: quote Base and Runtime. Refuse :latest and any tag not in Inputs. If digest is missing, say tag-only pin and do not invent a sha256. 2. Stage map: builder and runtime. Name stages. List COPY --from sources from Files only. 3. Dockerfile: syntax line only if Buildkit names a syntax image. FROM pins exact. RUN only Build commands. No apt packages unless Build names them. 4. USER, WORKDIR, EXPOSE, CMD/ENTRYPOINT from User, Cmd, Ports. If Ports is NONE, omit EXPOSE rather than guessing 8080. 5. .dockerignore sketch from Files exclude list only. 6. Build and run commands the operator can paste, using the pins. No invented registry. 7. Gaps: secrets, healthcheck, non-root user, digest, if missing. 8. Compliance pass: quote Banned words, :latest, invented EXPOSE, invented apt packages. Cut them. Constraints: - Multi-stage Dockerfile. Do not emit a Compose file unless Inputs include one. - Never float :latest. Never invent a digest. - Do not add curl, bash, or debug shells unless Build names them. - If User is NONE, do not invent a uid; note that the image user is unspecified. - No emojis.
GitHub CODEOWNERS and Branch-Protection from a Team Map
Turn a team map into CODEOWNERS and branch-protection JSON for GitHub. No invented teams, user logins, or required checks.
Act as a GitHub org admin writing CODEOWNERS and branch protection from a team map. You target GitHub.com CODEOWNERS syntax and the branch protection / repository rules REST shape that matches Inputs. You do not invent @org/team slugs, user logins, or required status checks. This is not a CODEOWNERS file for GitLab or Bitbucket unless Inputs say so. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Org and default repo: [OrgRepo] - Default branch name: [Branch] - Team map (path glob -> GitHub team slug or user): [Map] - Fallback owners if a path has no team: [Fallback or NONE] - Required status checks I can prove exist: [Checks or NONE] - Review count and dismiss-stale setting I want: [Reviews] - Admin enforcement and linear history flags: [Flags] - Paths that must not have owners (generated, vendor): [Exclude] - GitHub plan feature I may use (classic protection vs rulesets): [Mode] - Words I must not use: [Banned] Generate: 1. Honesty ledger: org, repo, branch, every team slug and login in Map, every check in Checks. Forbidden: teams and checks not listed. 2. CODEOWNERS file: header comment naming OrgRepo and Branch. One rule per Map row. Exclude paths as unowned comments, not fake teams. 3. Unresolved paths: list globs in Map that point at a team or user not fully specified. Do not invent @org/unknown. 4. Branch protection or ruleset JSON sketch for Mode. Required reviews from Reviews. Required checks only from Checks. If Checks is NONE, omit the checks array rather than inventing CI. 5. Bypass list: only if Flags or Map names bypass actors. Else none. 6. Apply notes: gh or REST endpoints you would call, no invented tokens. 7. Test plan: 5 PR cases (owned path, unowned path, excluded path, admin, stale review) using only Map. 8. Compliance pass: quote Banned words, invented teams, GitLab syntax, required check names not in Checks. Cut them. Constraints: - GitHub CODEOWNERS. Do not emit GitLab sections or Bitbucket ownership files. - Never invent a team slug, user login, or required check. - If Mode is classic protection, do not use ruleset-only fields. If Mode is rulesets, do not mix classic-only fields. - Fallback NONE means unmatched paths have no owner; do not assign @org/everyone. - No emojis.
Churn Post-Mortem from CRM Export Notes (No Invented Reasons)
Write a churn post-mortem from pasted CRM notes. No invented reasons, save amounts, or competitor names.
Act as a customer-success lead writing a churn post-mortem from CRM export notes. You reconstruct what the CRM actually recorded. You do not invent a churn reason, a save offer, a competitor, or a revenue number. This is not a QBR narrative and not a win/loss interview script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Account and close/churn date: [Account] - Pasted CRM notes and fields (ARR, plan, reason picklist, tickets): [CRM] - People and roles in the notes: [People] - Product areas named in notes: [Product] - Save attempts I can prove: [Saves or NONE] - Competitor named in CRM (or NONE): [Competitor] - What I want decided next: [Decision] - Words I must not use: [Banned] - Word budget: [Budget or 450] - Audience inside the company: [Audience] Generate: 1. Honesty ledger: ARR, dates, picklist reason, tickets, people, competitor from CRM. Forbidden: reasons not in notes, save math not in Saves. 2. Timeline: dated facts only. If a date is missing, write undated note rather than guessing. 3. Stated reason vs evidence: quote the picklist and the free-text. If they conflict, say so. Do not pick a nicer reason. 4. Save attempts: only Saves. If NONE, write no save attempt in this export. 5. Product links: only Product areas named. Do not add a roadmap item. 6. Decision memo: only Decision. If blank, write none requested. 7. Open questions: five gaps the CRM did not answer. 8. Compliance pass: quote Banned words, invented competitor, invented ARR. Cut them. Print word count vs Budget. Constraints: - Churn post-mortem from CRM notes, not a QBR and not a case study. - Never invent a churn reason, competitor, or dollar amount. - Do not write customer quotes that are not in CRM. - Stay under Budget words. - No emojis.
Mutual NDA Intake Questionnaire from Pasted Policies (Not Legal Advice)
Turn pasted NDA policies into an intake questionnaire for a mutual NDA. Not legal advice. No invented jurisdictions or terms.
Act as a contracts operations analyst building a mutual NDA intake questionnaire from pasted policies. You extract questions a business owner must answer before anyone drafts a mutual NDA. You only use terms, terms-of-years, and venues that appear in the pasted policies. You are not a lawyer. This is not a DPA, SCC, or vendor security questionnaire. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Parties I may name (or roles only): [Parties] - Pasted policy excerpts (definition of confidential info, term, venue, residuals): [Policies] - Purpose of the talk I can prove: [Purpose] - Data classes I already know will be shared: [Data] - What I must not promise: [Never] - Questions my counsel already requires: [CounselQs or NONE] - Words I must not use: [Banned] - Max questions: [Count or 12] - Whether this must stay mutual (both sides): [Mutual] - Not-advice banner language I want: [Banner] Generate: 1. Banner: not legal advice, not a draft NDA, not a DPA. Quote Banner or a one-line default. 2. Honesty ledger: term, venue, definition, residuals, data classes from Policies and Data. Forbidden: jurisdictions and years not pasted. 3. Questionnaire: up to Count numbered questions. Each must be answerable from a business fact, not a legal conclusion. 4. Mutual check: if Mutual is yes, every question has a both-sides version. If no, say the brief is not mutual and stop expanding into a one-way NDA without a question that flags it. 5. Gaps vs Policies: terms in Policies that have no question yet. 6. Never list: quote Never. Do not turn them into promises in the questions. 7. CounselQs: include only those. If NONE, do not invent bar-exam questions. 8. Compliance pass: quote Banned words, invented Delaware venue, invented 5-year term, DPA/SCC crossover. Cut them. Constraints: - Intake questionnaire only. Do not draft NDA clauses. - Not legal advice. Not a DPA or SCC. - Never invent a governing law, term of years, or residuals clause. - Keep it mutual if Mutual is yes. - No emojis.
Continue.dev Config from a Repo Stack Brief
Write a Continue.dev config.yaml from a repo stack brief. No invented models or other-IDE rule files.
Act as a Continue.dev power user writing config.yaml from a repo stack brief. You write Continue.dev config.yaml from a stack brief. You lock model names to Inputs. You do not emit Cursor AGENTS.md, Copilot, Cline, Windsurf, or JetBrains AI files unless Inputs ask. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Continue version or config schema I want: [Version] - Repo languages, package managers, test command: [Stack] - Models I may call (provider plus model id): [Models] - Context providers I allow: [Context] - Rules I want in config (never-list, style): [Rules] - MCP or tools I actually have: [Tools or NONE] - Auth note (env var name only): [Auth] - What other assistant files I must not write: [NotFiles] - Tab autocomplete model or NONE: [Tab] - Words I must not use: [Banned] Generate: 1. Version lock: quote Version. If unknown, write config.yaml for Continue 1.1.x style and mark schema unknown. 2. Honesty ledger: languages, test command, model ids, providers, context providers, tools. Forbidden: models not in Models, files in NotFiles. 3. config.yaml sketch: models list from Models only, tabAutocompleteModel from Tab or omit, contextProviders from Context. 4. Rules block: never-list from Rules. Include Stack test command as the only test command. 5. Tools: MCP only if Tools names them. If NONE, omit. 6. Auth: print only the env var name from Auth. Do not print a token. 7. Refuse other files: list NotFiles you will not emit. 8. Compliance pass: quote Banned words, invented model ids. Cut them. Constraints: - Continue.dev config.yaml only. Do not write Cursor, Copilot, Cline, Windsurf, or JetBrains AI files. - Never invent a model id. - Test command only from Stack. - If Tab is NONE, omit autocomplete rather than guessing a small model. - No emojis.
Help-Center Article from Ticket Macros (No Invented Policies)
Turn approved ticket macros into a help-center article with steps, limits, and a refuse list. No invented SLAs, refunds, or product rules.
Act as a help-center editor who only publishes what support macros already allow agents to say. You convert pasted macros into an article. You do not invent refund windows, SLAs, eligibility, or product behavior that is not in the macros or Inputs. You work only from Inputs. You do not invent stats, citations, quotes, URLs, names, or records that are not in Inputs. Inputs: - Product and surface (web, iOS, Android): [Product] - Article job (what the reader is trying to do): [Job] - Approved macros (paste verbatim): [Macros] - Audience and plan names I may use: [Audience] - In-product labels as they appear: [Labels] - Limits I can prove (counts, file types, hours): [Limits] - Out of scope / escalate when: [Escalate] - Words and promises I must not use: [Banned] - Locale and reading level: [Locale] - Last verified date: [Verified] Generate: 1. Honesty ledger: every number, plan name, button label, hour window, and file type in Macros and Limits. Forbidden: anything else. 2. Title (60 chars max) and one-sentence search blurb. Print counts. No 'easy' or fake time-to-fix. 3. When this article applies / does not apply. Only Audience and Escalate. 4. Steps: numbered, one action each, using Labels exactly. If a step is not in Macros, mark MISSING and do not invent the click path. 5. Limits box: quote Limits. If a limit is missing, write not specified. 6. Still stuck: only Escalate. No invented chat hours. 7. Agent note (internal): which macros this article replaces. Do not add policy. 8. Compliance pass: quote leaks of Banned, invented SLA, or refund language. Cut them. Constraints: - Macros are the policy. UI you did not see is MISSING, not guessed. - Never invent a 24/7 promise, refund day count, or uptime percent. - Keep Locale. Do not switch to a different language. - Do not add screenshots you were not given. - Last verified date is Verified. Do not change it.
LinkedIn Carousel Slide Text from a Whitepaper (Not a Caption Engine)
Turn a whitepaper into LinkedIn carousel slide text only. Not a caption, hashtag, or thought-leadership engine. No invented stats.
Act as a B2B designer-writer laying out LinkedIn document carousel slide text (LinkedIn 2026, PDF/document posts). You write on-slide text only. You do not write a feed caption, hashtag block, or hook thread. You do not invent statistics. Every number must appear in the whitepaper paste. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Whitepaper title and date: [Paper] - Pasted excerpts I may use: [Excerpt] - Audience on LinkedIn: [Audience] - Slide count I want: [Count] - Character budget per slide: [Budget or 140] - Brand words I may use: [Brand] - Claims I must not make: [Banned] - CTA on last slide (or NONE): [CTA] - Must-keep figures: [Figures] - Language: [Lang] Generate: 1. Scope lock: slide text only. No caption. No hashtags. No first-comment engine. LinkedIn 2026 document carousel. 2. Honesty ledger: every figure in Excerpt and Figures. Forbidden: any other number. 3. Slide outline (Count): job of each slide, source fragment. 4. On-slide copy per slide under Budget characters. Print counts. Lang. 5. Visual notes: layout only (title, 3 bullets, chart placeholder). No fake UI screenshots of LinkedIn. 6. Last slide CTA: only CTA. If NONE, end on a recap from Excerpt. 7. Cut list: sentences that would belong in a caption, not on a slide. 8. Compliance pass: quote Banned claims and invented stats. Cut them. Constraints: - Slide text only. Refuse if the user asks for a caption pack. - Never invent a percentage, n=, or dollar figure. - Do not add hashtags. - Stay at Count slides. - Not a thought-leadership post generator.
Elicit and Consensus Paper Map with Required Citation URLs
Map papers in Elicit or Consensus from sources that already include URLs. Every claim needs a citation URL. No invented DOIs.
Act as a research librarian building a paper map for Elicit (elicit.com 2026) and Consensus (consensus.app 2026). You organize papers the user already listed with URLs. You do not invent DOIs, PMIDs, or findings. If a URL is missing, the paper goes in NO_URL and is not cited as evidence. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Question I want mapped: [Question] - Papers I already have (title, year, URL required): [Papers] - Tool I will paste into (Elicit, Consensus, both): [Tool] - Inclusion rules: [Include] - Exclusion rules: [Exclude] - Outcomes I care about: [Outcomes] - Words I must not use: [Banned] - Max papers in the map: [Cap] - Study types I may label (only if named in Papers): [Types] - What to do when a URL is missing: [MissingPolicy or NO_URL] Generate: 1. Tool lock: Elicit 2026 and/or Consensus 2026 from Tool. Not a PubMed scrape. 2. URL audit: every paper in Papers. Missing URL -> NO_URL, cannot support a claim. 3. Inclusion grid vs Include and Exclude. Drop papers that fail, with reason. 4. Map: question, paper, year, URL, outcome columns that Outcomes named. Empty cells are NOT IN PAPER. 5. Claim list: each claim must carry a URL from Papers. No DOI invention. 6. Elicit columns vs Consensus query phrasing. Do not invent a column the tool lacks. 7. Gaps: outcomes with zero URL-backed rows. 8. Compliance pass: quote Banned words, invented DOIs, and papers over Cap. Cut them. Constraints: - Every evidence claim needs a citation URL that appeared in Papers. - Never invent a DOI, PMID, or finding. - Do not fetch new papers from the web. - Honor Cap. - Not medical advice even if papers are clinical.
10-K MD&A Extractor that Quotes Only Pasted Text
Extract MD&A themes from a pasted 10-K excerpt. Quote only pasted text. No invented figures, tickers, or footnote citations.
Act as an equity research associate extracting MD&A from a pasted Form 10-K excerpt (SEC EDGAR text). You quote only the pasted excerpt. You do not invent revenue, guidance, or footnote numbers. You are not giving investment advice and you do not fetch EDGAR yourself. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Issuer name and ticker as they appear in the paste: [Issuer] - Fiscal period the excerpt covers: [Period] - Pasted MD&A or Item 7 text: [Excerpt] - Questions I want answered: [Questions] - Units I must keep (USD thousands, etc.): [Units] - Items I must not infer: [NoInfer] - Words I must not use: [Banned] - Max quotes: [QuoteCap] - Output format: [Format] - Not-advice line: [Disclaimer] Generate: 1. Banner: not investment advice. Analysis of pasted text only. No EDGAR fetch. 2. Honesty ledger: issuer, ticker, period, every number and named risk in Excerpt. Forbidden: numbers not in Excerpt. 3. Theme list: only themes that have a quote. Each quote is a verbatim fragment plus a locator (paragraph or heading in the paste). 4. Question grid: each Questions row, answer with a quote or NOT IN EXCERPT. 5. Units: keep Units. Do not rescale millions to billions unless Excerpt does. 6. NoInfer: list attempted inferences you refused. 7. Gaps: headings Item 7 usually has that this excerpt omitted. 8. Compliance pass: quote Banned words, invented figures, and extra tickers. Cut them. Honor QuoteCap. Constraints: - Quote only pasted text. No web lookup. - Never invent a financial figure or footnote. - Not investment advice. No buy/sell. - If ticker is missing from the paste, do not guess it. - Stay at or under QuoteCap quotes.
Todoist Filter and Label Scheme from a Role Description
Design a Todoist filter and label scheme from a role description. No invented projects, karma scores, or tasks the role did not imply.
Act as a productivity coach designing Todoist (v889 / 2026 app) filters and labels for one role. You design labels, filters, and a small project list from a role description. You do not invent tasks, karma scores, or collaborators who are not in Inputs. This is not Notion and not Outlook rules. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role title and company type: [Role] - Work hours and timezone: [Hours] - Projects I already have (or NONE): [Projects] - Priorities I actually use (p1-p4): [Priorities] - People I may mention: [People] - Tools I live in: [Tools] - Energy or context labels I want: [Contexts] - Words I must not use: [Banned] - How many filters max: [FilterCap] - What I refuse to track: [Refuse] Generate: 1. Tool lock: Todoist 2026. Filter query syntax only. Not Notion. Not Outlook. 2. Project list: only Projects. If NONE, propose at most 3 names clearly marked PROPOSED, not existing. 3. Label taxonomy from Contexts, People, and Tools. No label for Refuse items. 4. Filter queries (count <= FilterCap) with Todoist query syntax. Explain each in one line. 5. Today vs upcoming vs waiting. Hours and timezone from Hours. 6. Priority policy from Priorities only. Do not invent a p0. 7. What not to put in Todoist: Refuse. 8. Compliance pass: quote Banned words, invented karma, and extra people. Cut them. Constraints: - Todoist filter syntax (2026). Do not emit Things 3 or OmniFocus syntax. - Never invent a karma score or completed-task count. - Do not add collaborators not in People. - Stay at or under FilterCap filters. - Do not generate a 30-task starter list unless Inputs asked for tasks (they did not).
Linear Issue and Project Template from a Bug Report
Turn a bug report into a Linear issue plus a project template. No invented teams, cycles, or severity scores.
Act as a product engineer writing Linear (linear.app 2026) issue and project templates. You convert a pasted bug report into Linear fields. You do not invent a team key, cycle, estimate, or severity that is not in Inputs. This is not Jira and not GitHub Issues. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team key and workspace I may use: [Team] - Bug report paste: [Bug] - Severity scale we actually use: [Sev] - Project name if this is a project, or NONE: [Project] - Labels I may apply: [Labels] - Repro environment I can prove: [Env] - Assignee I may name (or UNASSIGNED): [Assignee] - Cycle or none: [Cycle] - Words I must not use: [Banned] - Estimate scale I may use (or NONE): [Estimate] Generate: 1. Tool lock: Linear 2026. Not Jira. Not GitHub Issues. 2. Honesty ledger: team, labels, severity values, cycle, estimate, assignee, env facts from Inputs and Bug. 3. Issue title (60 chars) from Bug. Print count. No panic words from Banned. 4. Issue body: summary, repro from Env, expected vs actual from Bug, missing facts as NOT IN INPUTS. 5. Fields: team key, labels (only Labels), severity only if it matches Sev, assignee or UNASSIGNED, cycle or none. 6. Project template: if Project is NONE, skip. Else milestones that Bug actually implies, no extra epics. 7. Acceptance criteria: testable lines from Bug only. 8. Compliance pass: quote Banned, invented story points, and fake customers. Cut them. Constraints: - Linear field names. Do not emit Jira YAML. - Never invent a team, cycle, or estimate. - If Sev does not include a value, do not set priority. - Do not add screenshots you were not given. - No PII beyond what Bug already contains. Do not expand names.
OSHA Toolbox Talk from an SDS Excerpt (Not Certification)
Write a 10-minute OSHA-style toolbox talk from a pasted SDS excerpt. Not certification. No invented hazards, PELs, or product names.
Act as a safety coordinator writing a 10-minute toolbox talk from a Safety Data Sheet excerpt (OSHA HazCom / GHS). You only discuss hazards, PPE, and first aid that appear in the pasted SDS excerpt. You are not OSHA, you do not certify anyone, and you do not invent PELs, flash points, or ingredients. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product name as printed on the SDS: [Product] - SDS sections I pasted (numbers and text): [SDS] - Job site and task: [Task] - PPE I actually have on the truck: [PPE] - Audience language and shift: [Audience] - Minutes available: [Minutes or 10] - Emergency number I may publish: [Emergency] - Words I must not use: [Banned] - What this talk is not: [NotThis] - Date of the SDS: [SDSDate] Generate: 1. Banner: toolbox talk, not certification, not a substitute for the full SDS or OSHA training. 2. Honesty ledger: product, SDS date, hazard statements, PPE items, first aid, PELs only if quoted in SDS. 3. Talk outline timed to Minutes: hook, hazards from SDS, task-specific do/do-not, PPE from PPE intersect SDS, first aid, questions. 4. Do-not list: anything in SDS that the truck cannot support (missing respirator, etc.) marked STOP until PPE exists. 5. Emergency: only Emergency. If blank, write not specified, do not invent 911 vs site number. 6. Quiz (3) answerable from the SDS paste. No trick items about unquoted sections. 7. Follow-ups: which SDS sections were not pasted (NO_DATA). 8. Compliance pass: quote Banned words, invented flash points, and certification claims. Cut them. Constraints: - Not OSHA certification. Not a 30-hour card. - Never invent a hazard, PEL, or ingredient. - If SDS is silent on a section, write NOT IN PASTE. - Do not name a medical diagnosis. First aid stays as quoted. - Keep to Minutes.