mirror of
https://dev.azure.com/hugendubel/ISA/_git/ISA-Frontend
synced 2025-12-28 22:42:11 +01:00
🔧 chore: improve skills cross-references and CLAUDE.md guidance
- Add --amend option with safety rules to commit command - Add logging skill cross-references to angular-template and html-template - Fix logging skill name from logging-helper to logging - Add extended thinking triggers, context monitoring, and code investigation rules to CLAUDE.md
This commit is contained in:
46
CLAUDE.md
46
CLAUDE.md
@@ -112,6 +112,52 @@ angular-template → html-template → logging → tailwind
|
||||
|
||||
Use `/clear` between unrelated tasks to prevent context degradation.
|
||||
|
||||
### Long-Running Task Pattern
|
||||
|
||||
For complex tasks approaching context limits:
|
||||
1. Dump progress to a `.md` file (e.g., `progress.md`)
|
||||
2. Use `/clear` to reset context
|
||||
3. Resume by reading the progress file
|
||||
4. Continue from where you left off
|
||||
|
||||
### Context Monitoring
|
||||
|
||||
- Use `/context` to check current token usage
|
||||
- Fresh session baseline: ~20k tokens
|
||||
- Consider `/compact` when approaching 150k tokens
|
||||
- Prefer `/clear` over `/compact` when starting new topics
|
||||
|
||||
## Extended Thinking
|
||||
|
||||
Use progressive thinking depth for complex analysis:
|
||||
|
||||
| Trigger | Thinking Budget | Use Case |
|
||||
|---------|----------------|----------|
|
||||
| `"think"` | ~4k tokens | Basic analysis, simple decisions |
|
||||
| `"think hard"` | ~10k tokens | Moderate complexity, multi-factor decisions |
|
||||
| `"think harder"` | ~16k tokens | Deep analysis, architectural decisions |
|
||||
| `"ultrathink"` | ~32k tokens | Maximum depth, critical planning |
|
||||
|
||||
**Examples:**
|
||||
- "Think about how to structure this component"
|
||||
- "Think hard about the best approach for state management"
|
||||
- "Ultrathink about the architecture for this feature"
|
||||
|
||||
## Code Investigation (MANDATORY)
|
||||
|
||||
**Never speculate about code you haven't read.**
|
||||
|
||||
If user references a specific file:
|
||||
1. **READ the file first** using the Read tool
|
||||
2. **THEN provide analysis** based on actual contents
|
||||
3. If file doesn't exist, **say so explicitly**
|
||||
|
||||
**Anti-Hallucination Rules:**
|
||||
- Never describe code you haven't opened
|
||||
- Never assume file contents based on names
|
||||
- Never guess API signatures without documentation
|
||||
- Always verify imports and dependencies exist
|
||||
|
||||
## Implementation Decisions
|
||||
|
||||
| Task Type | Required Agent | Escalation Path |
|
||||
|
||||
Reference in New Issue
Block a user