◆ Apache Cassandra

Keep records of business transactions

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
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskLog the payment of $12,500 from Acme Corp for invoice #2023-09-012 into the transaction ledger,…+
Log the payment of $12,500 from Acme Corp for invoice #2023-09-012 into the transaction ledger, marking it as received today, October 26th.
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 acceptWhen recording this payment from Acme Corp, can you also cross-reference it with their open…+
When recording this payment from Acme Corp, can you also cross-reference it with their open invoices? If this payment clears multiple smaller invoices, consolidate them. I need to make sure our accounts receivable accurately reflects their current balance for the end-of-month close.
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 received a $7,500 payment from Beta Solutions, but it doesn't match any single open invoice,…+
I just got a payment from a client, but the amount doesn't match any single open invoice, and there's no reference number.
I received a $7,500 payment from Beta Solutions, but it doesn't match any single open invoice, and the client didn't provide an invoice number. If I just apply it to the oldest outstanding balance, it might not be what they intended, and we could end up with an incorrect ledger. How should I best record this payment, or what's my first step to clarify its purpose without delaying the ledger update?
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 situations where incoming payments don't have clear invoice references or…+
I frequently spend too much time manually reconciling payments that don't clearly match invoices.
I keep running into situations where incoming payments don't have clear invoice references or don't match exact invoice amounts. This means I spend hours every week manually investigating and reconciling, which delays ledger updates and causes friction with the finance team. What habit can I adopt to streamline this process, perhaps by prompting clients for better details, or by flagging ambiguous payments earlier?
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 Apache Cassandra'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.