◆ Elasticsearch

Install Elasticsearch

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 taskGet the search engine up and running on the dev server by Friday afternoon. Make sure it's…+
Get the search engine up and running on the dev server by Friday afternoon. Make sure it's stable enough for us to start testing our new search queries against it.
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 we push our search engine to production, I need to ensure it's configured for optimal…+
Before we push our search engine to production, I need to ensure it's configured for optimal performance. Review the default settings for indexing, memory allocation, and shard distribution, and suggest changes that will prevent bottlenecks under heavy load, especially during peak user traffic.
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 Elasticsearch cluster just went red again, and I'm not sure why. We created a new index for…+
The Elasticsearch cluster just went red for the third time this week, right after a new index was created.
The Elasticsearch cluster just went red again, and I'm not sure why. We created a new index for the product catalog, and now nodes are dropping. I'm afraid of data loss, but I can't tell if it's a resource issue or a mapping problem. What's the most likely cause, and what's the first thing I should check to stabilize it without losing any data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep having to manually re-index data every few weeks because of inconsistent mapping types…+
We keep having to manually re-index data because of inconsistent mapping types.
We keep having to manually re-index data every few weeks because of inconsistent mapping types in our data storage. It's eating up dev time and causing delays in feature releases. What habit should I change in our index creation process to ensure consistent and correct mappings from the start, preventing these painful re-indexes?
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 Elasticsearch'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.