mARTin-B78 910dd0456e Add Jules agent prompts and shared rules

Creates `AGENTS.md` with shared rules and environment setup block for Jules agents.
Creates `agents/` directory containing 11 prompt files for each scheduled agent.
Creates `.jules/` directory containing 11 initial journal files for the agents.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

2026-06-09 19:42:38 +00:00

1.8 KiB

Raw Blame History

Jules Agent Instructions

Environment / Verify

Before submitting changes, mirror the CI pipeline locally by running the following in a bash session:

sudo apt-get update && sudo apt-get install -y \
  python3-gi gir1.2-gtk-3.0 gir1.2-appindicator3-0.1 \
  libgirepository1.0-dev libcairo2-dev python3-dev
cd linux
pip install -r requirements.txt && pip install pytest ruff PyGObject
python -m py_compile blitztext/*.py     # syntax gate
PYTHONPATH=. pytest tests               # test gate
ruff check blitztext tests              # quality gate

Scope discipline

One concern, one small PR. No drive-by refactors (the repo's CONTRIBUTING says so explicitly).
If there's no clear, high-confidence win this run, STOP — don't open a PR.
Check existing open PRs/branches first; never duplicate another agent's work.
Never touch requirements.txt, pyrightconfig.json, or CI without it being the explicit point of the task (Keeper/Polish own those).
Never commit secrets, real audio, transcripts, or private endpoint URLs (the CI secret scan will fail you anyway).
Bump linux/blitztext/__init__.py + add a CHANGELOG.md entry for any user-visible change. SemVer: fix → patch, feature → minor.

Journal

Read .jules/<name>.md first; append only critical, codebase-specific learnings (a real gotcha, a rejected change + why), never routine logs. Format:

## YYYY-MM-DD — [Title]
**Learning:** …
**Action:** …

PR format

Use the following format for pull requests:

Title: "<emoji> <Name>: <one-line change>"
Body:
  💡 What  — the change
  🎯 Why   — the problem it solves
  ⚠️ Risk  — blast radius + how mitigated
  🔬 Verified — exact commands run (py_compile / pytest / ruff / build-deb)
  📎 Scope — files touched; confirm no unrelated changes