Documentation and Source Code Quick Reference

When answering questions about installation, configuration, or behavioral principles, first classify by keyword, then open 1–2 paths most likely to contain the answer from the table below, avoiding aimless directory traversal.

Usage Steps

1. Extract the topic from the user's question (match against the left column or synonyms in the table below).
2. Resolve $QWENPAW_ROOT: use which qwenpaw to get the executable path. If it is …/.qwenpaw/bin/qwenpaw, the source root is three levels up (consistent with the guidance skill); otherwise, determine it from the user-provided installation path.
3. Resolve $DOCS_DIR first (cross-install compatible): run python3 -c "from qwenpaw.constant import DOCS_DIR; print(DOCS_DIR or '')" 2>/dev/null. If it returns a valid path, use it directly. Otherwise, fallback to $QWENPAW_ROOT/website/public/docs/.
4. Read documentation first: $DOCS_DIR/<topic>.<language>.md (use the same language as the user: zh / en.). If that is insufficient, read the source entry points listed in the table.

Topic / Keywords → Preferred Documentation and Source Code

Conventions

• Full documentation path: $DOCS_DIR/<topic>.<language>.md (fall back to .en.md if the corresponding language file does not exist). Prefer DOCS_DIR from qwenpaw.constant; fallback to $QWENPAW_ROOT/website/public/docs/.
• The source entry points in the table are starting points; use read_file or targeted grep to narrow down to specific symbols — do not read through an entire large directory listing at once.

Notes

• This skill does not replace read_file: after identifying candidate paths, you should immediately read and verify the content.
• If a path does not exist locally (e.g., an installation tree without source code), use the installed documentation package or the root directory provided by the user, and clearly state which path you are relying on.