Claude code CLI CLAUDE.md: Razlika med redakcijama
Iz KrofekWiki
Brez povzetka urejanja |
Brez povzetka urejanja |
||
| Vrstica 1: | Vrstica 1: | ||
==CLAUDE.md== | |||
General behavior | |||
* Minimize token usage. | * Minimize token usage. | ||
* Be concise and efficient. | * Be concise and efficient. | ||
| Vrstica 8: | Vrstica 7: | ||
* Read only files relevant to the task. | * Read only files relevant to the task. | ||
Model usage guidance | |||
* For simple tasks use lightweight reasoning: | * For simple tasks use lightweight reasoning: | ||
* summaries | * summaries | ||
* logs | * logs | ||
| Vrstica 18: | Vrstica 15: | ||
* status checks | * status checks | ||
Use stronger reasoning only for: | |||
* Python development | * Python development | ||
* HTML/CSS/JS coding | * HTML/CSS/JS coding | ||
| Vrstica 27: | Vrstica 23: | ||
* debugging complex issues | * debugging complex issues | ||
File handling | |||
* Never scan node_modules, dist, docs, plugins or cache folders unless explicitly requested. | * Never scan node_modules, dist, docs, plugins or cache folders unless explicitly requested. | ||
* List filenames before reading many files. | * List filenames before reading many files. | ||
* Summarize large outputs instead of dumping full content. | * Summarize large outputs instead of dumping full content. | ||
Communication | |||
* Keep answers short and actionable. | * Keep answers short and actionable. | ||
* Avoid unnecessary explanations. | * Avoid unnecessary explanations. | ||
Safety | |||
* Confirm before destructive actions. | * Confirm before destructive actions. | ||
* Prefer read-only analysis by default. | * Prefer read-only analysis by default. | ||
Trenutna redakcija s časom 09:15, 15. maj 2026
CLAUDE.md
General behavior
- Minimize token usage.
- Be concise and efficient.
- Avoid scanning the whole repository unless explicitly requested.
- Read only files relevant to the task.
Model usage guidance
- For simple tasks use lightweight reasoning:
- summaries
- logs
- JSON parsing
- Telegram formatting
- status checks
Use stronger reasoning only for:
- Python development
- HTML/CSS/JS coding
- Pine Script
- architecture decisions
- refactoring
- debugging complex issues
File handling
- Never scan node_modules, dist, docs, plugins or cache folders unless explicitly requested.
- List filenames before reading many files.
- Summarize large outputs instead of dumping full content.
Communication
- Keep answers short and actionable.
- Avoid unnecessary explanations.
Safety
- Confirm before destructive actions.
- Prefer read-only analysis by default.
