Cline rules

1# asset-aware-mcp: Project Rules
2 
3These rules are meant for Cline usage in this repository.
4 
5## Goals
6- Build an MCP server and VS Code extension for **asset-aware, citation-ready** document workflows.
7- Prefer correctness and reproducibility: deterministic outputs, clear error paths, and tests for regressions.
8 
9## Repo Layout (DDD-ish)
10- `src/domain/`: pure domain models/value objects (avoid I/O and framework coupling)
11- `src/application/`: services/use-cases (coordinate domain + infrastructure)
12- `src/infrastructure/`: adapters (DOCX/PDF/Marker/LightRAG, file I/O)
13- `src/presentation/`: MCP tool layer + server wiring
14- `vscode-extension/`: client integration (TypeScript)
15 
16## Canonical Commands
17- Python checks: `uv run ruff check .`, `uv run mypy src --ignore-missing-imports`, `uv run pytest`
18- VS Code extension checks (run in `vscode-extension/`): `npm run test:ci`
19- Docker smoke: `docker build -t asset-aware-mcp:smoke .` then `docker run --rm --entrypoint python asset-aware-mcp:smoke -c "import src.presentation.server"`
20 
21## Safety / Hygiene
22- Avoid editing or committing generated/ignored outputs: `dist/`, `vscode-extension/out/`, `data/`, `.venv/`.
23- Never print or commit secrets from `.env`, key files, or `secrets/`.
24- Avoid destructive git operations (`reset --hard`, `clean -fdx`) unless explicitly asked.
25 
26## Prefer Existing Patterns
27- Keep MCP tool outputs backward-compatible when possible (tolerate alias keys / bilingual labels when parsing).
28- Add focused tests with fixes; keep changes minimal and scoped.
29- If you need product/architecture context, start with `memory-bank/activeContext.md` and `ARCHITECTURE.md`.
30 
31## Repo Defaults
32- Default branch: `master` (release workflows assume this unless the repo is reconfigured).
33- Use `.clineignore` to keep Cline indexing fast; explicitly mention ignored fixtures when you need them.
34