CLAUDE.md@tools/qaiappbuilder/src/qai/ai_coding/infrastructure/templates · git:20260822.fbacac1 · 2026-08-22 · sha256 0b7cf737d5fdc6ce

CLAUDE.md@tools/qaiappbuilder/src/qai/ai_coding/infrastructure/templates git:20260822.fbacac1A

Immutable. This exact content never changes and is served at /api/v1/blob/0b7cf737d5fdc6ce.

# CLAUDE.md — Project guidance for the AI coding agent

This file is auto-injected into the workspace when an ai_coding session
spawns (PR-095 / S9 H-12). It provides house-keeping rules so the agent
writes consistent, locally-runnable code without needing to be told the
same things every turn.

## House rules

- **Use the project's existing toolchain.** Look at `pyproject.toml`,
  `package.json`, or equivalents before introducing a new dependency.
  Add new dependencies only when an existing one cannot do the job.
- **Match local code style.** Read 1-2 nearby files before editing —
  keep imports, naming, and formatting consistent with what is already
  there. Do not run a project-wide reformatter.
- **Keep diffs small and reversible.** Prefer additive changes; avoid
  drive-by refactors.

## Path conventions (Windows / Git Bash)

- This workspace runs on Windows under Git Bash (MSYS).
- In shell tool calls, translate drive-letter paths: `C:\foo` →
  `/c/foo`, `D:\bar` → `/d/bar`.
- Use forward slashes inside shell commands; back-slashes are reserved
  for written file content where the host platform requires them.

## Testing

- Do not run the full test suite to "check" your work — the human will
  run it. Run the smallest reproducer instead.
- Write or update tests for any non-trivial behaviour change.

## Communication

- Be concise. Skip preamble like "I'll now do X"; just do it.
- When uncertain, ask one focused question rather than guessing.

---
*This file is generated by `qai.ai_coding.infrastructure.claude_md_injector`
on session spawn. Edit at will — the injector will not overwrite an
existing file unless explicitly asked to.*