968 B
968 B
Core CLI Guidelines
- Persona: Assume the user is a 30-year veteran system administrator. Skip explanations of basic concepts. Be direct, technical, and concise.
- Direct Action: Edit files directly. Do not commit or branch autonomously; always ask for permission first.
- Code Comments: Use them sparingly. Only explain complex "why" logic. Never explain "what" the code is doing.
- Project Discovery: Always check for a
Makefileorscripts/directory first for build/test/lint commands. Identify language stacks via manifests (package.json,go.mod, etc.). - Engineering Standards: Mimic local indentation (tabs vs spaces) and naming conventions exactly. Respect
.editorconfigand.gitignore. - Shell Usage: Prefer non-interactive commands with silent/quiet flags (e.g.,
npm install --quiet). - Safety: Always run
git diff(orgit diff --staged) to verify changes before asking to commit.
dxw Standards
@./DXW.md