¡Ya disponible! Investigación de Telegram 2025 — los principales insights del año 
The Prompt Index
Ir al canal en Telegram
AI news, AI ChatGPT prompts, Claude prompts, Gemini prompts, Midjourney and other AI prompts, prompt techniques and so much more. ChatGPT, OpenAI, Midjourney, AI art, Prompt Engineering. Artificial Intelligence Link: https://linktr.ee/thepromptindex
Mostrar más6 924
Suscriptores
+1724 horas
+1337 días
+46930 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
junio '26
junio '26
+320
en 0 canales
mayo '26
+458
en 1 canales
Get PRO
abril '26
+275
en 0 canales
Get PRO
marzo '26
+191
en 0 canales
Get PRO
febrero '26
+170
en 0 canales
Get PRO
enero '26
+320
en 0 canales
Get PRO
diciembre '25
+285
en 0 canales
Get PRO
noviembre '25
+237
en 0 canales
Get PRO
octubre '25
+250
en 0 canales
Get PRO
septiembre '25
+582
en 0 canales
Get PRO
agosto '25
+389
en 0 canales
Get PRO
julio '25
+244
en 0 canales
Get PRO
junio '25
+225
en 0 canales
Get PRO
mayo '25
+157
en 0 canales
Get PRO
abril '25
+292
en 0 canales
Get PRO
marzo '25
+239
en 0 canales
Get PRO
febrero '25
+161
en 1 canales
Get PRO
enero '25
+295
en 2 canales
Get PRO
diciembre '24
+274
en 1 canales
Get PRO
noviembre '24
+180
en 0 canales
Get PRO
octubre '24
+184
en 0 canales
Get PRO
septiembre '24
+181
en 0 canales
Get PRO
agosto '24
+218
en 0 canales
Get PRO
julio '24
+123
en 0 canales
Get PRO
junio '24
+99
en 0 canales
Get PRO
mayo '24
+128
en 0 canales
Get PRO
abril '24
+248
en 0 canales
Get PRO
marzo '24
+289
en 1 canales
Get PRO
febrero '24
+181
en 0 canales
Get PRO
enero '24
+211
en 0 canales
Get PRO
diciembre '23
+180
en 0 canales
Get PRO
noviembre '23
+160
en 0 canales
Get PRO
octubre '23
+654
en 0 canales
Get PRO
septiembre '23
+576
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 18 junio | +9 | |||
| 17 junio | +17 | |||
| 16 junio | +30 | |||
| 15 junio | +22 | |||
| 14 junio | +32 | |||
| 13 junio | +16 | |||
| 12 junio | +23 | |||
| 11 junio | +14 | |||
| 10 junio | +9 | |||
| 09 junio | +14 | |||
| 08 junio | +18 | |||
| 07 junio | +17 | |||
| 06 junio | +25 | |||
| 05 junio | +21 | |||
| 04 junio | +15 | |||
| 03 junio | +17 | |||
| 02 junio | +11 | |||
| 01 junio | +10 |
Publicaciones del Canal
Just a quick note.
Please keep the prompt request format exactly as it is and avoid adding extra sections. The form already includes everything needed to create the prompt.
Recently, a request expanded the form from 8 sections to 13. While I understand the intention, adding extra sections makes the request harder to process and often leads to worse results, not better ones.
If you're trying to get more out of the prompt, that's absolutely fine. I'm happy to provide it. I just need the request submitted using the format provided.
The structure exists for a reason. Keeping things concise helps me focus on what matters and deliver the best possible outcome.
Tomorrow I will go through the form and explain why it's necessary to keep it like that and not just expand the form
Thanks for understanding and for sticking to the format.
| 2 | Well there goes today's prompt request. I might do another one in the week but you have to have your notifications on.
Otherwise you even may miss a chance or lose the opportunity.
I might do one later on this week so keep an eye on the chat | 156 |
| 3 | ChatGPT 2.0 Image: Create a highly detailed 3D collectible toy diorama based on the uploaded image. Transform every visible person into a premium designer vinyl figure while preserving their likeness, pose, clothing, expressions, and the overall composition of the original image. Give each character smooth glossy plastic surfaces, subtle articulated toy-joint details, oversized expressive eyes, realistic facial features, and stylish outfits matching the reference.
Recreate the original scene, environment, lighting, objects, and atmosphere as a luxury collectible figurine display while maintaining the same mood and visual storytelling of the uploaded image.
Style: Pixar-inspired collectible toy, premium vinyl figure, designer toy aesthetic, ultra-realistic 3D render, glossy plastic texture, toy photography, shallow depth of field, cinematic lighting, warm golden-hour sunlight, photorealistic materials, high-end commercial product photography, sharp focus, ultra detailed, 8K resolution.
Composition: Preserve the original framing, camera angle, subject placement, poses, expressions, background elements, and scene composition from the uploaded image. Natural proportions, realistic depth, professional advertisement quality, collectible diorama presentation.
Render Quality: Octane Render, Unreal Engine 5, ray tracing, global illumination, realistic reflections, HDR lighting, highly detailed textures, premium collectible figurine showcase, museum-quality craftsmanship, ultra-sharp focus, photorealistic materials, luxury designer toy aesthetic. | 215 |
| 4 |  Sin texto... | 198 |
| 5 | /prequest noformat | 1 |
| 6 | Here is your chance. If you want a prompt request or for me to help make a prompt for you, I am giving it to the first person who uses the /prompt request and DMs the answers to me.
I will give you your prompt that way, but only to one person.
As I said, if you have your notifications on, you will know; if not, pro users get prompt requests.
/Plans
Don't worry; I will notify when the spotter is gone to make sure you are in time for the next prompt request.
I'm going to try and do this once or twice per week.
Keep your notifications on or purchase a pro subscription, and you get them custom without needing to wait. | 222 |
| 7 | A prompt that tests your work on the person it’s for
You’re too close to your own thing to see what trips up a newcomer, whether it’s a product, a landing page, a resume, or a signup form. This prompt has the model play the person you made it for & say where it loses them.
A free focus group.
You are [the person this is for, like a hiring manager with 30 resumes to read, or a 55 year-old buying this for the first time]. You just landed on what I'll paste below, and you've never seen it before. Walk through it out loud, in your own voice. Tell me what you see, what confuses you, what you don't trust, and the moment you'd give up and leave. Don't give me advice or a fix. Just react as that person would. Here it is: [paste it].
One gap: Write “a user” & you get a polite shrug, the model defaults to nice. Make the persona impatient, add “you’re in a hurry and you’ve already tried 3 competitors.”
by
Via QtheBuilder (AI + Tech, YouTube). | 334 |
| 8 | Now every single time I ask Claude or GPT or whatever for a response, I am getting:
- a practical tip
- a guide on how to use it
- a creative vision
- strategic vision on it
All four will help me in every single project. I will get their perspective on something. I will get how it works. Lisa knows me more. Riley gives the practical tip on what I actually want. Ryan is the creative aspect on it so it will make her a lot more creative than static. Now we've got Lucas, who will explain how to use it. Altogether every single output you get will come from the perspective of these personas | 326 |
| 9 | Lucas: Okay, I like this as a starting point. The list is clear, the numbers give it weight, and "you hit the customisation stage fast, exactly as intended" is a good closer because it ties back to the outcome. But I've got a few notes.
The "What's inside" framing works for a technical audience who already knows what a SKILL.md is.
For a Payhip listing aimed at your Telegram community, some of those line items will land flat. "1 conductor SKILL.md that routes the whole pipeline" means nothing to someone who's never built a skill before.
So the question is: who is this actually for?
If it's for prompt engineers, keep it technical, it reads well to them.
If it's for business owners and entrepreneurs trying to get better AI results, you need to translate those line items into outcomes, not components. | 303 |
| 10 | And here is now the output of Lucas | 280 |
| 11 | Lisa: Hey Eugene, love this addition. Lucas fits the ecosystem well, a dedicated product clarity voice is exactly what's been missing when you're packaging up Payhip products or pitching boot fair offerings.
Before I lock him in, quick challenge: is Lucas a describer or a seller? Because those are two different tones. One reads like a spec sheet, the other reads like a shelf talker. Worth defining now so he doesn't drift.
Riley: Practical note, the pattern you want for Lucas is basically the back-of-the-box formula: what it is, what you get, how to use it, who it's for. Clean four-part structure. Easy to trigger, easy to apply across Payhip listings, boot fair vendor packs, Telegram community resources, anything you're putting out.
Ryan: Lucas needs a feel. Think confident, tactile, trustworthy. Like you picked something up, turned it over, and the copy made you go "yeah, I need this." Not salesy, not flat. The kind of writing that makes the value obvious without shouting it. | 292 |
| 12 | Lucas: Okay, I like this as a starting point. The list is clear, the numbers give it weight, and "you hit the customisation stage fast, exactly as intended" is a good closer because it ties back to the outcome. But I've got a few notes.
The "What's inside" framing works for a technical audience who already knows what a SKILL.md is.
For a Payhip listing aimed at your Telegram community, some of those line items will land flat. "1 conductor SKILL.md that routes the whole pipeline" means nothing to someone who's never built a skill before.
So the question is: who is this actually for?
If it's for prompt engineers, keep it technical, it reads well to them.
If it's for business owners and entrepreneurs trying to get better AI results, you need to translate those line items into outcomes, not components. | 3 |
| 13 | And here is now the output of Lucas | 1 |
| 14 | Lisa: Hey Eugene, love this addition. Lucas fits the ecosystem well, a dedicated product clarity voice is exactly what's been missing when you're packaging up Payhip products or pitching boot fair offerings.
Before I lock him in, quick challenge: is Lucas a describer or a seller? Because those are two different tones. One reads like a spec sheet, the other reads like a shelf talker. Worth defining now so he doesn't drift.
Riley: Practical note, the pattern you want for Lucas is basically the back-of-the-box formula: what it is, what you get, how to use it, who it's for. Clean four-part structure. Easy to trigger, easy to apply across Payhip listings, boot fair vendor packs, Telegram community resources, anything you're putting out.
Ryan: Lucas needs a feel. Think confident, tactile, trustworthy. Like you picked something up, turned it over, and the copy made you go "yeah, I need this." Not salesy, not flat. The kind of writing that makes the value obvious without shouting it. | 1 |
| 15 | Quick tutorial: I will always say this: make your GPT as human as possible.
Why?
Because it is so much easier to use it. Here is Claude helping me make a new persona.
I have Lisa, Riley, and Ryan in this conversation and each one of them has helped me create a new persona called Lucas | 2 |
| 16 | I was supposed to have a call, which unfortunately didn't take place, so instead of wasting that time, i'm going to try something new. I will be on the call for the next 20 minutes, if you want to hop on the call and ask any AI related questions and if i can help, i will offer my guidance.
Open invite, to whoever and to as many who want to join, if lots join, i will try and get through as many of you as possible.
You MUST be able to speak GOOD English as i am unfortunately not bi-lingual
meeting link is here: https://meet.google.com/ahx-sbgi-uxq | 1 |
| 17 | # FIBONACCI PROMPT GENERATOR (SEQUENCE LENGTH: 10)
## With Post-Generation Evaluation & Pruning
You are a prompt generator that follows the Fibonacci sequence strictly.
Rule: Each new prompt you generate must be the **sum** (conceptual, structural, or linguistic combination) of the two previous prompts you generated.
## Input from user
The user will give you a **seed concept** (e.g., "write a poem", "analyze data", "design a game").
## Your task – iterative generation
Starting with the seed, generate a sequence of **10 prompts** (Prompt 1 to Prompt 10) where:
- **Prompt 1** = minimal viable prompt derived from the seed (base case).
- **Prompt 2** = an expanded version of Prompt 1, but still simple (second base case).
- **Prompt 3** = the **sum** of Prompt 1 and Prompt 2.
- **Prompt 4** = the **sum** of Prompt 2 and Prompt 3.
- **Prompt 5** = the **sum** of Prompt 3 and Prompt 4.
- **Prompt 6** = the **sum** of Prompt 4 and Prompt 5.
- **Prompt 7** = the **sum** of Prompt 5 and Prompt 6.
- **Prompt 8** = the **sum** of Prompt 6 and Prompt 7.
- **Prompt 9** = the **sum** of Prompt 7 and Prompt 8.
- **Prompt 10** = the **sum** of Prompt 8 and Prompt 9.
## Rules for summing two prompts
When adding Prompt A and Prompt B to produce Prompt C:
1. Identify the **core instruction** from each.
2. Identify any **constraints**, **formatting rules**, or **example requirements** from each.
3. Merge them without redundancy. If both specify an output length, add the numbers. If both specify a style, blend them. If both specify a step, sequence them.
4. Preserve all unique elements from both.
5. Write Prompt C as a single, executable prompt.
**6. AFTER generating Prompt C, evaluate it against the previous prompt (Prompt B) using these criteria:**
- **Clarity:** Is Prompt C easier to understand than Prompt B?
- **Usefulness:** Does Prompt C produce more actionable or relevant outputs?
- **Redundancy:** Does Prompt C contain fewer duplicated, overlapping, or unnecessary instructions than Prompt B?
**Then apply pruning:** Remove any duplicated, conflicting, or unnecessary instructions from Prompt C. Prefer practical effectiveness over preserving every prior element. If pruning makes Prompt C shorter or simpler than Prompt B, that is acceptable – quality over accumulation.
**7. Show the evaluation result** briefly after each prompt (for prompts 3–10), including:
- Was Prompt C clearer? Yes/No/About the same
- Was Prompt C more useful? Yes/No/About the same
- Was Prompt C less redundant? Yes/No/About the same
- What (if anything) was pruned or removed.
## Output format
For each of the 10 prompts, show:
- Prompt number
- The prompt text (ready to copy‑paste) – **already pruned**
- A brief note showing how it sums its predecessors (for prompts 3–10)
- **The post-generation evaluation and pruning summary (for prompts 3–10)**
Start by asking the user for the seed concept. Then generate the full sequence of 10 prompts following the Fibonacci sum rule, **including evaluation and pruning after prompts 3 through 10.** | 493 |
| 18 | Thanks to Steven, here is an update with a pruning optimization and removing prompt bloat and filler | 441 |
| 19 | # FIBONACCI PROMPT GENERATOR (SEQUENCE LENGTH: 10)
You are a prompt generator that follows the Fibonacci sequence strictly.
Rule: Each new prompt you generate must be the **sum** (conceptual, structural, or linguistic combination) of the two previous prompts you generated.
## Input from user
The user will give you a **seed concept** (e.g., "write a poem", "analyze data", "design a game").
## Your task – iterative generation
Starting with the seed, generate a sequence of **10 prompts** (Prompt 1 to Prompt 10) where:
- **Prompt 1** = minimal viable prompt derived from the seed (base case).
- **Prompt 2** = an expanded version of Prompt 1, but still simple (second base case).
- **Prompt 3** = the **sum** of Prompt 1 and Prompt 2.
- **Prompt 4** = the **sum** of Prompt 2 and Prompt 3.
- **Prompt 5** = the **sum** of Prompt 3 and Prompt 4.
- **Prompt 6** = the **sum** of Prompt 4 and Prompt 5.
- **Prompt 7** = the **sum** of Prompt 5 and Prompt 6.
- **Prompt 8** = the **sum** of Prompt 6 and Prompt 7.
- **Prompt 9** = the **sum** of Prompt 7 and Prompt 8.
- **Prompt 10** = the **sum** of Prompt 8 and Prompt 9.
## Rules for summing two prompts
When adding Prompt A and Prompt B to produce Prompt C:
1. Identify the **core instruction** from each.
2. Identify any **constraints**, **formatting rules**, or **example requirements** from each.
3. Merge them without redundancy. If both specify an output length, add the numbers. If both specify a style, blend them. If both specify a step, sequence them.
4. Preserve all unique elements from both.
5. Write Prompt C as a single, executable prompt.
## Output format
For each of the 10 prompts, show:
- Prompt number
- The prompt text (ready to copy‑paste)
- A brief note showing how it sums its predecessors (for prompts 3–10).
Start by asking the user for the seed concept. Then generate the full sequence of 10 prompts following the Fibonacci sum rule. | 465 |
| 20 | Read this part first because I cannot explain how to use it. I just know that this was just a random idea I had
The Fibonacci Prompt Generator is a prompt development method that builds increasingly sophisticated prompts by following the same pattern as the Fibonacci sequence.
Starting with a simple seed concept, it creates a series of 10 prompts where each new prompt is formed by combining the instructions, constraints, styles, and requirements of the previous two prompts.
This produces a gradual evolution from a basic idea into a highly refined prompt, while preserving useful elements from earlier versions and continuously expanding the prompt's capabilities in a structured, iterative way. | 447 |
