◆ Amazon DynamoDB

Fetch all items from a table

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 taskI need to get all the customer records out of the 'Customers' table and into a file so the…+
I need to get all the customer records out of the 'Customers' table and into a file so the sales team can do their quarterly review by Friday. Make sure the file is in a format they can easily open in their spreadsheet software.
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 I pull all customer data for the sales team, I need to make sure it's clean and usable.…+
Before I pull all customer data for the sales team, I need to make sure it's clean and usable. Filter out any records where the 'last_activity_date' is more than three years ago, and ensure all 'email' fields are valid before generating the export file.
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 sales team is asking for a full customer list again, but last time they said it was…+
The sales team just complained that the customer data I gave them last quarter was missing key information, but I thought I pulled everything.
The sales team is asking for a full customer list again, but last time they said it was incomplete. I'm afraid I'll miss something critical again and hold up their quarterly review. I'm not sure if I should just pull everything or if there's a specific set of fields they actually need. What's the best way to ensure I get all relevant customer attributes without overwhelming them with unnecessary internal data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get requests for 'all data' from various tables, but then the consuming teams…+
I keep getting requests for 'all data' from tables, but then the users always say it's too much or missing context.
I frequently get requests for 'all data' from various tables, but then the consuming teams always come back saying it's either too much or missing crucial context. This wastes my time and theirs. What habit should I change to better understand and deliver exactly what they need the first time, instead of just dumping raw table contents?
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.