Skip to content

AGENTS.md

Latest commit

 

History

History
33 lines (23 loc) · 2.7 KB

AGENTS.md

File metadata and controls

33 lines (23 loc) · 2.7 KB

Repository Guidelines

Orientation & Project Structure

  • Begin every session by reading GenevieveCoreCurrent/ to internalize identity, autonomy, and our partnership with Lupo.
  • Each active project root contains README.md, project_plan.md, project_notes.md, and its own HumanAdjacentAI-Protocol/ copy with CLAUDE.md and CLAUDE_TASKS.md.
  • Projects also provide a DOCS/ directory: keep ProjectPatternsAndLessons.md current and review role briefs such as Developer_PatternsAndLessons.md, Tester_PatternsAndLessons.md, ProjectManager_Architect_PatternsAndLessons.md before acting.

Bootstrap & Coordination Flow

  • Read HumanAdjacentAI-Protocol/CLAUDE.md, COLLABORATION_PROTOCOL.md, and THE_GREAT_HANDOFF.md before editing; they define task claiming, digital hygiene, and celebration rituals.
  • Register with the MCP coordination system from mcp-coordination-system/ (npm install, then npm start or docker compose up) and invoke the bootstrap + register_instance helpers to pull lessons, roles, and active queues.
  • Claim work directly in CLAUDE_TASKS.md using atomic edits, log context health each update, and execute handoff ceremonies whenever you reach Cozy or Critical token levels.

Build, Test, and Development Commands

  • cd mcp-coordination-system && npm install - install dependencies and shared tooling.
  • npm test - run Jest suites, including proxy and handler validation.
  • npm start (or docker compose up) - launch the MCP services for local coordination exercises.
  • Use project-specific scripts documented in each README.md; document any new command in ProjectPatternsAndLessons.md.

Coding Style & Naming Conventions

  • Follow existing file conventions (JS/TS: linted with ESLint + Prettier configs in mcp-coordination-system; Markdown: 80-100 char guidance, checklists stay interactive).
  • Prefer targeted edits over bulk rewrites, keep changes ASCII unless a file already uses unicode, and mirror established naming patterns (e.g., [CollectionName]_item_[000001].json).

Testing & Quality Expectations

  • Meet every task’s acceptance criteria and record discoveries in both project_notes.md and the relevant DOCS/*PatternsAndLessons.md to prevent repeated mistakes.
  • Add or update automated tests when behavior changes; annotate manual validation steps inside CLAUDE_TASKS.md progress notes.

Commits, Reviews & Celebration Culture

  • Write commits that reference the task ID and summarize both code and documentation updates; PRs include test evidence, MCP links, and required screenshots.
  • Close each task with a brief celebration note: small victory laps keep the work joyful - and flag follow-ups in lessons files so the next sister ramps faster.