Dorian Rodríguez

Director | Writer | DigitalMKT & SocialMedia Strategist | Brand Specialist | Marketing, Digital PR, Talent & Artist Relations

[Dorian Rodríguez @DorianRdrgz]

No tenemos que derrumbar nuestros sueños, hay que derrumbar las barreras que nos impiden cumplirlos...

[Ignacio Arsuaga @iarsuaga]

Hay gente que abre el ordenador y se pone a crear cosas así. Qué maravilla.

[darkPulse @darkpulsek]

😂The Most harmless prank 😂

[𝕚𝕝𝕠𝕧𝕖𝕪𝕠𝕦𝕞𝕒𝕚 @HopeBeatles]

Métanlo a la granja dicen jajajajajaj esos si son amigos 😂
Toño de Valdés y el otro comentarista que no me sé su nombre 🤭
Voten x Memo para que estos peligrosos no lo vean hasta febrero, háganles paro.
#LaCasaDeLosFamososMx #TropaSchutz

[eugi @jamoncitocrudo]

te borran la memoria pero podes ver este video por primera vez JAJAJA extraño a los miranda en ndn!!! cuando van?

[kocer @kocer_eth]

xAI EMPLOYEES LEFT 50 GROK BOT PROMPTS ACROSS A 72-HOUR BUILD AND PUBLIC GUIDES. COPY THEM IN THIS ORDER.

at 11:40 p.m., i nearly saved the viral list and moved on.

it had 30 prompts attributed to Lauren Tan, Matt Palmer, and Roshan Sadanani during their 72-hour xAI company build.

then i opened Lauren's public pstack guides and found the missing engineering layer.

i adapted all 50 into one paste-ready sequence and kept the source beside every prompt.

source key: [RS] Roshan, [MP] Matt, [LT] Lauren, [pstack] Lauren's public pstack guides.

find the market

› 01. [RS] mine public posts for agent problems. rank each by buyer clarity, willingness to pay, and speed to launch.

› 02. [RS] analyze customer conversations from the last 48 hours. extract repeated pain, urgency, budget signals, and named buyers.

› 03. [RS] compress the research into one thesis: customer, painful problem, wedge product, and why it must exist now.

› 04. [RS] define who pays, the first job to be done, and the fastest internal test of the product thesis.

› 05. [RS] map the two strongest segments by ICP, pain, offer, price range, and five Day 1 interview questions.

› 06. [RS] design outreach and onboarding for the first design partner. include the inputs needed to define measurable success.

› 07. [MP] find and rank 25 potential customers. identify the best contact path and flag feasibility or integration risks.

› 08. [MP] generate 15 company names. score the best five by domain, email format, memorability, and product fit.

› 09. [MP] find the fastest path from our current assets to the first $1. define the offer, price, buyer, and payment method.

› 10. [RS] find the smallest MVP we can presell. list what must be real before payment and what can wait.

design the company

› 11. [LT] ask me five questions about the company. then design the first three specialist bots with memory, skills, and initial tasks.

› 12. [LT] turn one general bot into a Chief of Staff. it should triage Slack and interrupt me only for money or product decisions.

› 13. [LT] turn this generic bot into a specialist. define its role, tone, tools, workflow, escalation rule, and success metric.

› 14. [MP] assume zero employees and 72 hours. design the smallest bot team for research, product, engineering, growth, and operations.

› 15. [MP] turn Slack into the control plane. create channels for product, engineering, bots, prospects, and customer signups.

› 16. [MP] create Operations and Creative Director bots. give each one routine, one metric, and one human escalation rule.

› 17. [LT] audit marketplace bots for research, outbound, inbox, engineering, and design. keep only bots that remove friction.

› 18. [RS] divide the next 24 hours across three humans and their bots. assign one owner and one definition of done per workstream.

› 19. [MP] write a five-line shipping policy for humans and bots. cover speed, direct deployment, rollback, ownership, and review.

› 20. [RS] create a Designer bot that delivers a company name, three logo directions, and a landing-page hero within 60 minutes.

build and ship

› 21. [LT] install an engineering skill pack for tests, PR hygiene, and issue-to-ship loops. remove anything unnecessary for Day 3.

› 22. [LT] create a Prototype Engineer that ships a landing page with email signup today. use no database unless it is essential.

› 23. [LT] use Grok Bot for research and disposable prototypes. define the exact handoff package for production engineering.

› 24. [LT] create an Engineer bot that owns the repository, ships small changes, writes minimal tests, and avoids bikeshedding.

› 25. [LT] create the full visual direction: brand voice, hero copy, CTAs, colors, typography, and an implementation-ready brief.

› 26. [LT] design the thinnest stack that can accept payment by Day 3. separate what must be built from what can be simulated.

› 27. [MP] name the company around its shipping deadline. create the GitHub organization and write the first product README.

› 28. [MP] connect the signup form to Notion. define the database fields, follow-up workflow, and confirmation message.

› 29. [MP] connect the repository to Vercel. document the path from first preview to production and custom domain.

› 30. [RS] map the path from waitlist to first paid customer to subscription. track daily signups, calls, sales, and revenue.

understand and plan

› 31. [pstack] read this Slack thread. restate the underlying issue in plain English before proposing any solution.

› 32. [pstack] trace how <feature> works at runtime. show the entry point, data flow, state changes, dependencies, and failure paths.

› 33. [pstack] explain why we still use <old dependency>. check Git history, PRs, tickets, docs, Slack, and production evidence.

› 34. [pstack] teach me why you implemented it this way. compare the strongest alternative and explain every tradeoff.

› 35. [pstack] recall yesterday's work on <system>. combine that context with this new bug report before taking action.

› 36. [pstack] recall seven days of related work. explain the current design, identify repeated failures, and propose a replacement.

› 37. [pstack] prototype three options for <feature>. keep them disposable and compare them with measured evidence.

› 38. [pstack] build two UI variants behind a switcher. use /control-app to record each flow and capture review screenshots.

› 39. [pstack] /architect <feature> before implementation. surface open questions and answer them with small prototypes.

› 40. [pstack] turn the approved design into a multi-phase plan. keep every PR small and attach proof to every completed task.

verify and improve

› 41. [pstack] investigate why background workers time out. separate facts, evidence, unknowns, and ranked hypotheses.

› 42. [pstack] architect rate limiting for external webhooks. test open questions with prototypes and wait for my review.

› 43. [pstack] plan the StyleX migration as small, verifiable PRs. require visual regression tests and live checks for each PR.

› 44. [pstack] reproduce this bug with /control-app. if it exists on main, fix it and return a video showing the working result.

› 45. [pstack] use /poteto-mode to build <feature>. verify it with /control-app and return screenshots plus a short video.

› 46. [pstack] spawn a cloud agent to build <feature> with /poteto-mode. require /control-app evidence before reporting completion.

› 47. [pstack] improve initial load time. capture a baseline trace, make one targeted fix, then use a swarm to confirm the win.

› 48. [pstack] evaluate this skill change. run old and new versions on the same tasks, compare failures, and show the evidence.

› 49. [pstack] run /create-verification-skill for this app. build a compact control CLI and a searchable feature map.

› 50. [pstack] run /maintain-verification-skill daily. update stale commands, feature paths, and known verification failures.

the useful part is not any single prompt.

each output becomes the next prompt's context: market becomes offer, offer becomes product, product becomes evidence.

that is when Grok Bot stops producing isolated answers and starts carrying a company build forward.

bookmark the sequence. the order is the asset.

[جابر 🇦🇪 @Jrb35r5]

شاف نجوم الظهر
🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣

[El Ranchero Loco ® @EIRancheroLoco]

El que hizo ésta broma no tiene perdón de Dios. 😂😂😂

[Dorian Rodríguez @DorianRdrgz]

@Apollo_MZ Nada mal, opinaría yo… 👏👏🔥🔥

[Dorian Rodríguez @DorianRdrgz]

@_CFCWhizz @grok It’s real, this is the Monterrey’s stadium 🏟️.

[Dorian Rodríguez @DorianRdrgz]

@deprimeramano Haha con esos nombres (lapizín, lapizito, gomita) y esa voz, es imposible tomar en serio esta nota haha 😂

[Sabiduría Eterna. @LealtadSabia]

25 HÁBITOS ABURRIDOS QUE TE HARÁN INRECOCIBIBLE PARA JULIO:

1. Bebe agua antes del café. Tu cuerpo ha estado en ayuno durante 8 horas.

[Kaynak Haber @KaynakNews]

Japonya'da yağmurlu havalarda kedilerin korunması için yapılan mini barınaklar.

[𝕐o̴g̴ @Yoda4ever]

They're probably talking something important..🐈🐈🐈🐈😅

[Vive con Propósito. @PropositoyVida]

Esta gata callejera, a la que alimentaban casi todos los días, da a luz a su único gatito y pide amablemente que lo adopten🥹♥️

[The Cats 𝕏 @TheCatsX]

"do you have games in your laptop?" 🥹

[🎼🌺Music Love♥️ @ThoNg676733]

The shock experienced by people whose photos were edited to make it look like they were friends with a criminal 😂What a funny prank 😂

[Mateo T Grow 💲 @MTOgrow]

Trucos útiles en Claude

[Alerta News 24 @AlertaNews24]

🇮🇪 | 114 años después, Belfast presencia la partida del Titanic en la noche, recreada con drones a escala real.

[Raúl | Productividad & IA @Raul_IA_Prod]

🚨 ÚLTIMA HORA: Claude ahora puede crear toda tu app móvil a partir de una captura de pantalla, como un desarrollador senior de Apple de $350K (gratis)

Aquí tienes 8 prompts increíbles de Claude que reemplazan a todo tu equipo de desarrollo móvil antes de que terminen de estimar el costo del proyecto: 👇

(Guarda este hilo 🔖 antes de que se vuelva viral)