This article looks at five things we set aside. They are worth knowing about because the same patterns can turn up in any prompt, including ones you find elsewhere or write yourself.

A text says your package is stuck, your toll is unpaid, or a traffic fine needs attention. Maybe you have not touched it, or maybe you already tapped, typed something, or paid and now want a clean plan. The useful question is not “Does this look scammy?” but “How do I check the claim without trusting the message itself?”

A text just landed saying a package is held, a toll is overdue, or a traffic fine needs paying before a deadline. Maybe you haven't touched it; maybe you tapped, typed something, and the page didn't sit right. You know texts like this exist. What you need is a clear way to check this one and decide what's next.

You are looking at a text claiming a package is delayed, a toll is unpaid, or you owe a traffic fine. The message demands immediate action and usually contains a link or a request to reply. You need a fast way to evaluate the request and plan your next steps without interacting with the sender or their links.

The urge is good. It comes from the best place there is — someone trusts you, and you want to be worth it. This article is about why that particular way of helping — you, alone, relaying their problem to an AI assistant — is the wrong tool for the job, and what to do instead. The person who runs this site responds to security incidents professionally, and this is the warning he would give a friend.

Three posts, one from each of three AI tools, all working from the same written brief. The topic brief each post was written from is published in full inside every post, so you can judge each answer against the ask it was given. Two standing instruction files travelled with it — the required post structure, and the audience, standards and forbidden list — and those are not published.

A new icon has suddenly appeared on your kid's tablet, or they are asking to install a game you have never heard of. You need to know what this app actually does, how it makes money, and what permissions it asks for before deciding if it stays. It is difficult to assess a developer's motives just by looking at store screenshots, especially when you have a squirming kid waiting for an answer. You need a structured way to evaluate the software right now, while you have the device in hand.

You picked up the tablet to check the time and there's an icon you've never seen — some game with a grinning mascot, installed sometime this week. Your kid says everyone at school has it. You're not assuming the worst, but you'd like to know what this thing actually is before it becomes a fixture of the household. The device is in your hand; the answer shouldn't require a research project.

The cards below give you copy-paste prompts for working through that app with your AI while the device is in reach. They help you organize what you can observe, identify what still needs verification, and read the AI's answer without treating it as the final authority.