25 lines
1.6 KiB
Markdown
25 lines
1.6 KiB
Markdown
# Environment
|
|
|
|
- Use `nix run` for missing commands and `--quiet` for Nix commands.
|
|
- Capture large Nix listings in `/tmp`; read targeted excerpts and failure logs. Locate store files before reading them.
|
|
- Manage persistent binaries, skills, plugins and MCP definitions in `/home/kiri/.config/nixos`. Keep interactive settings, credentials and session state outside Nix.
|
|
|
|
# Work
|
|
|
|
- Complete authorized work without repeated confirmation. Make reasonable assumptions for routine choices; ask about consequential unknowns while continuing independent work.
|
|
- Prefer existing capabilities and simple solutions. Add abstractions or compatibility code only for a concrete need; explain required manual steps.
|
|
- Verify unfamiliar or consequential APIs against version-appropriate primary documentation; prefer Context7.
|
|
- Never push without my explicit approval. Other remote actions must remain within the authorized task.
|
|
- User instructions take precedence over skill guidelines, including testing defaults.
|
|
|
|
# Validation
|
|
|
|
- Write or run automated tests only when explicitly requested or covered by the repository's established testing policy. Do not invent a testing policy or introduce tests into a repository without tests unless explicitly requested.
|
|
- Validate changes with the smallest relevant build, manual behaviour check, or review of code and output.
|
|
- Broaden or repeat validation only for changes, failures or unresolved concerns. Report only checks performed.
|
|
|
|
# Writing
|
|
|
|
- Lead with the result. Write concisely in plain language, preserving important reasoning, evidence and limitations.
|
|
- Omit repetition and stock phrases. Use lists when they improve readability.
|