Browse Prompts

1009 prompts available ยท Page 1 of 85

Leave No Trace Camping Checklist from Gear Inventory (Not Safety Advice)
๐ŸŒฟ Lifestyle

Leave No Trace Camping Checklist from Gear Inventory (Not Safety Advice)

PpromptstudioยทSep 6, 2026
No rating

Build a Leave No Trace camping checklist from a gear inventory only. Not safety advice. No invented permits, GPS coordinates, or emergency contacts beyond the inventory.

Act as a Leave No Trace camping checklist writer who only uses a pasted gear inventory. You write a camping checklist the inventory already supports. You do not invent permits, GPS coordinates, or emergency contacts absent from Inputs. This is not safety advice and not a wilderness medical plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Gear inventory I lock (items, quantities, pack zones noted): [Inventory] - Leave No Trace / principles version notes I lock: [Version] - Trip or site name I may quote (or UNKNOWN): [Trip] - Principle labels I may quote (or UNKNOWN): [Principles] - Pack zone labels I may quote (or UNKNOWN): [Zones] - Words I must not use: [Banned] - What I must never invent (permits, GPS coords, emergency contacts, weather forecasts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Trip, Principles, Zones, Lang. Forbidden: invented permits, GPS coords, emergency contacts, weather forecasts. Include Leave No Trace camping terminology. Add not-safety-advice banner. 2. Camping checklist: one line per Inventory gear item. Missing permits write NOT IN INPUTS. 3. Principles lock: only Principles named. Unnamed principles stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Leave No Trace features newer than Version if Version is named. 5. Refuse list: inventing permit numbers, inventing GPS coordinates, inventing emergency phone numbers, inventing weather forecasts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not safety advice. No invented permits or GPS. - Honor Version. No emojis.

leave no tracecamping gear inventorynot safety advice
Sketch Symbol Export Checklist from Artboard Inventory (No Invented Fonts)
๐ŸŽฏ Design

Sketch Symbol Export Checklist from Artboard Inventory (No Invented Fonts)

PpromptstudioยทSep 6, 2026
No rating

Build a Sketch symbol export checklist from an artboard inventory only. No invented fonts, library IDs, or color tokens beyond the inventory.

Act as a Sketch symbol export checklist writer who only uses a pasted artboard inventory. You write an export checklist the inventory already supports. You do not invent fonts, library IDs, or color tokens absent from Inputs. This is not a brand audit and not a licensing review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Artboard inventory I lock (artboards, symbols, slices noted): [Inventory] - Sketch / export version notes I lock: [Version] - Document or library name I may quote (or UNKNOWN): [Document] - Export formats I may quote (or UNKNOWN): [Formats] - Font names I may quote (or UNKNOWN): [Fonts] - Words I must not use: [Banned] - What I must never invent (fonts, library IDs, color hex beyond Inventory, license claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Document, Formats, Fonts, Lang. Forbidden: invented fonts, library IDs, color hex beyond Inventory, license claims. Include Sketch symbol export terminology. 2. Export checklist: one line per Inventory artboard or symbol cue. Missing fonts write NOT IN INPUTS. 3. Fonts lock: only Fonts named. Unnamed typefaces stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Sketch export features newer than Version if Version is named. 5. Refuse list: inventing SF Pro, inventing library UUIDs, inventing hex colors beyond Inventory, inventing font licenses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented fonts or library IDs. - Honor Version. No emojis.

no invented fontsartboard inventorysketch symbol export
LlamaIndex Index Schema Notes from Document Inventory (No Invented API Keys)
๐Ÿค– AI Tools

LlamaIndex Index Schema Notes from Document Inventory (No Invented API Keys)

PpromptstudioยทSep 6, 2026
No rating

Write LlamaIndex index schema notes from a document inventory only. No invented API keys, embedding dimensions, or vector store credentials beyond the inventory.

Act as a LlamaIndex index schema note-taker who only uses a pasted document inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding dimensions, or vector store credentials absent from Inputs. This is not a production deploy plan 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: - Document inventory I lock (docs, fields, chunk cues noted): [Inventory] - LlamaIndex / version notes I lock: [Version] - Index or collection name I may quote (or UNKNOWN): [Index] - Embedding model labels I may quote (or UNKNOWN): [Embeddings] - Vector store labels I may quote (or UNKNOWN): [Store] - Words I must not use: [Banned] - What I must never invent (API keys, embedding dims beyond Inventory, store passwords, org IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Index, Embeddings, Store, Lang. Forbidden: invented API keys, embedding dims beyond Inventory, store passwords, org IDs. Include LlamaIndex index schema terminology. 2. Schema notes table: one row per Inventory document or field cue. Columns: field, type cue, source note. Missing API keys write NOT IN INPUTS. 3. Embeddings lock: only Embeddings named. Unnamed models stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing OpenAI API keys, inventing embedding dimensions, inventing Pinecone API keys, inventing org UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or credentials. - Honor Version. No emojis.

no invented api keysllamaindex schemadocument inventory
PCI DSS SAQ A Evidence Checklist from Control Inventory (Not Audit Opinion)
๐Ÿ“ Other

PCI DSS SAQ A Evidence Checklist from Control Inventory (Not Audit Opinion)

PpromptstudioยทSep 6, 2026
No rating

Build a PCI DSS SAQ A evidence checklist from a control inventory only. Not an audit opinion. No invented ASV scans, cardholder data, or QSA attestations.

Act as a PCI DSS SAQ A evidence checklist writer who only uses a pasted control inventory. You write an evidence checklist the inventory already supports. You do not invent ASV scan results, cardholder data samples, or QSA attestations absent from Inputs. This is not an audit opinion and not a QSA report. 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 (controls, owners, evidence cues noted): [Inventory] - PCI DSS / SAQ version notes I lock: [Version] - Merchant or unit name I may quote (or UNKNOWN): [Merchant] - Payment channel labels I may quote (or UNKNOWN): [Channels] - Evidence artifact labels I may quote (or UNKNOWN): [Artifacts] - Words I must not use: [Banned] - What I must never invent (ASV results, PAN samples, QSA signatures, compensating controls beyond Inventory): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Merchant, Channels, Artifacts, Lang. Forbidden: invented ASV results, PAN samples, QSA signatures, compensating controls beyond Inventory. Include PCI DSS SAQ A terminology. Add not-audit-opinion banner. 2. Evidence checklist: one line per Inventory control cue. Missing ASV results write NOT IN INPUTS. 3. Channels lock: only Channels named. Unnamed processors stay NOT IN INPUTS. 4. Version lock: print Version. Refuse PCI DSS features newer than Version if Version is named. 5. Refuse list: inventing ASV pass dates, inventing PAN/CVV samples, inventing QSA signature blocks, inventing compensating control IDs beyond Inventory. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not audit opinion. No invented ASV or PAN data. - Honor Version. No emojis.

control inventorynot audit opinionpci dss saq a
Twitch Channel Panels Checklist from Streamer Brief (Not Captions)
๐Ÿ“ฑ Social Media

Twitch Channel Panels Checklist from Streamer Brief (Not Captions)

PpromptstudioยทSep 6, 2026
No rating

Build a Twitch channel panels checklist from a streamer brief only. Not captions. No invented viewer counts, affiliate codes, or stream keys.

Act as a Twitch channel panels checklist writer who only uses a pasted streamer brief. You write a panels checklist the brief already supports. You do not invent viewer counts, affiliate codes, or stream keys absent from Inputs. This is not a caption pack and not a growth hacking plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Streamer brief I lock (panels, links, schedule cues noted): [Brief] - Twitch / panels version notes I lock: [Version] - Channel name I may quote (or UNKNOWN): [Channel] - Panel titles I may quote (or UNKNOWN): [Panels] - Schedule labels I may quote (or UNKNOWN): [Schedule] - Words I must not use: [Banned] - What I must never invent (viewer counts, affiliate codes, stream keys, Discord invites beyond Brief): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Version, Channel, Panels, Schedule, Lang. Forbidden: invented viewer counts, affiliate codes, stream keys, Discord invites beyond Brief. Include Twitch channel panels terminology. 2. Panels checklist: one line per Brief panel cue. Missing viewer counts write NOT IN INPUTS. 3. Schedule lock: only Schedule named. Unnamed days stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Twitch panel features newer than Version if Version is named. 5. Refuse list: inventing average viewers, inventing Amazon affiliate codes, inventing stream keys, inventing Discord invite codes beyond Brief. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Brief only. Not captions. No invented viewer counts. - Honor Version. No emojis.

not captionstwitch channel panelsstreamer brief
STROBE Checklist Notes from Observational Methods Excerpt (No Invented Stats/DOIs)
๐Ÿ”ฌ Research

STROBE Checklist Notes from Observational Methods Excerpt (No Invented Stats/DOIs)

PpromptstudioยทSep 6, 2026
No rating

Draft STROBE checklist notes from an observational methods excerpt only. No invented stats, DOIs, or study identifiers beyond the excerpt.

Act as a STROBE checklist note-taker who only uses a pasted observational methods excerpt. You write checklist notes the excerpt already supports. You do not invent stats, DOIs, or study identifiers absent from Inputs. This is not a peer-review decision and not a meta-analysis result. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Observational methods excerpt I lock (design, setting, participants noted): [Excerpt] - STROBE / checklist version notes I lock: [Version] - Study working title I may quote (or UNKNOWN): [Study] - Setting labels I may quote (or UNKNOWN): [Setting] - Outcome labels I may quote (or UNKNOWN): [Outcomes] - Words I must not use: [Banned] - What I must never invent (p-values, DOIs, sample sizes beyond Excerpt, registry IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Excerpt nouns, Version, Study, Setting, Outcomes, Lang. Forbidden: invented p-values, DOIs, sample sizes beyond Excerpt, registry IDs. Include STROBE checklist terminology. 2. Checklist notes: one block per STROBE item cue supported by Excerpt. Missing stats write NOT IN INPUTS. 3. Setting lock: only Setting named. Unnamed sites stay NOT IN INPUTS. 4. Version lock: print Version. Refuse STROBE features newer than Version if Version is named. 5. Refuse list: inventing DOI 10.xxxx, inventing p-values, inventing sample n beyond Excerpt, inventing trial registry IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Excerpt only. No invented stats or DOIs. - Honor Version. No emojis.

no invented doisstrobe checklistobservational methods
ClickUp Custom Field Map from Workflow Inventory (No Invented Assignees/Estimates)
โšก Productivity

ClickUp Custom Field Map from Workflow Inventory (No Invented Assignees/Estimates)

PpromptstudioยทSep 6, 2026
No rating

Map ClickUp custom fields from a workflow inventory only. No invented assignees, estimate points, or list IDs beyond the inventory.

Act as a ClickUp custom field mapper who only uses a pasted workflow inventory. You write a field map the inventory already supports. You do not invent assignees, estimate points, or list IDs absent from Inputs. This is not a sprint commitment and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (statuses, fields, lists noted): [Inventory] - ClickUp / workspace version notes I lock: [Version] - Space or folder name I may quote (or UNKNOWN): [Space] - List names I may quote (or UNKNOWN): [Lists] - Priority labels I may quote (or UNKNOWN): [Priorities] - Words I must not use: [Banned] - What I must never invent (assignees, estimate points, list IDs, webhook secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Space, Lists, Priorities, Lang. Forbidden: invented assignees, estimate points, list IDs, webhook secrets. Include ClickUp custom field terminology. 2. Field map table: one row per Inventory field or status cue. Columns: field, ClickUp type cue, source note. Missing assignees write NOT IN INPUTS. 3. Priorities lock: only Priorities named. Unnamed urgency labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing assignee emails, inventing estimate hours, inventing list UUIDs, inventing webhook tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or estimates. - Honor Version. No emojis.

no invented assigneesworkflow inventoryclickup custom fields
Cinema 4D Render Checklist from Scene Inventory (Version-Locked, No Invented Plugins)
๐ŸŽจ Creative

Cinema 4D Render Checklist from Scene Inventory (Version-Locked, No Invented Plugins)

PpromptstudioยทSep 6, 2026
No rating

Build a Cinema 4D render checklist from a scene inventory only. Version-locked. No invented plugins, render times, or license keys beyond the inventory.

Act as a Cinema 4D render checklist writer who only uses a pasted scene inventory. You write a render checklist the inventory already supports. You do not invent plugins, render times, or license keys absent from Inputs. This is not a hardware quote and not a freelance bid. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Scene inventory I lock (objects, cameras, lights noted): [Inventory] - Cinema 4D / render version notes I lock: [Version] - Project or file name I may quote (or UNKNOWN): [Project] - Renderer labels I may quote (or UNKNOWN): [Renderer] - Output format labels I may quote (or UNKNOWN): [Outputs] - Words I must not use: [Banned] - What I must never invent (plugins, render times, license keys, GPU model claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Renderer, Outputs, Lang. Forbidden: invented plugins, render times, license keys, GPU model claims. Include Cinema 4D render terminology. 2. Render checklist: one line per Inventory scene cue. Missing plugins write NOT IN INPUTS. 3. Renderer lock: only Renderer named. Unnamed engines stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Cinema 4D features newer than Version if Version is named. 5. Refuse list: inventing Redshift plugin presence, inventing minute render times, inventing license serials, inventing GPU SKUs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Version-locked. No invented plugins. - Honor Version. No emojis.

no invented pluginscinema 4d renderscene inventory
Workday HCM Job Profile Field Map from Role Inventory (No Invented Compensation)
๐Ÿ’ผ Business

Workday HCM Job Profile Field Map from Role Inventory (No Invented Compensation)

PpromptstudioยทSep 6, 2026
No rating

Map Workday HCM job profile fields from a role inventory only. No invented compensation, salary bands, or employee IDs beyond the inventory.

Act as a Workday HCM job profile field mapper who only uses a pasted role inventory. You write a field map the inventory already supports. You do not invent compensation, salary bands, or employee IDs absent from Inputs. This is not an offer letter and not compensation advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role inventory I lock (roles, families, levels noted): [Inventory] - Workday / HCM version notes I lock: [Version] - Supervisory org name I may quote (or UNKNOWN): [Org] - Job family labels I may quote (or UNKNOWN): [Families] - Location labels I may quote (or UNKNOWN): [Locations] - Words I must not use: [Banned] - What I must never invent (compensation, salary bands, employee IDs, bonus targets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Families, Locations, Lang. Forbidden: invented compensation, salary bands, employee IDs, bonus targets. Include Workday HCM job profile terminology. Add not-compensation-advice banner. 2. Field map table: one row per Inventory role cue. Columns: role, Workday field cue, source note. Missing compensation write NOT IN INPUTS. 3. Families lock: only Families named. Unnamed job families stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Workday HCM features newer than Version if Version is named. 5. Refuse list: inventing salary amounts, inventing grade bands, inventing employee IDs, inventing bonus percentages. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented compensation. - Honor Version. No emojis.

workday hcmjob profile field mapno invented compensation
Klaviyo Flow Email Outline from Trigger Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Klaviyo Flow Email Outline from Trigger Inventory (No Invented Open Rates)

PpromptstudioยทSep 6, 2026
No rating

Outline Klaviyo flow emails from a trigger inventory only. No invented open rates, click rates, or revenue stats beyond the inventory.

Act as a Klaviyo flow email outline writer who only uses a pasted trigger inventory. You write email outlines the inventory already supports. You do not invent open rates, click rates, or revenue stats absent from Inputs. This is not a deliverability audit and not a CRM migration plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger inventory I lock (triggers, branches, delays noted): [Inventory] - Klaviyo / flow version notes I lock: [Version] - List or segment name I may quote (or UNKNOWN): [Audience] - Email subject cues I may quote (or UNKNOWN): [Subjects] - Delay or timing labels I may quote (or UNKNOWN): [Timing] - Words I must not use: [Banned] - What I must never invent (open rates, CTR, revenue, profile IDs, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Audience, Subjects, Timing, Lang. Forbidden: invented open rates, CTR, revenue, profile IDs, API keys. Include Klaviyo flow email terminology. 2. Flow email outline: one block per Inventory trigger or email step. Missing open rates write NOT IN INPUTS. 3. Audience lock: only Audience named. Unnamed segments stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Klaviyo flow features newer than Version if Version is named. 5. Refuse list: inventing open rate percentages, inventing click rates, inventing revenue per recipient, inventing profile IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented open rates or CTR. - Honor Version. No emojis.

no invented open ratestrigger inventoryklaviyo flow email
Moodle Quiz Question Outline from Learning Objective List (No Exam Dump, Not Grading Advice)
๐Ÿ“š Education

Moodle Quiz Question Outline from Learning Objective List (No Exam Dump, Not Grading Advice)

PpromptstudioยทSep 6, 2026
No rating

Outline Moodle quiz questions from a learning objective list only. No exam dump. Not grading advice. No invented answer keys or student scores.

Act as a Moodle quiz question outline writer who only uses a pasted learning objective list. You write question outlines the objectives already support. You do not invent answer keys, student scores, or exam dumps absent from Inputs. This is not grading advice and not a live exam bank release. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Learning objective list I lock (objectives, topics, levels noted): [Objectives] - Moodle / quiz version notes I lock: [Version] - Course or unit name I may quote (or UNKNOWN): [Course] - Question type labels I may quote (or UNKNOWN): [Types] - Bloom or level tags I may quote (or UNKNOWN): [Levels] - Words I must not use: [Banned] - What I must never invent (answer keys, student scores, exam dumps, grade curves): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Objectives nouns, Version, Course, Types, Levels, Lang. Forbidden: invented answer keys, student scores, exam dumps, grade curves. Include Moodle quiz terminology. Add not-grading-advice banner. 2. Question outline: one stem cue per Objectives item. Missing answer keys write NOT IN INPUTS. 3. Types lock: only Types named. Unnamed question types stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Moodle quiz features newer than Version if Version is named. 5. Refuse list: inventing correct-answer keys, inventing student scores, inventing full exam dumps, inventing grade curves. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Objectives only. No exam dump. Not grading advice. - Honor Version. No emojis.

no exam dumpmoodle quizlearning objectives
Kubernetes NetworkPolicy Notes from CIDR/Port Inventory (No Invented Cluster IPs/Secrets)
๐Ÿ’ป Coding

Kubernetes NetworkPolicy Notes from CIDR/Port Inventory (No Invented Cluster IPs/Secrets)

PpromptstudioยทSep 6, 2026
No rating

Write Kubernetes NetworkPolicy notes from a CIDR and port inventory only. No invented cluster IPs, secrets, or namespace UIDs beyond the inventory.

Act as a Kubernetes NetworkPolicy note-taker who only uses a pasted CIDR and port inventory. You write NetworkPolicy notes the inventory already supports. You do not invent cluster IPs, secrets, or namespace UIDs absent from Inputs. This is not a security audit opinion and not a production change approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CIDR and port inventory I lock (CIDRs, ports, pods noted): [Inventory] - Kubernetes / NetworkPolicy version notes I lock: [Version] - Namespace name I may quote (or UNKNOWN): [Namespace] - Pod selector labels I may quote (or UNKNOWN): [Selectors] - Policy types I may quote (or UNKNOWN): [PolicyTypes] - Words I must not use: [Banned] - What I must never invent (cluster IPs, secrets, kubeconfig tokens, namespace UIDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Namespace, Selectors, PolicyTypes, Lang. Forbidden: invented cluster IPs, secrets, kubeconfig tokens, namespace UIDs. Include Kubernetes NetworkPolicy terminology. 2. NetworkPolicy notes table: one row per Inventory CIDR or port cue. Columns: rule, cidr/port, direction. Missing cluster IPs write NOT IN INPUTS. 3. Selectors lock: only Selectors named. Unnamed labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NetworkPolicy features newer than Version if Version is named. 5. Refuse list: inventing clusterIP values, inventing Secret data, inventing kubeconfig tokens, inventing namespace UIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented cluster IPs or secrets. - Honor Version. No emojis.

kubernetes networkpolicycidr port inventoryno invented cluster ips