Repository navigation
chore(templates): add llms.txt docs banner to generated starters - #1295
Merged
Merged
Conversation
Point AI agents to https://www.builderbot.app/llms.txt in the first lines of every generated src/app.{js,ts}, then regenerate starters/apps.
Pin the docs banner in the template sources and in every generated starters/apps entrypoint. generate:check only catches drift between the template and starters/apps, so it stays green when the banner disappears from both sides.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Que tipo de Pull Request es?
Descripción
Los proyectos que genera
create-builderbotahora abren su entrypoint (src/app.js/src/app.ts) con un comentario de 5 líneas que apunta a https://www.builderbot.app/llms.txt y le pide a un agente de IA leer esa documentación antes de responder o modificar el proyecto (API actual, patrones de uso, soluciones y buenas prácticas).El banner vive en la fuente del generador y se propaga solo:
starters/apps/**es generado, nunca editado a mano.Cambios
scripts/generate/template/js/src/app.jsscripts/generate/template/ts/src/app.tsstarters/apps/*/src/app.{js,ts}pnpm run generate.templates: 181 archivos, +5 líneas cada unopackages/cli/_test_/starters-banner.test.tsVerificación ejecutada
pnpm run generate.templates(2 corridas)git statuslimpio → idempotente y byte-idéntico a lo commiteadopnpm run generate:check✔ starters/apps is in sync with scripts/generate.starters/apps/base-ts-tiktok-json/src/app.ts, el test falla nombrando ese starterpnpm --filter @builderbot/cli test→ 16/16 (3 casos nuevos)pnpm test→ passed (30 proyectos)Notas
git show --unified=0).tiktok,voice-whatsapp,meta-voice-ai× JS/TS) pasan por la rama del generador que eliminaimport { join } from 'path'; el banner sobrevive y los imports arrancan en la línea 6.generate:checksolo detecta drift template → starters, así que el test nuevo cubre el caso que ese guard no ve: el banner borrado de ambos lados a la vez.type:*disponibles; no agrego label.