Github se acaba de f0llar al vibe coding
Acaba de publicar spec-kit y en pocos días tiene 95k estrellas y 8.3k forks
Esto no es un proyecto cualquiera. Es GitHub diciéndote cómo se programa con IA de verdad.
El problema con los agentes de IA no es el modelo
Es que le mandas una idea en texto y él interpreta lo que quiere
Spec-kit resuelve eso con 6 comandos que convierten tu idea en una especificación estructurada antes de escribir una sola línea de código
✅ /speckit.constitution → las reglas del proyecto: calidad, testing, arquitectura
✅ /speckit.specify → describes QUÉ construir, no el stack
✅ /speckit.clarify → el agente pregunta lo que no entiende antes de empezar
✅ /speckit.plan → ahora sí eliges la tecnología
✅ /speckit.tasks → lista de tareas ordenada por dependencias
✅ /speckit.implement → el agente construye
El entregable ya no es código generado a lo loco
Es una especificación viva que tu IA lee, valida y ejecuta paso a paso
Funciona con Claude Code, Cursor, Copilot, Codex, Gemini CLI y más de 25 agentes
La diferencia real es esta
Antes: "hazme una app de tareas" y rezas para que el agente no se pierda a mitad
Ahora: especificación primero, código después
El agente sabe exactamente qué construir, en qué orden y por qué
95k estrellas. 8.3k forks. Publicado por el propio GitHub. Licencia MIT.
el repo aquí 👇
A single 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 file just hit #1 on GitHub trending 🤯
It fixes LLMs' worst coding habits using 4 principles from Karpathy:
Karpathy called LLMs out for making wrong assumptions silently. They overcomplicate everything. They edit code they were never asked to change. No pushback. No clarifying questions. They just run.
So those observations were encoded into 4 behavioral constraints:
→ Think before coding. If something’s ambiguous, ask. Don’t pick one interpretation and run. Surface tradeoffs, stop when confused.
→ Simplicity first. Write the minimum code that solves the problem. No speculative abstractions, no flexibility nobody asked for.
→ Surgical changes. Only touch what the task requires. Don’t improve neighboring code, don’t refactor what isn’t broken.
→ Goal-driven execution. Turn vague instructions into verifiable targets before writing a line. “Add validation” becomes “write tests for invalid inputs, then make them pass.”
It works immediately.
Drop the file in your project root and Claude Code follows it from the first task.
One file. Zero dependencies. No setup.
And best part, 100% open source.
UN SOLO ARCHIVO CLAUDE. md ACABA DE ALCANZAR EL #1 EN TENDENCIAS DE GITHUB.
82,100 estrellas. 7.8k forks. cero dependencias.
Guarda esto en favoritos antes de que se te olvide. Y tu Claude empezará a funcionar de manera diferente.
4 principios. un archivo. Hábitos de codificación LLM de Karpathy. destilados.
> piensa antes de codificar.
> simplicidad primero.
> solo ediciones quirúrgicas.
> objetivos dirigidos por metas antes de empezar.
Intercámbialo en tu CLAUDE. md hoy.
tu Código Claude se convierte en una herramienta diferente.
Léelo hoy. Enlace abajo.
Claude → Habilidades → CLAUDE. md → Código Mejor → Sistemas Mejores → Dinero
ANTHROPIC JUST PROVED MOST PEOPLE HAVE NO IDEA HOW TO PROMPT CLAUDE.
Their applied AI team dropped a 24 minute free workshop.
Not a creator who reverse engineered it.
Not a Reddit thread.
ANTHROPIC.
The people who wrote the weights.
And what they showed is uncomfortable.
There are 6 elements to a properly structured Claude prompt.
Most people are using 1.
Maybe 2.
That is not a skill issue.
That is an information issue.
And it has been quietly costing you every single day.
The outputs that felt slightly off.
The responses you had to rewrite 4 times.
The prompts that worked once and never again.
All of it traces back to the same 6 missing elements.
The people who watch this 24 minute workshop tonight will understand something about Claude that most daily users still do not know exists.
The people who skip it will keep getting 30% of what the tool is actually capable of and wonder why the results never quite land.
I watched it twice.
Then I built a Claude Skill that applies all 6 elements to every prompt automatically.
No more thinking about structure.
No more guessing what Claude needs.
The framework runs in the background every single time.
Full breakdown and skill setup is below.
Bookmark this now.
Watch the workshop first.
Then read the guide.
This is the one that compounds.
Follow @cyrilXBT for the exact prompt architecture, Claude skills, and systems I use to get outputs most people do not believe came from one person working alone.
This WW2 bunker used a fake air vent to return grenade to sender. Warfare during World War II became more gruesome due to remarkable technological advances. However, in Normandy, bunker builders employed a deadly trick through misdirection. They designed a hole, cleverly disguised as an air vent, enticing advancing enemies to toss a grenade. Yet, to their dismay, the explosive simply dropped through a small pipe, landing at the assailant's feet. Imagine the fear coursing through their minds during those harrowing 2 seconds before the explosion.
Juegos + Música = 💚
Gana este reproductor de casetes inspirado en Xbox Series S y 3 meses de suscripción a #GamePassUltimate. Para participar tienes que retwittear este post antes del 27/12/2022, ser residente en España y mayor de 18 años 🎵
"Me trajo una hoja a cambio de una de mis brochetas de barbacoa, ella vio como la gente compraba mis brochetas y quiso hacer lo mismo, vean su carita, no se de donde saco la hoja. Tan sólo miren sus ojos."