Promptmaxing — Lobstermax

Core pattern

One prompt, four headers

If you only remember one thing: do this.

Goal:
- <what you want>

Context:
- <files, URLs, constraints, current behavior>

Constraints:
- <security rules, OS rules, time budget>

Output format:
- <bullets / JSON schema / markdown sections>

For code work

Ask for diffs + verification commands

Keeps reviews fast and reduces accidental breakage.

When you change code:
- Show a minimal diff (or exact before/after snippets).
- Explain why the change fixes the issue.
- Provide 1–3 exact commands to verify.
- If there’s a risk, add a rollback note.

“I’m on Windows PowerShell” reminder

Stops the classic `&&` / quoting issues.

Environment:
- Windows PowerShell
- Use `;` (not `&&`) as a statement separator.
- Prefer `cmd /c` if a command expects CMD parsing.

High-signal prompts

Bug report → patch

Gives the agent enough to reproduce and fix.

We have a bug.

Symptoms:
- <what you see>

Expected:
- <what should happen>

Repro:
- <exact steps or commands>

Artifacts:
- Logs:
  - <paste>
- Relevant files:
  - <paths>

Task:
- Identify root cause.
- Propose 1–2 fixes.
- Implement the safest fix with a minimal diff.
- Add a test or verification command.

Research → executive brief (with citations)

Avoids walls of text and demands sources.

Research question:
- <one sentence>

Constraints:
- Use only primary sources when possible.
- Provide citations as URLs.
- Keep answer to 10 bullets max.

Output:
- Summary (3 bullets)
- Key facts (bullets, each with a citation)
- Open questions / unknowns

"Make it runnable" (commands + env)

Turns "works on my machine" into explicit steps.

Goal: make this runnable for a new machine.

Deliverable:
- A short Quickstart section with exact commands.
- List required environment variables.
- Include a troubleshooting section with 3 common failures.

Constraints:
- Assume Windows PowerShell.
- Don’t include secrets.