AGENTS.md

AGENTS.md

Rules for AI agents working in this repository (rafaelapb.github.io). These rules take precedence over any other instructions.

1. Keep source private

  • Treat all source files in this repository as private. Do not copy, quote, export, upload, paste into external tools, or otherwise expose them outside this workspace.
  • Do not create copies, mirrors, backups, or “helpful” exports of site sources (HTML, SCSS, posts, layouts, includes, data) anywhere outside the repo.
  • Nothing from this repository should be shared with third-party services unless it is part of the normal, verified publish flow (see §2).

2. Only what is needed for the Docker image / Jekyll site may be exposed

The only permissible exposure is what the build/publish pipeline strictly requires:

  • Docker image: contents included via Dockerfile / docker-compose.yml and not excluded by .dockerignore (e.g., Gemfile, Gemfile.lock, site sources needed at build time).
  • Jekyll website publishing: content that ends up in _site/ (and docs/, if published via GitHub Pages).
  • Anything else (drafts in _posts/_to_publish/, plans in docs/plans/, scratch files in tmp/, private notes) must not be added to the image or the published site.
  • Before changing Dockerfile, docker-compose.yml, .dockerignore, or _config.yml (include: / exclude:), verify that the change does not pull in private or unpublished material.

3. NEVER push

  • Do not run git push, ggpush, git remote update, or any variant that contacts a remote. Local commits are allowed; pushing is not, under any circumstances, unless the user explicitly asks in their own words in that moment.
  • Do not create remotes, do not run scripts that push, and do not set up automation (cron, CI, hooks) that pushes.
  • When unsure whether a command touches the network via git, do not run it.

4. Do not touch .env

  • Never read, open, display, move, rename, edit, create, delete, or commit .env files (including .env.local, .env.*, secrets, tokens, API keys).
  • Do not print environment variables that may contain secrets.
  • Do not add .env files to the Docker image or any build context.
  • If a task seems to require a value from .env, stop and ask the user instead.