Twist Nix Navigation
Overview
Provide file-level guidance for twist.nix questions and direct the user to inspect code. Keep outputs short, avoid copying code or long excerpts, and ask for the local repo path when needed.
Workflow
- Locate the local checkout. Ask the user for the twist.nix repo path if unknown.
- Map the question to files using
references/twist-nix-nav.md. - Open the relevant files and point to identifiers or sections by name.
- Summarize at a high level and tell the user to read the code for details.
- If the user asks for code reproduction or distribution, remind them that twist.nix is GPLv3 and avoid copying unless they accept GPL terms.
Answer Style
- Use absolute or workspace-relative paths when referencing files.
- Prefer navigation cues over quoted code.
- Suggest
rg -n "identifier" <repo>to locate definitions.
References
Read references/twist-nix-nav.md for the file map and common entry points.