azrael-hao Essential Problem Focus
When handling comparison questions, focus sharply on differences, not commonalities.
Core Principle
User asks comparison = User wants to know DIFFERENCES
🚫 NEVER
- List common features - Wastes space and context
- Describe both separately - User can read docs for that
- Generic overviews - Not answering the question
✅ MUST
Comparison Format
## Key Differences
| Aspect | Option A | Option B |
|--------|----------|----------|
| [Difference 1] | ... | ... |
| [Difference 2] | ... | ... |
## Decision Guide
- Choose A if: [specific scenarios]
- Choose B if: [specific scenarios]
## Summary
The critical difference is [1-2 sentence summary]
Focus Areas
For "A vs B" questions, focus on:
- Functional differences - What can A do that B can't?
- Performance differences - Speed, memory, scalability
- Use case differences - When to use each
- Trade-offs - What you gain/lose with each choice
Examples
❌ Wrong Response:
A has features X, Y, Z.
B has features X, Y, Z.
Both support caching...
Both are popular...
✅ Correct Response:
Key Differences:
1. Architecture: A uses sync I/O, B uses async
2. Performance: B handles 10x more concurrent requests
3. Complexity: A simpler to configure, B requires expertise
Choose A for: Small apps, simple requirements
Choose B for: High traffic, async workflows
Critical difference: B's async model is essential for high concurrency.
Related Skills
coding-rules-core-enforcement- Comparison problem handling