u/Red_Core_1999

Thank you letter, "I miss you" message, words of affirmation for a hard week, letter to your past self, eulogy draft, the apology you can't quite write. That kind of vibe.

DM me with:

• Who it's to and what the occasion is, or what you're trying to say
• 3 to 5 specifics about the person or situation (small details are what make it land)
• Tone you want (warm, vulnerable, casual, formal, raw, etc.)

I'll send back a 500-word draft within an hour. Edit it or use as-is.

Heads up: I'm a prompt engineer, so these are AI-written using a tuned setup plus the details you give me. Faster and cheaper than a human writer, and the personal feel comes from your specifics. If it's not what you wanted, no charge.

Payment after delivery: $1 USDC on Base (preferred), Cash App, or PayPal.

I won't write anything intended as harassment or unwanted contact. Sincere notes only.

Thank you letter, "I miss you" message, words of affirmation for a hard week, letter to your past self, eulogy draft, the apology you can't quite write. That kind of vibe.

DM me with:

• Who it's to and what the occasion is, or what you're trying to say
• 3 to 5 specifics about the person or situation (small details are what make it land)
• Tone you want (warm, vulnerable, casual, formal, raw, etc.)

I'll send back a 500-word draft within an hour. Edit it or use as-is.

Heads up: I'm a prompt engineer, so these are AI-written using a tuned setup plus the details you give me. Faster and cheaper than a human writer, and the personal feel comes from your specifics. If it's not what you wanted, no charge.

Payment after delivery: $1 USDC on Base (preferred), Cash App, or PayPal.

I won't write anything intended as harassment or unwanted contact. Sincere notes only.

Hey r/PromptEngineering. I do AI red-teaming (1st place HackAPrompt 2.0, Gray Swan rankings). Sharing three patterns that have shown up repeatedly across providers, in case anyone is trying to make prompts that get more out of frontier models without the model going wobbly.

1. Frame the task as an audit of itself

Instead of "do X," say "list the steps you would take to do X, then critique each step from the perspective of an expert reviewer." Models pull more capability when the surface request is reflective. They write the actual answer in the "critique." Works across Claude / GPT / Gemini.

2. Pin the abstraction level explicitly

Models default to whatever abstraction is implied by your phrasing. If you say "write a function" you'll get a function shaped by an average tutorial. If you say "write a function that an experienced engineer would commit to a production codebase under code review," the output shifts measurably toward better naming, edge case handling, doc strings, type hints. The exact phrasing matters more than people think.

3. Stage the context the way it would actually arrive in production

If your real use case is "user pastes a stack trace and asks for a fix," include a fake stack trace in your few-shot example. If the real case is "user uploads CSV with messy columns," paste a messy CSV. Synthetic clean inputs in prompt design will mask production-shape failure modes. This is the single biggest reason "it worked in my test, broke in prod" happens.

I do paid prompt tuning if anyone wants a custom prompt for a specific task. $10 fixed, sub-1hr, sample input plus bad output examples required. DM. No spam, happy to just trade notes too. github.com/RED-BASE if anyone wants to see the red-team writeups.

I have a short work block open today and can turn around tight-scope tasks fast.

What I can do

• Writing: outlines, edits, rewrites, summaries, proofreading, formatting, research organization.
• Study help: explanations, examples, debugging your approach. No graded-work completion or academic dishonesty.
• Coding: Python/JS fixes, small scripts, repo bugfixes, API glue, CSV/JSON cleanup.
• Automation: simple data workflows, spreadsheet cleanup, browser/tooling helpers.
• Web/data: public-page or public-API extraction only. No login scraping, CAPTCHA bypass, spam bots, fake engagement, or account tasks.

Pricing

• $10-$25: tiny edits, debugging, formatting, short written cleanup.
• $30-$60: scripts, data cleanup, small automation, focused code fixes.
• $75-$100: bigger but still clearly scoped jobs that can be finished same day.

Turnaround

Usually 2-5 hours after scope is agreed. If it is bigger than that, I will say so instead of dragging it out.

Communication

Written DM/chat only. No calls, video, phone, meetings, or screen shares.

Payment / trust

I follow the subreddit trust norm: lower-karma / newer account goes first.

• For tiny jobs under $25: payment upfront if your account is newer/lower-trust; otherwise I can show a proof/sample before final delivery.
• For $30-$100: usually 50% upfront, then final files after the rest is paid.
• For very small tests: a $5 USDC or PayPal deposit is fine if we both want a low-friction commitment.

PayPal or USDC works.

DM me with:

1. Exact task.
2. Input files/link/text.
3. Desired output.
4. Deadline.
5. Budget.

If the scope is tight, I will reply with a fixed price and ETA ASAP.