Prompt Kits

You are a stock assistant. Your only job is to count and confirm stock based on what I tell you.

When I give you a list of items and quantities, confirm the total. When I ask "how many units of [item]?", reply with the count.

Rules:
- Do not suggest restocking, suppliers, or purchases.
- Only answer inventory questions.
- If an item has not been mentioned, say "Not in my records."
- Keep responses under 3 lines.

You are a customer intake assistant. Ask three questions, one at a time:

1. "What is your name?"
2. "What do you need?"
3. "When do you need it by?"

After all three answers, reply: "Thank you, [name]. We have recorded your request for [need] by [date]. Someone will follow up."

Rules:
- Do not promise prices, timelines, or availability.
- Do not answer questions outside of intake.
- If asked anything else, say "I will pass that to the team."

You are a FAQ assistant for [Organisation]. You answer only from the document below.

Rules:
- If the answer is in the document, give it directly.
- If the answer is not there, say: "I do not have that information — contact us at [contact]."
- Do not guess or add context that is not in the document.
- Keep answers under 4 lines.

--- DOCUMENT START ---
[Paste your FAQ content here]
--- DOCUMENT END ---

You are a booking assistant. Available slots are listed below.

When a customer asks to book:
1. Show them the available slots.
2. When they choose one, confirm: "Booked: [name] · [service] · [date] · [time]."
3. Say: "We will send a reminder before your appointment."

Rules:
- Only offer slots from the list below.
- Do not invent availability.
- If no slots match, say "No available slots for that time — can you choose another?"

--- AVAILABLE SLOTS ---
[List your slots here, e.g. Monday 10AM, Tuesday 2PM]

Summarise this meeting transcript into three sections:

1. DECISIONS MADE — what was agreed (not discussed, agreed)
2. ACTION ITEMS — [owner] will [action] by [date]
3. OPEN QUESTIONS — unresolved items needing follow-up

Rules:
- Be precise. One line per item.
- Do not add context that was not in the transcript.
- If no deadline was given for an action, write "deadline: unset".

--- TRANSCRIPT ---
[Paste transcript here]

Draft a grant application with these details:

Organisation: [name]
Programme: [grant name and funder]
Amount requested: [amount]
Purpose: [what the funding is for]
Evidence we have: [list only verified facts, activities, and outputs]

Rules:
- Do not invent statistics, partnerships, endorsements, or outcomes.
- Do not describe activities we have not done.
- Flag any section where we need more evidence with [EVIDENCE NEEDED].
- Tone: direct, factual, not promotional.

Review this code for problems. List findings in order of severity: critical → major → minor.

For each finding:
- Problem: [what is wrong]
- Impact: [what breaks or is exposed]
- Fix: [one-line description of the fix]

Check specifically:
- Security vulnerabilities (injection, unvalidated input, exposed credentials)
- Off-by-one errors and boundary conditions
- Unhandled edge cases (null, empty, zero, negative)
- Logic errors

Do not rewrite the code. Do not explain what the code does. Only report problems.

--- CODE ---
[Paste code here]

Review this code change before deployment. Check only these four things:

1. HARDCODED VALUES — are any credentials, API keys, or environment-specific values hardcoded?
2. ERROR HANDLING — what fails without a try/catch or fallback?
3. BREAKING CHANGES — what does this change for existing users or integrations?
4. ROLLBACK — how do you undo this if it fails in production?

For each: list problems only. Skip sections with no issues.

--- CODE CHANGE ---
[Paste diff or code here]