◆ Amazon DynamoDB

Check if DynamoDB table exists

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCheck if a table named 'order_details' exists in the current region and tell me if it…+
Check if a table named 'order_details' exists in the current region and tell me if it does.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the deployment script tries to create the 'user_preferences' table, check if it already…+
Before the deployment script tries to create the 'user_preferences' table, check if it already exists. If it does, tell me its status and if it's active. If it doesn't, confirm that so the script can proceed to create it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'feature_flags' table is supposed to be present in this test environment, but my…+
A critical table for a new feature seems to be missing, but I'm unsure if it was deleted or just never created in this environment.
The 'feature_flags' table is supposed to be present in this test environment, but my application is failing to find it. I'm afraid it might have been accidentally deleted, or perhaps it was never provisioned correctly. I can't proceed with testing without knowing its status. How do I definitively check if it exists and what its current state is?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep running into frustrating errors during deployments or when running integration tests…+
I frequently encounter errors in deployment or testing because I assume tables exist when they don't, or vice-versa.
I keep running into frustrating errors during deployments or when running integration tests because my code assumes a table exists, but it doesn't, or tries to create one that's already there. This costs me a lot of debugging time. What habit should I change to ensure I always verify table existence reliably before proceeding with operations?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.