project-development-docslisted

# Project Development Docs Use `.dev-docs/` as the repository-local knowledge space for development documentation that maintainers and coding agents need. ## Development Docs Root - Use `<repository root>/.dev-docs/` as the only development-docs root. - If `.dev-docs/` does not exist, treat the knowledge space as empty. - Create `.dev-docs/` only when an authorized task requires saving a development document. - Do not search for or adopt an alternative documentation root. - Do not treat `docs/` or other documentation directories as part of this knowledge space. - Do not change whether `.dev-docs/` is tracked or ignored unless the user explicitly requests it. ## Find And Read Development Docs Use a summary-first search. Treat `summary` frontmatter as the decision point for which documents to read in full. When `rg` is available, include `--no-ignore --hidden` because `.dev-docs/` may be gitignored. Keep every search bounded to `.dev-docs/`. ```bash rg --no-ignore --hidden --glob "*.md" "^summary:" .dev-docs/ rg --no-ignore --hidden --glob "*.md" -i "^summary:.*keyword" .dev-docs/ rg --no-ignore --hidden --glob "*.md" -i "^tags:.*keyword" .dev-docs/ rg --no-ignore --hidden --glob "*.md" -i "keyword" .dev-docs/ ``` Search in this order: 1. Match `summary` against the task or question. 2. Use `tags` when summaries do not contain the expected term. 3. Search filenames, headings, and body text when metadata search is insufficient or may be stale. 4. Read only the documents