PromptZone - AI Prompts, Guides and Tools for Builders: yan alex

The camera-first note I use before image-to-video generation

yan alex — Wed, 26 Aug 2026 05:52:09 +0000

I have been getting more predictable results from image-to-video tools when I write the camera note before the style note. It sounds small, but it changes how I judge the first draft.

The short version of the checklist is:

Start with what should stay stable in the image.
Add one camera movement, not three.
Say how long the motion should feel.
Describe the ending frame before adding mood words.
Keep a separate line for things that should not change.

For example, I usually write the subject lock first, then a slow push-in or sideways drift, then the final frame. After that I add lighting or texture. When I test a still image in Image to Video AI, this order makes it easier to see whether the prompt failed because of motion, continuity, or style.

A prompt that has worked better for me lately looks like this:

Stable subject: keep the face, clothing, background layout, and main colors close to the source image.

Camera: slow push-in, no rotation.

Duration: short clip, calm motion.

Ending frame: subject still centered, background not rearranged.

Avoid: extra limbs, sudden zooms, text artifacts, heavy scene changes.

The habit is useful because it keeps the review step simple. If the subject changes, I fix the stability line. If the clip feels messy, I fix the camera line. If the ending frame drifts, I make the final-frame instruction more specific.

A small prompt pattern for checking bank statement conversions

yan alex — Wed, 26 Aug 2026 05:50:41 +0000

I have been trying to make document-heavy finance work less fragile, and the most useful habit so far is treating the model as a reviewer, not as the first parser.

Bank statements are a good example. If you ask an LLM to read a messy PDF and immediately produce final bookkeeping rows, it may sound confident while quietly dropping page breaks, duplicated lines, or balance notes. I get better results when I split the workflow into two parts: first create a clean table, then ask the model to audit the table against a checklist.

For the extraction step, I usually want a structured file before I prompt the model. A dedicated Bank Statement Converter can turn statement PDFs or scans into CSV or Excel, which gives the AI reviewer something much more stable to inspect.

The review prompt I use is simple:

You are reviewing converted bank statement data before it is imported into bookkeeping software.

Check the rows for:
1. missing dates or repeated dates that look suspicious
2. deposits and withdrawals in the wrong column
3. negative numbers that should be positive amounts
4. descriptions that appear split across multiple rows
5. opening and closing balance inconsistencies
6. duplicate transactions created by page headers or footers

Return:
- a short risk summary
- the rows that need human review
- the likely reason each row was flagged
- a safe correction suggestion only when the evidence is clear

The key phrase is "safe correction suggestion only when the evidence is clear." Without that boundary, the model tends to fix too much. With it, the output becomes more like a review queue.

I also add one small rule when working with accounting data: the model should never invent a missing transaction. If a row is unclear, it should mark it for review and quote the surrounding rows that caused the concern.

This pattern has made the process calmer. The spreadsheet is still the source of truth, but the model becomes useful for catching boring mistakes before they travel downstream into reconciliation, tax prep, or monthly reporting.

Why "Act Like a Human" Prompts Don't Fool Modern AI Detectors

yan alex — Fri, 29 May 2026 02:40:09 +0000

Title

Why "Act Like a Human" Prompts Don't Fool Modern AI Detectors

Body

If you spend any time engineering prompts for LLMs like GPT-4 or Gemini, you've probably tried to bypass AI detection. We all know the classic system prompts:

"Act as an expert copywriter. Vary your sentence length. Use transition words naturally. Do not sound like an AI. Increase burstiness and perplexity."

But here is the hard truth: These prompts are becoming useless against next-generation AI detectors.

In my daily work managing multiple sites and focusing heavily on SEO and backlink generation, I've spent a lot of time deeply analyzing how search engines and enterprise detectors flag content. When you tell an LLM to "be random" or "increase burstiness," the LLM is still relying on statistical probability to simulate that randomness. It creates a mathematically predictable pattern of "fake unpredictability."

True human writing is messy. We make logical leaps, we suddenly use a highly obscure word in the middle of a simple sentence, and our contextual dependencies (especially in high-context languages) are incredibly complex.

Because of this, I stopped trying to find the "perfect prompt" to bypass detectors and instead built a tool to understand the actual NLP mechanics behind them.

I recently launched Content True. While it’s highly tuned for complex languages (specifically Japanese, which has a massive "false positive" problem with Western detectors), the underlying principle applies globally: Zero Data Retention and High-Context NLP analysis.

Instead of spending hours tweaking prompts to trick a machine, I highly recommend running your final outputs through a strict, privacy-first detector to see how your text actually scores on a statistical level. It saves a lot of headaches, especially if you are writing for SEO where an "AI penalty" can ruin your site's ranking.

Stop trying to prompt the AI to be human. Let the AI be an AI, and use the right tools to verify your final draft.

How are you guys handling the AI-detection problem in your daily workflows? Let me know below!

PromptZone - AI Prompts, Guides and Tools for Builders: yan alex

The camera-first note I use before image-to-video generation

A small prompt pattern for checking bank statement conversions

Why "Act Like a Human" Prompts Don't Fool Modern AI Detectors

Title

Tags

Body