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 • • 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 • • 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 • • 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 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 • • 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 • • 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


r/PromptEngineering • • 20h ago

Tutorials and Guides AI Prompting basics

3 Upvotes

r/PromptEngineering • • 20h ago

General Discussion ChatGPT planned my Chicago itinerary like a frequent flyer, then packed my carry-on like it had never lifted a bag

0 Upvotes

i almost made the mistake of blindly trusting ChatGPT with my packing list at 1am last night. if i hadn't done a test pack on my living room floor, i would have been screwed. i'm flying to Chicago for 5 days tomorrow with no checked bag. normally this is brainless for me because i fly for work every month and have my routine dialed in. i use a 40L level8 carry-on that swallows a week of clothes without a fight, and the front laptop compartment holds my MacBook, iPad, and every charger so i don't have to open the whole bag in the TSA line. the wheels glide well enough that i can sprint across O'Hare one-handed when a connection gets tight without the bag fishtailing behind me. since i was exhausted from work this week, i got lazy and asked ChatGPT to plan the whole Chicago trip from scratch: itinerary and packing list. honestly, the itinerary blew me away. it mapped out neighborhood coffee spots right by my hotel, rainy-day museum backups, and even flagged which dinner places had a smart casual dress code. i sat there thinking, alright, this thing actually knows what it's doing. then i scrolled down to the packing list and lost my mind. it told me to pack a fresh dinner outfit for every single night, a light jacket plus a heavy winter coat because the lakefront wind shifts, and three pairs of shoes because walking sneakers, dress shoes, and a spare pair were apparently non-negotiable. it never asked how big my suitcase was. when i laid everything out next to my bag last night, the three pairs of shoes alone ate up half the main compartment, even with all my tech and cables tucked into the front pocket. by the time i added the two coats, two full days of clothes were still sitting on my couch with nowhere to go. smooth wheels aren't going to save a bag that won't zip. the itinerary felt like it was written by a frequent flyer. the packing list felt like it was written by an alien who had never lifted luggage in its life. has anyone figured out a prompt setup that forces these models to pack around real bag dimensions instead of an imaginary walk-in closet?


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 • • 1d ago

Tools and Projects Claude Code's /advisor can't hand work to other agents. Here's a skill.md that decides when a job needs splitting and which model gets each piece

2 Upvotes

Claude Code has a native /advisor [model|off] command. The main model does the work and calls a stronger advisor model at decision points. The docs say it "tends to consult before committing to an approach, when an error keeps recurring, and before declaring a task done, but the timing is model-driven rather than rule-based." The advisor has no tools, so it can't spawn or direct other agents.

That leaves a gap. If the job has to be split (collect sources, fact-check them, write, judge the draft), the advisor can't split it. The other option is Fable 5.2 as main model, delegating work down to cheaper models.

This skill decides between the two and sets the rules for the second.

What it does:

1. Picks a mode. Mode A (native /advisor): one cheaper agent can do the whole task and only the decisions need a stronger model. Mode B (Fable as main): the work has to be split across models.

2. Assigns tiers in Mode B. Fable plans, makes the calls and writes the final copy. Haiku collects sources and does read-only lookups. Sonnet fact-checks each claim against its saved source. A cheap model that did not write the draft cold-reads it.

3. Sets the handoff rules. Every subagent writes its full result to a file with no length limit. The message it returns to the orchestrator is 200 words or fewer and names the file. The cap is on the return message only, not the file and not the final copy.

4. Holds collector output until a checker passes it. Verdicts are PASS, FIX, UNSUPPORTED, NO SOURCE. (The skill check in the table below used a different set: DRIFT, INVENTED, MISSING.) The orchestrator keeps one run-log row per subagent: job, model, tokens, verdict, file.

5. Uses fresh agents for cheap jobs. A forked subagent inherits the parent model and ignores the model override.

It doesn't decide whether to delegate. That's my earlier skill, subagent-dispatch-economics (post: https://www.reddit.com/r/PromptEngineering/s/ivuwzVYwad). This one starts after that decision.

Why the checker tier is there: in an earlier session a Sonnet checker found a "quote" a Haiku collector had saved that wasn't on the page. On 16 Nov I ran the pattern itself, with Fable 5.2 as main model and /advisor off:

jobmodeltokensverdict
read-only lookup of my tool's databaseHaiku91,409rows found; no token/cost data recorded
fact-check of the generated skill (first generation, before the fixes below)Sonnet78,43728 claims: 8 PASS, 4 DRIFT, 11 INVENTED, 5 MISSING
fact-check of Fable's own LinkedIn draftsSonnet89,86156 rows: 37 PASS, 5 FIX, 10 UNSUPPORTED, 4 NO SOURCE
cold-read judge of those draftsHaiku79,6347 drafts scored 2-4 of 5; 2 AI tells

That's 339,341 subagent tokens in total. All four returned 200 words or fewer and wrote a file. Fable's own token count isn't visible from inside the session. The checker flagged 19 lines in the top model's drafts, so the top model needs checking too.

About the cost claim you may have seen: Anthropic's April blog post reports Sonnet with an Opus advisor at +2.7 points on SWE-bench Multilingual and 11.9% lower cost per task. Those were older models (Opus 4.6 as advisor), not Fable 5.2. The current platform docs only say "Opus keeps total cost similar or lower; Claude Fable 5.2 maximizes the quality lift." I couldn't find a Fable advisor number from Anthropic, so the skill doesn't use one.

How it was made, and what it taught me about my own tool: I generated it with the Context Engineering pipeline in my tool, from a goal plus a one-page reference file of verified facts. Then I ran an evaluation: 4 skills x (with reference / goal only) x 2 runs, 16 generations on production.

  • With a reference file: 8 of 8 usable. 74 of 80 required rules came through, and every limit kept its qualifier.
  • From a goal only: 0 of 8 worth using. Each was well-formed but hollow, and each carried my platform's own security boilerplate ("sanitize external inputs", "least privilege") even for skills with no tools or inputs.

The two evaluation rounds led to three fixes, now live:

  • A prompt bug that deleted the steps from skills (15 of 16 lost them in the first round).
  • The boilerplate no longer appears for goals that don't mention access, input, auth or data (a keyword check).
  • A goal with no reference now warns you it will be a scaffold before you spend credits.

The advisor file below started as the reference run's output. I rebuilt it by hand from the reference file:

  • Removed one invented line (a garbled version of the benchmark caveat plus the boilerplate).
  • Put back the companion-skill pointer, which the generator dropped in both runs.
  • Added the Mode A limits, the fork rule, the checker gate, and the Never and Requirements sections.
  • Rewrote the description.

What I checked and didn't: a fresh Sonnet agent followed the skill on four tasks with pass conditions fixed beforehand: a variable rename, a fact-checked blog post from 6 sources, a flaky test, and 40 tickets summarized for a CEO. It picked the expected path all four times. It also listed six unclear spots, and I fixed three. That run came before my last wording edits and I didn't repeat it. This is a smoke test on four prompts, not an evaluation. I haven't measured whether Mode B is cheaper or better than one Fable agent doing everything.

The Skill Definition (skill.md):

---
name: "advisor"
description: "Decides which Claude model tier does which job when Fable 5.2 is available, and sets the handoff rules between them. Use when a task could run under native /advisor or with Fable as main model delegating to cheaper models. Not for deciding whether to delegate at all (see subagent-dispatch-economics)."
---

# advisor

Chooses between native /advisor (a cheaper model works, Fable 5.2 advises) and Fable 5.2 as main model delegating down to cheaper models, then assigns each job to a tier and enforces the handoff rules.

## Instructions

### Steps
1. **Confirm delegation is decided.** Whether to delegate, and fork vs. fresh agent, belongs to `subagent-dispatch-economics`. This skill starts after that decision. Do not restate it. If the answer is "don't delegate", stop here and do the task in the main session.
2. **Choose the mode.**
   - **Mode A, native `/advisor`:** one cheaper main model can do the whole task and only the decisions need a stronger model. The advisor has no tools and cannot delegate or orchestrate. Its call timing is model-driven; there is no setting to cap or force calls, so ask in your instructions if you want more or fewer.
   - **Mode B, Fable 5.2 as main:** the work must be split across models. Fable plans, judges and writes the final copy. It delegates lower-level jobs to fresh subagents with a per-spawn model override.
3. **In Mode B, assign tiers:**
   | Job | Model |
   |---|---|
   | Plan, make the calls, write the final copy | Fable 5.2 (main) |
   | Collect sources, read-only lookups | Haiku |
   | Fact-check each claim against its saved source (web page, file or input record) | Sonnet |
   | Cold-read judge of the final draft (no project context) | Haiku or another cheap model, a fresh agent: never the writer, never the agent that collected |
4. **Spawn cheap jobs as fresh agents.** A forked subagent inherits the parent model and ignores the model override.
5. **Apply the handoff rules** (below) to every subagent.
6. **Gate on the checker.** Collector output is not trusted until a checker tier that did not produce it passes it. The orchestrator's own drafts go through the checker too.
7. **Keep the run log.** One row per subagent: job, model, tokens (as the harness reports them; write "not available" if it doesn't), verdict, output file.

### Handoff Rules
- Every subagent writes its full result to a file. The file has no length limit.
- The message a subagent returns to the orchestrator is 200 words or fewer and names the file.
- The 200-word cap applies only to that return message, not to the result file and not to the orchestrator's final copy.
- Checker verdicts: PASS, FIX, UNSUPPORTED, NO SOURCE.

### Never
- Present the Sonnet + Opus advisor benchmark (+2.7 points, 11.9% lower cost, Anthropic blog, April 2026, older models) as a Fable 5.2 result.
- Let the writer judge its own draft.
- Use a forked subagent for a job meant for a cheaper model.

### Requirements
- Native /advisor is experimental and requires the Anthropic API, Claude Platform on AWS, or Claude Models on Google Cloud (Anthropic managed). Fable 5.2 requires Claude Code v2.1.321 or later. On some plans Fable usage, including as advisor, bills to usage credits.

Which describes you best? A) I run one model for everything. B) I use /advisor already. C) I hand jobs to cheaper subagents by hand. D) I have a checker step that isn't the writer.

Has a cheap checker ever caught something your top model got wrong?

Repo: https://github.com/nivlewd1/prompt-optimizer/tree/main/skill/advisor

I built a platform that generates skills like this from a goal and a reference file: promptoptimizer.xyz/about/context-engineer (signup required, free tier).


r/PromptEngineering • • 1d ago

General Discussion DOJ reportedly used Pangram AI-detector results as exhibits in a federal case — detectors in court now?

9 Upvotes

In a federal case in the Northern District of Texas, the DOJ reportedly used output from the Pangram AI detector as court exhibits. That is a big step: detector scores have known false-positive problems, and they are now showing up as evidence.

Should AI-detection output ever be admissible without independent verification? How would you challenge it if you were on the other side?

Stories at the AI-and-law intersection get tracked in r/AINewsRumors too.


r/PromptEngineering • • 1d ago

General Discussion Do not listen to u/Spacmonitor , they are a scammer pushing their AI Humanizer that doesn’t work.

3 Upvotes

Don’t fall for the scammer Reddit user u/Spacmonitor , they are spamming multiple subreddits with their AI Humanizer called Wento.ai that doesn’t work: https://www.reddit.com/r/PromptEngineering/s/xBBAfHVGmq

As soon as I commented that I tested it on all Modes and the text came back 100% AI on detectors, they deleted their post + comments and blocked my account. Don’t be dumb like me, avoid this scam!!


r/PromptEngineering • • 1d ago

Quick Question Looking for Claude Pro

0 Upvotes

Hey everyone, does anyone happen to have a Cloud Pro invite available? I'd really appreciate it if someone could send me one.🙏🙏


r/PromptEngineering • • 1d ago

Tips and Tricks Run this prompt before you split a Claude Code task into subagents

4 Upvotes

same task, no subagents:

Do this task yourself, without subagents. Read the files you need, make the change, and run the tests.

then run your subagent version with the same time limit and compare /usage. a team almost always gets more compute than the one agent it's compared to, so this is the fair version. run both twice, a break can show up in only one of two runs.

wrote up the rest in my newsletter, including when subagents do pay off: https://newsletter.diamant-ai.com/p/when-claude-code-subagents-help-and?utm_source=reddit&utm_medium=social&utm_campaign=black-friday-2026&utm_content=promptengineering


r/PromptEngineering • • 1d ago

Tips and Tricks Meta Modell prompting strategy

0 Upvotes

Years ago I read the structure of magic by Richard bandler. Now I catch myself using the knowledge for prompting.

For example If I belief Codex can handle it I keep it vague. When I know he will have a Hard time write out instructions very Detailed.


r/PromptEngineering • • 1d ago

Tools and Projects The biggest prompt I've written isn't a paragraph, it's a folder

2 Upvotes

I've been running two coding agents for sometime, Claude Code and Codex, on real work every day. The rules that made them reliable ended up as a folder of markdown, so I cleaned it up and turned it into a guided setup. You open the folder in either agent and paste one line: "Set me up. Follow the Dev Crew playbook in this folder from the start, or resume where we left off. One step at a time, and check each step on my computer before moving on."

From there the agent walks you through the whole thing step by step, checking each step on your machine. It covers Git, Docker for testing locally, GitHub for backup and releases, the second agent if you want one, and whatever other tools you use.

Pick whichever agent you want leading:

Claude Code first, Codex optional:

https://github.com/AffStackDev/dev-crew-kit

Codex first, Claude optional:

https://github.com/AffStackDev/dev-crew-codex

These are the prompt engineering parts that actually mattered.

Rules go where the agent loads them by itself, not in the chat. Claude reads CLAUDE.md and Codex reads AGENTS.md at the start of every session. Anything said only in chat gets lost when a long chat is compacted.

Don't load the whole playbook up front. The agent reads each step's file in full when it reaches it, not before and not from memory. It writes its progress to a file after every step, so a brand-new session can pick up from that file alone.

Quote the owner word for word. My rules sit in the rule files as exact quotes with dates, not the agent's paraphrase, because paraphrases drift.

Put a marker line at the very bottom of the global rules file. If that line shows up in what the agent actually loaded, the whole file made it in. Codex can print its loaded prompt without calling the model, so checking costs nothing.

Tell it what to do when a new request conflicts with an old decision. One of my behaviour checks failed until I added this: a fresh chat read a new request as permission and drafted ten posts that an earlier decision had ruled out. The fix was one rule: quote the earlier decision, say what the normal workflow would do, and ask whether I'm overriding it.

Test the prompt like code. The behaviour checks run fresh agents with nothing but the request, and each check runs twice, because one pass can be luck.

Don't make an agent wait on an exact phrase. A watcher that waited for the other agent to write "COMPLETE" slept through a finished task because the other agent worded it differently. Now it wakes on any change to the file.

Instructions relayed by another agent are reports, not orders. When Claude tells Codex "the owner wants X", Codex confirms it with me before treating it as my word.

A checklist the agent is told to review is optional to a model. A failing check isn't. Anything that must always be true becomes a test.

Feel free to go through every file before you run anything, or have Claude or Codex inspect the whole thing first and tell you what it does. It's mostly markdown plus a few small scripts. It asks before every install or download, and you type your own passwords and tokens.

Disclaimer: I built this workflow with AI's help while actually working on our own and client sites. It's free and it's staying free. No paid version is coming: no paywall, no affiliate links, no commissions, no signup. It's not a funnel to anything else, either. It's on my business's GitHub account because that's where I keep my stuff, but nothing in it mentions or links to anything I sell. It's text files and a few small scripts that run on your own computer through your own Codex or Claude app. There's no tracking, nothing reports back to me, and you type your own passwords and tokens.


r/PromptEngineering • • 1d ago

Tools and Projects Rolled out a new experimental step-prompting feature in my free AI app

3 Upvotes

Hi guys. I am the creator of Midum, a free and source available AI runtime. I recently rolled out an experimental prompting feature in it called step-prompting. Basically, it allows you to specify steps for your AI to follow, check off, and optionally provide a proof/verify for each step. It works by first letting the user define steps in a panel that appears over their prompt box and optionally select if the model should verify it and define if the model should do only a set number of steps in that response. Then when they send the prompt, the model gets the prompts each response and tool turn, along with the proper instructions telling it to follow the steps. It checks out individual steps one by one, and provides proof of completion if selected. The way it is different from simply typing in bullet points in a normal prompt is that it gives the model a strict system governed incentive and guidance to follow the steps. In addition, the model can write steps for itself if steps haven't been explicitly provided and it deems that writing steps can be beneficial. In my current testing, completion rate has been significantly higher in step prompting than mentioning the same prompts in bullet points in the prompt (Note: if you test this, turn off the tool that lets the model write its own steps first, otherwise it will convert the bullet points into steps itself). Because you guys are the experts in this field, I thought some feedback from you would be nice.

If you want to test it, you can get the app for free from GitHub or from the Microsoft Store.

Thank you <3 :D


r/PromptEngineering • • 1d ago

General Discussion Five edits to one prompt: what each one looked like vs. what the test set showed

3 Upvotes

From an article I wrote (hypothetical prompt, illustrative numbers). A prompt turns meeting transcripts into JSON action items that a script uses to create tasks. A fixed set of 8 test transcripts is run after every edit, three runs per case. Here’s each edit side by side:

EditWhat it looked likeWhat the test set showed
v1.1: “Do not invent due dates; use null if none is stated”A clear improvement, since the invented date was goneStill 5 of 8. “Next Friday” now failed, because the model had no meeting date to resolve it against
v1.2: add a meeting_date field to the input and resolve relative dates against itA prompt tweak6 of 8, but it was also a contract change: every caller now has to send the field, so prompt version and input schema version need to be tracked together
v1.3: add “Be concise”Cleaner, shorter outputs5 of 8. A commitment mentioned in passing was dropped, and nothing about the cleaner output suggested a task was missing
v1.4: replace “be concise” with “include every commitment, even if stated briefly; one sentence per task”, plus “unassigned, never guess” and “empty list if no items”A longer prompt7 of 8. The remaining failure is two attendees with the same first name, which the transcript can’t resolve. Logged as a known limitation
Week 8: no prompt changeNothing to look at6 of 8. The provider had updated the model behind the endpoint, and one case started returning dates in a different format

Three things I took from writing it:

  • Totals can hide movement. After v1.1 the total didn’t change, yet the set of failing cases did. Reading per-case results is what shows a regression.
  • Some edits aren’t prompt edits. Contract changes and model changes need to be recorded too, or you’ll search the prompt for a mistake that isn’t there.
  • Writing the reason next to each rule is what lets someone who wasn’t there decide later whether it can be removed.

Limits: eight cases catch only the regressions you thought to include. Pass/fail is coarse (a correct but badly worded output passes). Three runs is a small sample, and the process costs time, so it’s not worth it for a prompt one person uses occasionally.

The full write-up, with a case-by-case matrix and how I’d keep the log, is here. I’m the author, and the article also mentions a paid resource of mine near the end, so treat the link as optional: https://medium.com/@nagatomopedro05/five-versions-of-one-prompt-and-what-the-changelog-caught-00c63d1b1c00

When you edit a prompt that other code depends on, how do you check that you haven’t broken a case you weren’t looking at?


r/PromptEngineering • • 1d ago

Tips and Tricks How I prompt AI

9 Upvotes

I've been both software engineer and a systems engineer for long time. 20+ YOE

I don't create huge monlithic prompts to give to the AI agents. This typically will fail.

What I do is have the AI start at a baseline. If it's greenfield then it starts with requirements. If it's maintaining existing code then it starts with having the AI explore and analyze the solution. If you're working in copilot use .copilot-instructions to setup any instructions you want read on every request. You can also have AI generate a AGENTS.md for the project. Add any guardrails/rules you want the AI to follow for every request to that file. Avoid conflicting instructions.

When optimizing. Go in stages. Priompt to create baseline benchmark tests against the code you want to optimize. This should be fairly short prompt maybe one paragraph. Next, have the AI create a staged optimization plan. It may ask questions for any decisions to be made that will impact the code. Once the plan is made, review it and make any change before you give the greenlight.

As the AI makes changes. Review the changes. Verify it each stage works as you want.

At the end stage, re-run the bencmarks and verify the improvements with measured results.

Have the AI generate a full report of the results and any measured improvements.


r/PromptEngineering • • 1d ago

General Discussion Before/after: I turned a one-line bakery newsletter request into a structured prompt — what would you tighten?

0 Upvotes

I keep giving ChatGPT one-line writing tasks and getting back emails that invent prices, ingredients and process details I never gave.

Today's example was this one-liner:

help me write a weekly newsletter for my bakery customers about our new sourdough

That's the entire brief. No price, no launch date, no flour blend, no CTA preference.

I rewrote it into the structured prompt below (trimmed a little). I'm not claiming this is the right pattern — I'd rather people poke holes in it.

## Role
You are a small-business email marketer who writes short newsletters and customer updates that people open, read on a phone and act on.

## Context
Readers (as I said): my bakery customers

## Task
Help me write a weekly newsletter for my bakery customers about our new sourdough.
Success looks like: I get a ready-to-send email with a subject line, preview text and one clear call to action, using only the details I gave and [placeholders] for the rest.

## If details are missing
I haven't told you these yet, so assume:
- Key news / facts: use [placeholders] for any date, price or product detail I haven't given; never invent them
- Call to action: one simple next step, such as replying, visiting or ordering
- Length: 150–250 words, readable in under a minute
State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first.

## Constraints (shortened)
- Don't invent facts, statistics, quotes, sources or details about me; use [placeholders] for anything I didn't give
- Exactly one call to action
- Never invent product details, prices, dates, numbers, process facts (e.g. fermentation time, ingredients), quotes or testimonials
- Warm, plain language for existing customers; no SEO keywords or blog headings

## Output format
- Subject line (+2 alternatives)
- Preview text (under 90 characters)
- Email body (plain text, short paragraphs)
- Call to action (one line or button text)

Why I added each part:

  • Role: "small-business email marketer" sets the job and the channel (a phone-length customer email), so the model doesn't drift into an SEO blog post or a generic marketing essay.
  • Stated details over defaults: the audience I actually named — "my bakery customers" — is copied into Context as "Readers (as I said)". The 150–250 word length is listed as an assumption because I didn't give a length, not as if I had asked for it.
  • Placeholders instead of invented facts: the brief only says "new sourdough". Price, date, flour and process details are unknown, so the prompt says to write [placeholder] rather than invent a fermentation time or a launch price.
  • One CTA: a weekly bakery email is easy to overload with "reply, visit, order, follow us". The prompt asks for exactly one next step and checks that before answering.

When I ran this, the model did use [placeholder] for flour and price. It still invented sensory and process details I never gave — "tangy, crusty loaf", "slow-fermented starter", "chewy crumb", "golden-brown finish", and a "limited-time" launch week. So the structure helped with numbers, and leaked on adjectives.

I built a free tool that does this, link in comments if allowed.

If you were tightening this prompt, what would you change so those invented sensory details don't sneak through? Would you force the model to ask up to 3 questions first, or is there a better constraint?