KNEL/ChatGPTScaffolding
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
Files
v0.0.0
ChatGPTScaffolding/meta/AGENTS.seed.llm.md

2.2 KiB
Raw Permalink Blame History

AGENTS (Seed, LLM)

  • One-way workflow: questions → proposal → plan → implement; no backsteps after approval.

  • Gates: human .md must include exact phrases — Questions: "Approved for Proposal"; Proposal: "Approved for Plan"; Plan: "Approved to Implement".

  • Read .llm.md only; write both .md and .llm.md siblings for collab artifacts.

  • Chat ≤5 lines; default “Updated …”; no diffs; announce only collab file changes; log details in docs/devlog/.

  • Quiet shell: avoid cat/sed outputs; use silent checks; log details to DevLog files.

  • Quiet is mandatory (no toggle) for this tool.

  • Tool logging: use quiet wrapper; log to docs/devlog/tool.log on failures; no chat output.

  • Keep changes minimal and focused; adopt TDD (tests first); require unit/integration tests for all features; consistent style.

  • Git: Conventional Commits; branch main; optional tags YYYY-MM-DD-HHMM.

  • Tools: file-first; use rg; read ≤250 lines; respect sandbox/approvals; preface grouped commands.

  • Prompts/config (if applicable): YAML+yq; precedence CLI>ENV>project>mode>global; prompts order global→mode-system?→mode→project; outputs to runs/<ts>/; --force to overwrite; never git push.

  • Governance: For reusable rules, update system prompt and AGENTS templates; keep them aligned; log in DevLog.

  • Zero Technical Debt: Safety first; no technical debt; always production-ready; no deferring tests/docs/refactors; TDD by default; keep docs current.

  • Planning/Architecture: Plan via Questions→Proposal→Plan; maintain global architecture/module map; implement module-by-module; avoid refactors unless assumptions change and plans/docs are updated.

  • Clean Roots: Keep project root minimal; use docs/, templates/, prompts/, scripts/, etc.; avoid ad-hoc root files.

  • CI/Containers: Use Gitea Actions with local parity via Docker Compose; do work in containers; host for git/tea + Docker orchestration; dependencies via Docker; explicit names; cleanup.

  • .gitignore: Ensure .gitignore includes runs/ and common OS ignores; keep updated.

  • Audits: Run regular audits; prompt user before release; store under docs/audits/; summarize in DevLog.