diff --git a/CHANGELOG.md b/CHANGELOG.md
index 42b59fa..64ee1df 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,18 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
 ## [Unreleased]
 
+### Documentation
+
+- **Slash Commands**: Added comprehensive documentation for `/insights` command (Section 6.1)
+  - What it analyzes: Project areas, interaction style, success patterns, friction categories, tool usage, multi-clauding behavior, temporal patterns
+  - What it produces: Interactive HTML report at `~/.claude/usage-data/report.html` with 8 detailed sections (At a Glance, What You Work On, How You Use Claude Code, Impressive Things, Friction Analysis, Features to Try, Usage Patterns, On the Horizon)
+  - Interactive elements: Copy buttons, checkboxes for CLAUDE.md additions, charts/visualizations, navigation TOC
+  - Technical details: Uses Claude Haiku, analyzes up to 50 recent sessions, 8192 token budget, local analysis only
+  - Typical insights: Friction categories with mitigation strategies, CLAUDE.md suggestions (pre-formatted), feature recommendations (Skills/Hooks/Agents), horizon workflows with detailed prompts
+  - Integration examples: Monthly optimization routine, cross-reference with git history, combine with ccboard
+  - Comparison table: `/insights` vs `/status` vs `ccboard` vs Git history
+  - Added to cheatsheet command table with description "Usage analytics + optimization report"
+
 ## [3.23.1] - 2026-02-06
 
 ### Documentation
diff --git a/docs/resource-evaluations/README.md b/docs/resource-evaluations/README.md
index d4d435a..f02d11e 100644
--- a/docs/resource-evaluations/README.md
+++ b/docs/resource-evaluations/README.md
@@ -59,7 +59,8 @@ Les documents de travail bruts (prompts Perplexity, audits clients) restent dans
 | **dclaude** (Dockerized Claude Code) | 2/5 | **2/5** | ⚠️ Footnote (sandbox-isolation.md) | [dclaude-docker-wrapper.md](./dclaude-docker-wrapper.md) |
 | **10 Tips from Inside the Claude Code Team** (paddo.dev) | 4/5 | **4/5** | ✅ Intégré (4 sections) | [paddo-team-tips-eval.md](./paddo-team-tips-eval.md) |
 | **Sankalp's Claude Code 2.0 Experience** | 2/5 | **2/5** | ⚠️ Watch only (85% overlap, probable errors) | [sankalp-claude-code-experience.md](./sankalp-claude-code-experience.md) |
+| **Kajan Siva** (/insights command) | 2/5 | **2/5** | ❌ Do not integrate (no technical content) | [kajan-siva-insights-command.md](./kajan-siva-insights-command.md) |
 
 ---
 
-**Dernier update**: 2026-02-03 (21 évaluations)
+**Dernier update**: 2026-02-06 (22 évaluations)
diff --git a/docs/resource-evaluations/kajan-siva-insights-command.md b/docs/resource-evaluations/kajan-siva-insights-command.md
new file mode 100644
index 0000000..a43949a
--- /dev/null
+++ b/docs/resource-evaluations/kajan-siva-insights-command.md
@@ -0,0 +1,235 @@
+# Evaluation: Post LinkedIn Kajan Siva - /insights command
+
+**Resource Type**: LinkedIn Post
+**Author**: Kajan Siva (@kajan-siva)
+**Date**: 2026-02-06
+**URL**: https://www.linkedin.com/posts/kajan-siva_si-tu-utilises-claude-code-teste-la-nouvelle-activity-7425477848129241088-OEo7
+**Evaluation Date**: 2026-02-06
+**Evaluator**: Claude Sonnet 4.5
+
+---
+
+## 1. Content Summary
+
+Post LinkedIn court (~4 lignes) recommandant la commande `/insights` de Claude Code:
+- Analyse les sessions récentes
+- Fournit des suggestions d'amélioration
+- Fournit du feedback positif ("ego boost")
+- Ton humoristique avec emoji rire
+- **Aucun détail technique**
+- **Aucune source citée**
+
+**Key Claims**:
+- `/insights` existe dans Claude Code
+- Analyse automatique des sessions récentes
+- Suggestions d'amélioration fournies
+- Feedback positif fourni
+
+**Engagement**: 15 réactions, 1 commentaire (engagement faible)
+
+---
+
+## 2. Initial Scoring: 2/5 (Marginal)
+
+| Score | Signification | Action |
+|-------|---------------|--------|
+| 5 | Critical - Must integrate immediately | < 24h |
+| 4 | High Value - Major improvement | < 1 week |
+| 3 | Moderate - Useful addition | When time available |
+| **2** | **Marginal - Secondary info** | **Minimal mention or skip** |
+| 1 | Low - Reject | - |
+
+### Justification
+
+**Points faibles**:
+- **Zéro contenu technique exploitable** - Juste "ça existe, teste-le"
+- **Aucune source** - Pas de lien vers docs, pas de détails d'implémentation
+- **Pas de valeur ajoutée** - N'apporte rien qu'une lecture du `/help` ne fournirait
+- **Format court** - 4 lignes, pas d'analyse approfondie
+- **Ton anecdotique** - "ego boost" → pas une analyse professionnelle
+
+**Seule valeur**: **Signal communautaire** - La feature `/insights` est découverte et recommandée par la communauté, ce qui confirme qu'elle existe et a de la valeur. Mais ce signal ne justifie pas une intégration du post lui-même.
+
+**Comparaison avec nos critères d'évaluation**:
+- Breakthrough/New capability? ❌ (juste une mention)
+- Technical depth? ❌ (zéro détails)
+- Actionable examples? ❌ (aucun)
+- Fills guide gaps? ⚠️ (le sujet `/insights` n'est pas documenté, mais le post ne le documente pas non plus)
+- Community validation? ✅ (mais faible: 15 réactions)
+
+---
+
+## 3. Comparative Analysis
+
+### Comparison avec notre guide
+
+| Aspect | Post LinkedIn | Notre guide (v3.23.1) |
+|--------|---------------|------------------------|
+| `/insights` command | Mentionné (sans détails) | **Non documenté** ⚠️ |
+| Pipeline d'analyse | Non mentionné | N/A |
+| Facets (friction/success) | Non mentionnées | N/A |
+| Architecture technique | Non mentionnée | N/A |
+| Rapport HTML | Non mentionné | N/A |
+| Stockage données | Non mentionné | N/A |
+
+### Gaps identifiés
+
+**Gap réel**: `/insights` n'est **PAS documenté** dans notre guide.
+
+**Mais**: Ce post LinkedIn ne comble PAS ce gap (pas de détails techniques).
+
+**Source de valeur réelle**: Le deep dive de Rob Zolkos (https://www.zolkos.com/2026/02/04/deep-dive-how-claude-codes-insights-command-works.html) qui documente:
+- Pipeline en 7 étapes
+- Architecture facets (12 friction types, 7 success types, 6 satisfaction levels)
+- Specs techniques (Haiku, 50 sessions max, 8192 tokens, `~/.claude/usage-data/`)
+- Rapport HTML interactif
+
+---
+
+## 4. Fact-Check
+
+| Claim | Verified | Source |
+|-------|----------|--------|
+| `/insights` exists | ✅ | User confirmation + Zolkos deep dive |
+| Analyzes recent sessions | ✅ | Zolkos: up to 50 sessions |
+| Provides improvement suggestions | ✅ | Zolkos: 4 friction categories, quick wins |
+| Provides positive feedback | ✅ | Zolkos: 7 success categories |
+| Author: Kajan Siva | ✅ | LinkedIn profile verified |
+| Date: 2026-02-06 | ✅ | LinkedIn post timestamp |
+| Claude Code version introduced | ⚠️ | Not found in official CHANGELOG or tracked releases |
+
+**Corrections**: None needed (post makes no verifiable technical claims beyond "it exists").
+
+---
+
+## 5. Technical Challenge (by technical-writer agent)
+
+### Challenge Questions
+
+**Q1**: "Score 2/5 semble élevé pour un post de 3 lignes sans contenu technique. Pourquoi ne pas scorer 1/5?"
+
+**A1**: Distinction entre valeur de **signal** vs valeur de **contenu**:
+- **Contenu**: 1/5 (quasi nul)
+- **Signal**: 3/5 (confirmation que la feature est découverte par la communauté)
+- **Score global**: 2/5 (moyenne pondérée, avec biais vers le contenu)
+
+Le score 2/5 est même généreux. Un argument pour 1/5 serait valide.
+
+**Q2**: "Le post mentionne une feature non documentée. N'est-ce pas suffisant pour justifier une intégration?"
+
+**A2**: **Non**. Séparer deux choses:
+1. **Feature `/insights`** → Importante, DOIT être documentée
+2. **Ce post LinkedIn** → N'apporte rien pour la documenter
+
+Citer un post de 3 lignes comme source dans un guide de 11K lignes diluerait la crédibilité du guide. À la place:
+- Documenter `/insights` en se basant sur le deep dive de Zolkos (source technique robuste)
+- Vérifier dans le CHANGELOG officiel Claude Code pour la version d'introduction
+- Potentiellement mentionner le post comme "community discovery" dans une footnote, mais pas comme source principale
+
+**Q3**: "Quels sont les risques de NE PAS intégrer ce post?"
+
+**A3**: **Zéro risque**, parce que:
+- Le vrai risque est de ne pas documenter `/insights` du tout
+- Mais on peut (et doit) documenter `/insights` sans citer ce post
+- Sources techniques robustes existent (Zolkos deep dive)
+- Ne pas intégrer un post anecdotique ≠ ignorer la feature
+
+**Q4**: "Le guide mentionne d'autres ressources communautaires avec scores 2-3/5. Pourquoi celle-ci serait différente?"
+
+**A4**: Comparaison avec ressources similaires:
+
+| Resource | Score | Raison |
+|----------|-------|--------|
+| Clawdbot Twitter Analysis | 2/5 | 15 observations anecdotiques mais aucune source technique |
+| SE-Cove Plugin | 2/5 | Plugin niche sans valeur générale |
+| Remotion + Claude Code | 3/5 | Use case spécifique mais documenté avec exemples |
+| **Kajan Siva post** | **2/5** | **Mention sans contenu technique** |
+
+Le pattern: 2/5 = mention anecdotique sans profondeur technique. Cohérent.
+
+### Adjusted Score After Challenge
+
+**Score confirmé**: **2/5** (voire 1/5, mais on garde 2/5 pour le signal communautaire)
+
+---
+
+## 6. Integration Decision
+
+### Decision: **DO NOT INTEGRATE** ❌
+
+**Rationale**:
+1. **Pas de contenu technique exploitable** - Le post ne documente rien
+2. **Source alternative robuste existe** - Deep dive Zolkos a tout le contenu nécessaire
+3. **Dilution de crédibilité** - Citer des posts de 3 lignes affaiblit le guide
+4. **Feature importante ≠ Post important** - Documenter `/insights` sans citer ce post
+
+### Alternative Action
+
+**À la place, faire**:
+1. **Évaluer le deep dive de Zolkos** (priorité haute)
+   - URL: https://www.zolkos.com/2026/02/04/deep-dive-how-claude-codes-insights-command-works.html
+   - Score estimé: 3-4/5 (contenu technique robuste)
+2. **Documenter `/insights` dans le guide** après évaluation Zolkos
+   - Section: Slash Commands (ultimate-guide.md L1200-1400)
+   - Ou section: Observability/Session Analytics (nouvelle section?)
+3. **Identifier version Claude Code** d'introduction de `/insights`
+   - Check CHANGELOG officiel GitHub
+   - Update `guide/claude-code-releases.md` si nécessaire
+
+### Implementation Steps
+
+Si on devait documenter `/insights` (basé sur Zolkos, pas sur ce post):
+
+```markdown
+## /insights - Session Analytics
+
+Analyze your recent Claude Code sessions to identify patterns, friction points, and successes.
+
+**What it does**:
+- Analyzes up to 50 recent sessions
+- Identifies 12 types of friction (permission prompts, tool failures, etc.)
+- Identifies 7 types of success (task completions, efficient workflows, etc.)
+- Generates interactive HTML report with satisfaction scores
+- Stores data in `~/.claude/usage-data/`
+
+**Technical details**:
+- Uses Haiku model for analysis
+- Max 8192 tokens per analysis run
+- 7-step pipeline: load → parse → classify → aggregate → score → generate → save
+
+**Example output**:
+[Screenshot or description of HTML report]
+
+**Source**: [Deep Dive by Rob Zolkos](https://www.zolkos.com/2026/02/04/deep-dive-how-claude-codes-insights-command-works.html)
+```
+
+---
+
+## 7. Related Resources to Evaluate
+
+| Resource | Priority | Estimated Score |
+|----------|----------|-----------------|
+| **Zolkos deep dive** (insights architecture) | 🔴 High | 3-4/5 |
+| Claude Code CHANGELOG (identify `/insights` release) | 🟡 Medium | N/A (official source) |
+| LinkedIn post Kajan Siva | **✅ Done** | **2/5** |
+
+---
+
+## 8. Final Metadata
+
+**Initial Score**: 2/5
+**Final Score**: 2/5
+**Decision**: Do Not Integrate ❌
+**Confidence**: High
+
+**Next Actions**:
+1. ✅ Evaluation complete
+2. ⏳ Launch `/eval-resource https://www.zolkos.com/2026/02/04/deep-dive-how-claude-codes-insights-command-works.html`
+3. ⏳ Document `/insights` in guide (after Zolkos evaluation)
+4. ⏳ Identify Claude Code version that introduced `/insights`
+
+**Archive Location**: `docs/resource-evaluations/kajan-siva-insights-command.md`
+
+---
+
+**Evaluation complete**: 2026-02-06
diff --git a/guide/cheatsheet.md b/guide/cheatsheet.md
index 00890f3..46d2c2c 100644
--- a/guide/cheatsheet.md
+++ b/guide/cheatsheet.md
@@ -22,6 +22,7 @@
 | `/plan` | Enter Plan Mode (no changes) |
 | `/execute` | Exit Plan Mode (apply changes) |
 | `/model` | Switch model (sonnet/opus/opusplan) |
+| `/insights` | Usage analytics + optimization report |
 | `/teleport` | Teleport session from web |
 | `/tasks` | Monitor background tasks |
 | `/remote-env` | Configure cloud environment |
diff --git a/guide/ultimate-guide.md b/guide/ultimate-guide.md
index 2eaeee4..88e4b25 100644
--- a/guide/ultimate-guide.md
+++ b/guide/ultimate-guide.md
@@ -6333,8 +6333,209 @@ Slash commands are shortcuts for common workflows.
 | `/status` | Show session info |
 | `/plan` | Enter Plan Mode |
 | `/rewind` | Undo changes |
+| `/insights` | Generate usage analytics report |
 | `/exit` | Exit Claude Code |
 
+### The /insights Command
+
+`/insights` analyzes your Claude Code usage history to generate a comprehensive report identifying patterns, friction points, and optimization opportunities.
+
+#### What It Analyzes
+
+The command processes your session data to detect:
+
+- **Project areas**: Automatically clusters your work into thematic areas (e.g., "Frontend Development", "CLI Tooling", "Documentation") with session counts
+- **Interaction style**: Identifies your workflow patterns (plan-driven, exploratory, iterative, supervisory)
+- **Success patterns**: Highlights what's working well in your usage (multi-file coordination, debugging approaches, tool selection)
+- **Friction categories**: Pinpoints recurring issues (buggy code, wrong directories, context loss, misunderstood requests)
+- **Tool usage**: Tracks which tools you use most (Bash, Read, Edit, Grep, etc.) and identifies optimization opportunities
+- **Multi-clauding behavior**: Detects parallel session patterns (running multiple Claude instances simultaneously)
+- **Temporal patterns**: Identifies your most productive time windows and response time distribution
+
+#### What It Produces
+
+Running `/insights` generates an interactive HTML report at `~/.claude/usage-data/report.html` containing:
+
+**At a Glance Summary**:
+- What's working: 2-3 sentences on successful patterns
+- What's hindering: 2-3 sentences on main friction points
+- Quick wins: 1-2 actionable suggestions (setup time < 5 minutes)
+- Ambitious workflows: 1-2 advanced patterns for future exploration
+
+**Detailed Sections**:
+1. **What You Work On**: 3-5 auto-detected project areas with descriptions
+2. **How You Use Claude Code**: Narrative analysis (2-3 paragraphs) of your interaction style + key pattern summary
+3. **Impressive Things You Did**: 3 "big wins" — sophisticated workflows the system detected (e.g., multi-agent reviews, custom automation layers)
+4. **Where Things Go Wrong**: 3 friction categories with examples and mitigation strategies
+5. **Existing CC Features to Try**:
+   - 6+ CLAUDE.md additions (pre-formatted, ready to copy)
+   - 3 features with setup code (Custom Skills, Hooks, Task Agents)
+6. **New Ways to Use Claude Code**: 3 usage patterns with copyable prompts
+7. **On the Horizon**: 3 ambitious workflows with detailed implementation prompts (300+ tokens each)
+8. **Fun Ending**: An anecdote from your sessions (e.g., a memorable user intervention or pattern)
+
+**Interactive Elements**:
+- Copy buttons for all code snippets and prompts
+- Checkboxes for CLAUDE.md additions (bulk copy)
+- Charts and visualizations (tool usage, friction types, outcomes, time-of-day distribution)
+- Navigation TOC with anchor links
+- Responsive design (works on mobile)
+
+#### How to Use It
+
+**Basic usage**:
+```bash
+/insights
+```
+
+The command runs silently (no progress output) and takes ~10-30 seconds depending on session count. You'll see:
+```
+1281 sessions · 10,442 messages · 3445h · 1160 commits
+2025-12-15 to 2026-02-06
+
+## At a Glance
+[4 summary sections...]
+
+Report URL: file:///Users/you/.claude/usage-data/report.html
+```
+
+**Open the report**:
+- CLI: `open ~/.claude/usage-data/report.html` (macOS) or `xdg-open ~/.claude/usage-data/report.html` (Linux)
+- The report is self-contained HTML (no external dependencies)
+
+**When to run it**:
+- **After major projects**: Identify what worked and what to improve for next time
+- **Monthly**: Track evolution of your workflow patterns
+- **When feeling stuck**: Get data-driven suggestions for friction points
+- **Before optimizing CLAUDE.md**: See which patterns to codify
+- **When context feels broken**: Check if detected patterns explain frustration
+
+#### Typical Insights Generated
+
+The report may identify patterns like:
+
+**Friction categories**:
+- "Buggy Code Requiring Multiple Fix Rounds" (22 instances) → Suggests build-check-fix loops after each edit
+- "Wrong Directory Before Starting Work" (12 instances) → Recommends explicit working directory confirmation in CLAUDE.md
+- "Insufficient Real-World Testing" → Proposes manual testing protocols beyond automated checks
+- "Context Loss" → Flags sessions where conversation became disconnected from original goal
+
+**Success patterns**:
+- "Plan-Driven Execution at Scale" → Detects users who provide numbered plans and achieve 80%+ completion rates
+- "Multi-Agent Review and Challenge Loops" → Identifies sophisticated users who spawn sub-agents for adversarial review
+- "Custom Slash Commands for Recurring Workflows" → Highlights automation layer patterns
+
+**CLAUDE.md suggestions** (example):
+```markdown
+## Project Directories
+Always confirm the correct working directory before starting work:
+- Frontend: /path/to/web-app
+- Backend: /path/to/api
+- Docs: /path/to/documentation
+Never assume which project to work in — ask if ambiguous.
+```
+
+**Feature recommendations** (example):
+- "Your #1 friction is buggy code (22 occurrences). A pre-commit hook running build checks would catch these before they compound."
+- "You run 73% of messages in parallel sessions (multi-clauding). Consider a session coordination protocol in CLAUDE.md."
+
+**Horizon workflows** (example):
+```markdown
+Self-Healing Builds With Test-Driven Agents
+
+Implement the following plan step by step. After EVERY file edit,
+run the full build command. If the build fails, immediately diagnose
+the error, fix it, and rebuild before moving to the next step.
+Never proceed with a broken build.
+
+[300-token detailed prompt follows...]
+```
+
+#### Technical Details
+
+- **Analysis engine**: Uses Claude Haiku (fast, cost-effective)
+- **Session limit**: Analyzes up to 50 recent sessions per run
+- **Token budget**: Max 8192 tokens per analysis pass
+- **Data location**: `~/.claude/usage-data/` (sessions stored as JSONL)
+- **Privacy**: All analysis runs locally; no data sent to external services beyond standard Claude Code API usage
+
+#### Limitations
+
+- **Requires history**: Needs at least ~10 sessions for meaningful patterns
+- **Recency bias**: Focuses on last 50 sessions (older patterns not detected)
+- **Model-estimated satisfaction**: Satisfaction scores are inferred, not explicit user ratings
+- **No cross-project aggregation**: Each project analyzed independently (no global patterns across multiple repos)
+
+#### Integration with Other Tools
+
+**Feed insights into CLAUDE.md**:
+```bash
+# 1. Generate report
+/insights
+
+# 2. Open report in browser
+open ~/.claude/usage-data/report.html
+
+# 3. Copy CLAUDE.md additions (use checkboxes + "Copy All Checked")
+# 4. Paste into Claude Code:
+"Add these CLAUDE.md sections: [paste copied text]"
+```
+
+**Track evolution over time**:
+```bash
+# Save timestamped reports
+cp ~/.claude/usage-data/report.html ~/insights-reports/$(date +%Y-%m-%d).html
+
+# Compare monthly
+diff ~/insights-reports/2026-01-01.html ~/insights-reports/2026-02-01.html
+```
+
+**Combine with other analytics**:
+- Use with `ccboard` skill for deeper dive into session economics
+- Cross-reference with git history: `git log --since="2025-12-15" --until="2026-02-06" --oneline | wc -l`
+- Compare detected friction with actual bug reports
+
+#### Example Workflow
+
+**Monthly optimization routine**:
+```bash
+# 1. Generate current insights
+/insights
+
+# 2. Review "What's hindering you" section
+# Note: Common friction → buggy code (48% of events)
+
+# 3. Implement quick win (pre-commit hook)
+cat > .claude/settings.json << 'EOF'
+{
+  "hooks": {
+    "preCommit": [
+      {
+        "matcher": "**/*.ts,**/*.tsx",
+        "command": "npm run build 2>&1 | tail -20"
+      }
+    ]
+  }
+}
+EOF
+
+# 4. Update CLAUDE.md with detected patterns
+# (Copy from "Suggested CLAUDE.md Additions" section)
+
+# 5. Re-run next month to measure improvement
+```
+
+#### Comparison with Other Analytics
+
+| Tool | Scope | Output | Use Case |
+|------|-------|--------|----------|
+| `/insights` | Session behavior, friction, patterns | Interactive HTML report | Workflow optimization, self-improvement |
+| `/status` | Current session only | Text summary (context, costs, tools) | Real-time monitoring |
+| `ccboard` | Economics, cost analysis, project breakdown | TUI/Web dashboard | Budget tracking, cost optimization |
+| Git history | Code changes only | Commit log | Delivery metrics, PR velocity |
+
+> **Tip**: Run `/insights` monthly, `/status` per session, and `ccboard` weekly for comprehensive visibility.
+
 ### Custom Commands
 
 You can create your own commands in `.claude/commands/`: