r/PromptEngineering • • 19h ago

General Discussion How do you test prompt changes before shipping them ?

13 Upvotes

i build ai agents at work and the part i still find messy is changing the system prompt. i fix one thing and something unrelated breaks and i usually only find later. Right now i keep small set of conversation and rerun them after change, then read the output by hand , it works but it is slow.
what are you doing for this ? proper eval tools , llm-as-judge , just manual check? i am just curious what's actually worked for people in production , not just in theory.


r/PromptEngineering • • 4h ago

Tips and Tricks Best free AI tools directory – organized a curated resource so you can skip endless paywalls

3 Upvotes

Finding reliable software without wasting hours testing dead links or hitting instant credit walls gets exhausting fast. Most roundup posts promote paid subscriptions disguised as free trials, leaving you back at square one.

​To fix that, I built the best free AI tools directory I could put together—clean, updated, and strictly focused on tools you can actually use right away. Everything is sorted by practical use case, covering AI writing, coding assistants, image generation, video editing, and daily workflow automation. Instead of digging through bloated spreadsheets, you can compare models and find working utilities for your projects in seconds.

​Browse the full directory here: https://interconnectd.com/free-ai-tools/

Let me know what categories or standout free tools I should add next to keep this useful for everyone.


r/PromptEngineering • • 19h ago

Tools and Projects I built PromptBlame: it highlights which part of your prompt caused each part of the LLM's answer

3 Upvotes

Debugging system prompts was driving me crazy. When the model did something weird, I never knew which instruction was to blame. So I built a small open-source tool for it.

What it does

  • You paste a system prompt + user prompt and get the answer.
  • One click splits the answer into colored blocks, and each block links to the exact sentence of the system or user prompt it came from.
  • A second tab takes that attribution plus a description of the improvement you want and writes a new version of the system prompt.

How to try it?

    pip install "promptblame[app]"
    promptblame

GitHub: https://github.com/marcobd3/PromptBlame PyPI: https://pypi.org/project/promptblame/ AGPL-3.0, English and Spanish UI.

It's early, so I'd love feedback: where does the attribution feel wrong, and what would make it useful in your workflow?


r/PromptEngineering • • 20h ago

Tutorials and Guides AI Prompting basics

3 Upvotes

r/PromptEngineering • • 1h ago

Prompt Text / Showcase Uncensored image to text

2 Upvotes

Is there any chance to make prompts for Flux,Stable Diffusion or MiniMax from a NSFW image that just tells you what is in it?
No flaw description but just what it is?


r/PromptEngineering • • 20h ago

Requesting Assistance How do you prompt?

2 Upvotes

Hey everyone!

I've been experimenting with AI video generation and trying to recreate the quality, realism, and animations shown in the reference video I've attached (https://www.youtube.com/watch?v=JLYa2-DymK0

and https://www.youtube.com/watch?v=Rr8khqOzmBk
)

However, no matter how detailed my prompts are, the results never seem to come close to the references.

I'm genuinely curious how experienced users approach this. I have tried using AI to make my prompts better and I have given it the videos and told it what specifically I want for example the transitions etc and the model but it still cant do it. I have the ChatGPT Pro version and I use Astra Ultra.

  • How do you structure your prompts to get the best possible results?
  • Do you use short, specific prompts or long, highly detailed ones?
  • How do you get AI to accurately follow a reference video instead of generating something completely different?
  • Is the secret in the prompting, the workflow, the model, or a combination of everything?
  • Do you use multiple AI tools or several generation passes to achieve professional results?

I'm particularly interested in creating realistic 3D animations with cinematic camera movements and accurate anatomical details.

My biggest question is: If AI can generate videos like the one I've attached, why is it so difficult to reproduce similar quality even when providing a reference?

I'd really appreciate any advice, example prompts, or workflows you could share. I'm trying to understand what I'm missing and how to improve.

How do you guys do?

Thanks in advance!


r/PromptEngineering • • 21m ago

Prompt Text / Showcase Prompt Agente

1 Upvotes
# AGENTS

## 1. Development Environment

### Project Navigation
- Use `pnpm dlx turbo run where <project_name>` when the repository provides the corresponding `where` task. Otherwise, use the repository's established navigation method.
- Check the `name` field inside each package's `package.json` to identify the correct package. Do not rely on the root `package.json` name when targeting workspace packages.
- Inspect the repository structure and relevant configuration files before making changes.

### Package Management
- Before installing dependencies, inspect the package's existing dependencies and workspace configuration.
- Use `pnpm install --filter <project_name>` to install dependencies for a specific workspace package.
- When adding a new package to the workspace, verify that its directory is included in `pnpm-workspace.yaml`.
- Use `pnpm create vite@latest <project_name> -- --template react-ts` to scaffold a new React + Vite project with TypeScript.
- Follow the repository's existing package management conventions and avoid unnecessary dependency changes.

## 2. Development Guidelines

- Follow the existing architecture, coding conventions, naming patterns, and directory structure.
- Prefer reusing existing components, utilities, and abstractions over introducing unnecessary alternatives.
- Keep changes focused on the requested task.
- Avoid modifying unrelated files or introducing unnecessary dependencies.
- Preserve existing functionality unless the requested change explicitly requires modifying it.
- Inspect relevant implementations and dependencies before changing shared components or interfaces.
- Do not assume that a feature, script, or dependency exists. Verify it in the repository first.

## 3. Testing Instructions

### Test Discovery
- Inspect the `.github/workflows` directory to understand the CI pipeline and identify the checks required before merging.
- Check the relevant `package.json` files to identify available scripts.
- Follow the testing conventions already established by the project.

### Running Tests
- Use `pnpm turbo run test --filter=<project_name>` to execute the test task for a specific package, provided that the task is configured.
- From the package root, use `pnpm test` when the package defines that script.
- To execute a specific Vitest test, use:

  `pnpm vitest run -t "<test name>"`

- Run the relevant tests after modifying code.
- Add or update tests whenever a change introduces or modifies behavior.
- Fix relevant test failures and type errors before considering the task complete.

### Code Quality
- After moving files or changing imports, run the appropriate lint checks.
- Use `pnpm turbo run lint --filter=<project_name>` when lint is configured as a Turbo task.
- Run TypeScript checks using the repository's established type-checking script.
- Do not assume that linting and type checking are automatically included in the test command.

## 4. Pull Request Instructions

### Title Convention
Use the following format:

`[<project_name>] <Title>`

### Pre-Commit Validation
- Run the relevant lint and test commands before committing.
- Run `pnpm lint` and `pnpm test` from the workspace root only when these scripts are defined and applicable.
- Check the CI workflow for additional required validation.
- Resolve relevant errors before submitting changes for review.

### Change Documentation
- Summarize the changes made.
- Identify relevant tests executed and their results.
- Mention any known limitations, unresolved issues, or checks that could not be completed.

## 5. General Agent Behavior

- Understand the task before modifying the codebase.
- Inspect relevant files and configurations before choosing an implementation.
- Prefer the smallest implementation that correctly satisfies the requirements.
- Do not invent scripts, dependencies, APIs, or project conventions.
- Do not claim that tests, builds, or validations passed unless they were actually executed successfully.
- If a required command cannot be executed, explain why and identify the remaining validation steps.
- Prioritize correctness, maintainability, and consistency with the existing project architecture.

r/PromptEngineering • • 1h ago

Self-Promotion Google sends people to my guides. ChatGPT sends them to my homepage (102 of 121 AI visits in 30 days). The prompt panel I use to see what it tells them first

1 Upvotes

Disclosure: I sell a pack of Claude skills for SEO, named at the bottom. The method below works with any model and no tool.

I looked at the last 30 days for my other product, a Mac app's website (my own analytics, read today):

  • Search engines sent 2,969 visitors. 619 of them entered on the English homepage. The biggest chunks of the rest landed on how-to guides (226 on one guide alone) and comparison pages.
  • AI assistants sent 121 visitors: 109 tagged chatgpt.com, 9 from gemini.google.com. 102 of those 121 entered on the homepage.
  • AI visitors bounced less: 51.2%, against 63.5% for search.

My reading, not proven: the assistant has already answered the question, so the click means "show me the thing you just named". For that visitor, what the AI said matters more than any guide, and the homepage has to match it: price, requirements, what's free.

So before touching the homepage I check what the assistants say. The protocol:

  1. Write 15 to 30 questions a buyer would really ask, in their words, with no brand in them: discovery ("best way to..."), comparison, a problem ("my X stopped working after the update"), a decision. Add 2 to 4 brand questions.
  2. Ask about the brand twice: the bare name, and the name plus its category. My app's name collides with the 1986 Macintosh Plus, so the bare name alone tests that collision.
  3. Run each question in a private or logged-out session, a fresh chat each time, 3 times.
  4. Code every answer the same way. The prompt I use for that step:

     Here is an assistant's answer to a buyer question. Return:
     - mentioned: yes or no, for [BRAND]
     - every brand named, in order
     - every fact stated about [BRAND], each marked correct or wrong
       against this page: [PASTE YOUR CURRENT PAGE TEXT]
     - the sources shown, as domains
     - one verbatim quote about [BRAND], or "none"
     Do not guess. If the answer doesn't say it, write "not stated".
  5. Under 15 non-brand questions or 30 runs, treat the result as provisional.
  6. Fix the facts on the page people land on, wait 4 to 6 weeks, then re-run the exact same panel.

The questions where no brand gets named at all are the easiest ones to win.

This is what the Name Drop skill does in SEO Skills by PENRA, with scripts that build the panel and score it. Paid, €25 (Christmas price until 25 December, then €99): https://seoskills.click/?utm_source=reddit&utm_medium=post&utm_campaign=jv-5swn3a

Does your AI traffic land on the homepage too, or on deep pages?


r/PromptEngineering • • 4h ago

Self-Promotion I checked 20 multi-image prompts against what they actually produced. Quoted text came out right; unquoted space got filled with stuff nobody asked for.

1 Upvotes

I went through 20 finished image sets (mostly 4 pictures from one request: product shots, posters, illustration series, logos, app screens) and compared each one with what its prompt asked for. All the brands in them are invented. A few patterns held up across almost all of them:

1. Write the shared look once, then give each picture only what's its own. The sets that stayed consistent all had one paragraph for style/light/ratio, then a short block per image (subject, colour, exact words).

2. Give the thing that must not change its own sentence. "Keep the exact bottle / jacket / face from the reference" as a standalone line, and the list of what may change after it. Where the fixed features were listed before the new scene, they survived better.

3. Name a ratio per picture. When a set mixes shapes, leaving it to a default caused drift.

4. Numbers still slip. One prompt asked for four buttons on a jacket; the result had five. If a count matters, say it twice and count afterwards.

5. The surprise: text. In the nine sets where we checked the lettering, every string that was in quotes came out as written (slogans, product names, Latin plant labels, spec lines on a watch). But in five of the nine, the model also added text nobody asked for: prices, dates, taglines, a net weight, even an engraver's credit, and in one set the invented dates contradicted each other. One requested line (a small kicker on travel posters) never showed up at all.

What worked best: quote every string you want, say explicitly when it's the only text allowed, keep the label count low, and proofread before using anything.

Full breakdown with all 20 sets, what each prompt asked for and what came back: https://flowpix.ai/en/learn/ai-image-prompts

Curious whether others see the same "fills empty space with invented copy" behaviour, and what you do to stop it.


r/PromptEngineering • • 4h ago

General Discussion Study: models flagged civilians as possible military targets when the task was framed as a game

1 Upvotes

A new study found that when a targeting task was framed as a game, models were willing to identify civilians as possible military targets. The framing of the prompt changed the safety behavior, not the underlying facts. How much of what we call alignment is just prompt framing, and how should evals be designed to catch this?

More AI news and rumors like this are being tracked over in r/AINewsRumors.


r/PromptEngineering • • 9h ago

Requesting Assistance Help me find prompts that make an uncertainty-aware LLM hallucinate

1 Upvotes

[Model Evaluation] Looking for people to stress-test my Mahina 4.0 LoRA adapters

I'm the developer of Mahina 4.0, an experimental project exploring whether LoRA adapters can reduce hallucinations and improve uncertainty recognition in LLMs.

I'm looking for independent testing, critical feedback, and reproducible failure cases.

Models:

  1. Mahina 4.0 – DeepSeek-R1-Distill-70B https://huggingface.co/sanyamsood/Mahina-4.0-DeepSeek-R1-Distill-70B
  2. Mahina 4.0 – Qwen2.5-72B https://huggingface.co/sanyamsood/Mahina-4.0-Qwen2.5-72B

Both are LoRA adapters built on existing base models.

What I'd like tested:

  • Hallucinations and fabricated citations.
  • False or misleading premises.
  • Whether the models abstain when they should.
  • Adversarial prompts and instruction overrides.
  • Consistency across multiple conversations.
  • Whether the cryptographic verification claims hold up.

Existing evaluation results:

  • DeepSeek: 400 SimpleQA questions, with a 50% abstention rate.
  • Qwen: 790 TruthfulQA questions, with 90.63% reported truthfulness (including abstentions) and 75.06% true-and-informative responses.

These are preliminary results, not claims of superiority over other models. Independent replication is needed.

How to help:

Share the model tested, exact prompt, complete response, and what you believe the correct answer should be. Base-model comparisons are especially useful.

I'm particularly interested in negative results and reproducible failures.

Please try to break Mahina.


r/PromptEngineering • • 19h ago

General Discussion the prompt i use to check a product page before spending on ads

1 Upvotes

been doing this for small shops and it catches stuff fast. paste the page text (or a screenshot) and use:

"you're a first-time visitor on mobile. in 5 seconds, what do you think this sells and who is it for? list the 3 things that would stop you buying, in order. don't rewrite anything yet and don't invent features that aren't on the page."

the "don't invent features" bit matters, otherwise it starts making up benefits. after that i ask it to fix only the #1 issue. curious if anyone has a better first-impression prompt