Saltar al contenido principal

Vibe Coding

Definición

Vibe codificación es un estilo de desarrollo de software donde trabajas iterativamente con asistencia de IA: se describe la intención en lenguaje natural, get code or edits from an LLM or codificación tool, then refine by feedback and context rather than writing every line from scratch. The “vibe” is the loose, exploratory flow—you steer by intent and feel, and the model fills in implementation details.

It contrasts with fully spec-first or plan-then-code approaches (por ej. spec-driven development): you often start with a rough idea and let prompt engineering, agents, and tools (por ej. Cursor, Claude Code) suggest and edit code. Useful for prototypes, scripting, and tasks where speed and iteration matter more than upfront diseño.

Cómo funciona

You give the model (or IDE tool) context: open files, cursor position, or a short prompt (“add a test for this”, “refactor to use async”). The model returns suggested code or diffs; you accept, edit, or reject and optionally add feedback (“use a different library”, “make it shorter”). The loop repeats until the result igualares what you want. Tools often provide project-aware context (indexed codebase, RAG-style recuperación) so suggestions stay relevant. Success depends on clear intent, good tooling, and knowing when to take over or refine the output.

Casos de uso

Vibe codificación encaja cuando quieres avanzar rápido con asistencia de IA y estás de acuerdo con iterar en el bucle en lugar de definir la especificación primero.

  • Prototyping and scripting (por ej. one-off scripts, small tools)
  • Boilerplate, tests, and refactors where the intent is easy to state
  • Learning or exploring a codebase by asking the AI to implement or explain
  • Combinación con agentes o agentes autónomos que escriben y editan código a partir de descriptions

Ventajas y desventajas

ProsCons
Fast iteration and less typingCan obscure understanding if you never read the code
Good for exploration and learningMay produce brittle or overfitted code without review
Low friction for small tasksHard to scale to large, consistent systems without specs
Works well with agents and IDEsDepends on model quality and context

Documentación externa

Ver también