¿Puedo vibecodear Lex?

SÍ · se arma en una sentada

precio $12/mesahorrarías $144/añotiempo de build varios díascategoría ✍️ escritura con iareemplazada por 0 personas

The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Lex, write and revise long-form documents with comments, version history, and AI actions. The hard boundary is collaborative editor polish, sync, and embedded model access, plus workflow, data, and model tuning.

el prompt

Build a personal replacement for Lex in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and the OpenAI Responses API; do not offer alternative stacks.
The core loop is: take a brief, gather user-supplied source material, generate and revise a structured long-form draft with comments and AI actions, and keep citations and version history attached to each section.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Build a brief form with audience, objective, tone, source URLs, and prohibited claims.
Store imported source text locally and chunk it for retrieval with SQLite FTS5.
Generate an outline first and require approval before drafting sections.
Attach source references to generated paragraphs and flag unsupported claims.
Provide rewrite controls for shorten, clarify, change tone, and add evidence.
Export clean Markdown plus a JSON research bundle.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out live search-engine rank data.
Deliberately leave out automatic publishing to third-party CMSs.
Deliberately leave out multi-user approvals and brand governance.
Finish by running the tests and listing the exact commands used.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

Puedes vibecodearlo

Ahorro de referencia: US$144/año si dejas de pagar Lex.

Quiero que lo armen →

por qué la gente sigue pagando

People still pay for Lex because the subscription bundles a refined workflow, proprietary signals, templates, and predictable output quality for a team. The recurring cost buys prompt maintenance, retrieval quality, source handling, provider changes, and editorial QA, not just the visible interface.

qué pierdes

xpulido del editor colaborativo, sincronización y acceso a modelos integrados

xdatos de ranking propietarios

xmodelos entrenados con la marca

xflujos de trabajo en equipo

xamplias bibliotecas de plantillas

compartir en X ↗"Acabo de reemplazar Lex ($12/mes) con un prompt"

la salida

¿No quieres construirlo? Esta gente ya lo hizo gratis.

AppFlowyUn espacio de trabajo documental colaborativo local first con comentarios, historial e IA gratuita con Ollama; con forma de Notion, pero puede reemplazar a Lex.75kjul 2026open source↗

sin votos, sin pago por aparecer · solo lo que es real