◆ Amazon DynamoDB

Maintain reusable knowledge assets

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 taskDocument the new DynamoDB table design for the user profile service, including partition keys,…+
Document the new DynamoDB table design for the user profile service, including partition keys, sort keys, and global secondary indexes, and add it to our internal knowledge base by Friday.
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 add this database design document to the knowledge base, make sure it's easy for new…+
Before I add this database design document to the knowledge base, make sure it's easy for new engineers to understand. Clarify why we chose these particular access patterns, highlight any potential pitfalls, and suggest common query examples.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI've documented the DynamoDB table design for the new reporting service, focusing on the main…+
I've documented a new DynamoDB table, but I'm unsure if the chosen access patterns are truly optimal for our anticipated query load.
I've documented the DynamoDB table design for the new reporting service, focusing on the main dashboard queries. But I'm stuck on whether the current access patterns will scale efficiently if the sales team starts running ad-hoc analytical queries against it. I can't tell if I've over-optimized for one use case. What are the likely performance bottlenecks, and what's the best next step to validate this before it goes live?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur internal knowledge base for database designs often becomes outdated or hard to navigate,…+
I struggle to keep our knowledge assets up-to-date and easily searchable for the team.
Our internal knowledge base for database designs often becomes outdated or hard to navigate, leading to engineers re-solving problems. I spend too much time hunting for current information. What habit can I change to ensure these assets are consistently maintained, discoverable, and truly useful for the team as our services evolve?
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.