release: v3.29.0
- Observability: MLflow Tracing section complète (CLI + SDK, LLM-as-judge) - Skills §5.5: UI UX Pro Max (33.7k stars, design reasoning engine BM25) - Diagram #41: AI Fluency High vs Low paths (Anthropic research) - 3 callouts empiriques AI Fluency Index (Rev Engine 5.6×, CLAUDE.md 30%) - Hooks docs v2.1.47-2.1.50: WorktreeCreate/Remove, ConfigChange, --from-pr - CC releases tracking: v2.1.50 → v2.1.52 - 4 nouvelles évaluations ressources (AgentsView, AI Fluency, UX Pro Max) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
939e33ab68
commit
79157ac077
14 changed files with 1192 additions and 40 deletions
|
|
@ -0,0 +1,146 @@
|
|||
# Resource Evaluation: AgentsView — Local Session Analytics for Claude Code
|
||||
|
||||
**Evaluated**: 2026-02-23
|
||||
**Evaluator**: Claude Sonnet 4.6 + technical-writer agent challenge
|
||||
**Target Guide**: Claude Code Ultimate Guide
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
**Resource**: AgentsView — Local web app for browsing, searching, and analyzing AI coding sessions
|
||||
**URL**: https://www.agentsview.io/
|
||||
**GitHub**: https://github.com/wesm/agentsview
|
||||
**Author**: Wes McKinney (creator of pandas)
|
||||
|
||||
**Initial Score**: 4/5
|
||||
**Challenged Score**: 3/5
|
||||
**Final Score**: **3/5 (Pertinent — Complement utile)**
|
||||
|
||||
**Decision**: **Integrate in `guide/observability.md` (External Monitoring Tools section). Cross-reference in `guide/third-party-tools.md` (Session Management).** Wait 2-4 weeks for adoption to consolidate before publishing (target: ~200+ stars).
|
||||
|
||||
---
|
||||
|
||||
## 📄 Resource Summary
|
||||
|
||||
**Type**: Local-first web application (Go + Svelte 5 + SQLite FTS5)
|
||||
|
||||
**Key Points**:
|
||||
1. **Full-text search** across months of sessions via SQLite FTS5 — find specific discussions instantly
|
||||
2. **Usage analytics**: activity heatmaps, velocity metrics, tool usage breakdowns, per-project stats
|
||||
3. **Real-time monitoring**: watches session directories via Server-Sent Events, streams live messages
|
||||
4. **Multi-CLI support**: Claude Code + Codex + Gemini CLI (unique in the space)
|
||||
5. **Local-first**: single Go binary, MIT license, no accounts, no cloud; session export as HTML or GitHub Gist
|
||||
|
||||
**Technical Stack**:
|
||||
- Backend: Go (56.8% of codebase)
|
||||
- Frontend: Svelte 5 + Vite + TypeScript
|
||||
- Storage: SQLite with FTS5 full-text search
|
||||
- Real-time: Server-Sent Events (embedded web server)
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Score: 3/5
|
||||
|
||||
**Justification**: Real gap in the guide — no existing documented tool combines full-text search + visual analytics (heatmaps, velocity) in a local web UI.
|
||||
|
||||
- `claude-code-viewer`: basic session viewer, no search, no analytics
|
||||
- `session-search.sh`: CLI search only, zero UI, no analytics
|
||||
- `ccboard`: cost-centric dashboard, full-text search not confirmed
|
||||
|
||||
AgentsView fills this gap. However, the repo was created on February 19, 2026 (4 days before this evaluation), has 49 stars, and only 2 contributors. Too recent for a 4/5 (High Value) without established adoption. Wes McKinney's credibility (pandas creator) is a strong positive signal.
|
||||
|
||||
---
|
||||
|
||||
## ⚖️ Comparative Analysis
|
||||
|
||||
| Feature | AgentsView | Guide (current) |
|
||||
|---------|-----------|-----------------|
|
||||
| Full-text search sessions | ✅ SQLite FTS5 | ⚠️ CLI only (`session-search.sh`) |
|
||||
| Activity heatmaps | ✅ Yes | ❌ Missing |
|
||||
| Velocity metrics | ✅ Yes | ❌ Missing |
|
||||
| Tool usage breakdown | ✅ Yes | ⚠️ Partial (ccboard) |
|
||||
| Local web UI | ✅ Go embedded server | ⚠️ claude-code-viewer (viewer only) |
|
||||
| Real-time monitoring | ✅ SSE | ⚠️ claude-code-viewer (SSE too) |
|
||||
| Multi-CLI support | ✅ Claude + Codex + Gemini | ❌ Claude Code only |
|
||||
| Cost tracking | ❌ Not mentioned | ✅ ccusage, ccboard |
|
||||
| Session replay/rewind | ❌ No | ✅ Entire CLI |
|
||||
| Keyboard navigation | ✅ Vim-style shortcuts | N/A |
|
||||
|
||||
**vs ccboard distinction**: ccboard = cost-centric with session view. AgentsView = behavior-analytics-centric with FTS search. Different primary use case, ~40% feature overlap.
|
||||
|
||||
---
|
||||
|
||||
## 📍 Integration Recommendations
|
||||
|
||||
### Primary: `guide/observability.md` — External Monitoring Tools
|
||||
|
||||
Add row to the comparison table (after ccboard):
|
||||
|
||||
```markdown
|
||||
| **AgentsView** | Local web app | FTS search + activity heatmaps + velocity metrics + real-time monitoring. Multi-CLI (Claude/Codex/Gemini). No cost tracking. | `github.com/wesm/agentsview` |
|
||||
```
|
||||
|
||||
Add to Decision Guide:
|
||||
```
|
||||
Want search + visual analytics in one local UI? → AgentsView
|
||||
```
|
||||
|
||||
### Secondary: `guide/third-party-tools.md` — Session Management
|
||||
|
||||
Add short entry after `claude-code-viewer` with explicit differentiation:
|
||||
|
||||
| Tool | Focus | Search | Analytics |
|
||||
|------|-------|--------|-----------|
|
||||
| claude-code-viewer | UI viewer | No | No |
|
||||
| AgentsView | Search + analytics | ✅ FTS5 | ✅ Heatmaps, velocity |
|
||||
| session-search.sh | CLI search | ✅ Fast | No |
|
||||
|
||||
### Priority
|
||||
|
||||
**Low-Medium** — Integrate in 2-4 weeks once repo reaches ~200 stars. The gap is real but not critical; users can currently combine session-search.sh (CLI) + ccboard (stats).
|
||||
|
||||
---
|
||||
|
||||
## 🔥 Challenge (technical-writer)
|
||||
|
||||
The challenge agent recommended **3/5** (vs initial 4/5) for the following reasons:
|
||||
|
||||
1. **Score**: 4/5 requires verifiable adoption signals. Repo is 4 days old, 49 stars → 3/5 correct.
|
||||
2. **Placement corrected**: `observability.md` (analytics/monitoring) is the right location, not `third-party-tools.md`. The guide explicitly states third-party-tools.md is "not DIY monitoring scripts (see Observability)". AgentsView is an analytics dashboard.
|
||||
3. **ccboard overlap**: More significant than initially assessed. Must document the distinction explicitly: ccboard = cost + session view; AgentsView = FTS search + behavior analytics.
|
||||
4. **Missing in initial evaluation**: Model type (now confirmed MIT open source), exact stack (confirmed Go, not Rust), "nothing leaves your machine" claim is marketing (unaudited via traffic analysis).
|
||||
|
||||
**Adopted**: Score adjusted to 3/5. Placement changed to `observability.md`.
|
||||
|
||||
---
|
||||
|
||||
## ✅ Fact-Check
|
||||
|
||||
| Claim | Verified | Source |
|
||||
|-------|----------|--------|
|
||||
| Author = Wes McKinney | ✅ | github.com/wesm/agentsview |
|
||||
| MIT License, open source | ✅ | GitHub repo |
|
||||
| Stack Go + Svelte 5 + SQLite FTS5 | ✅ | GitHub (56.8% Go) |
|
||||
| Full-text search via SQLite | ✅ | README + codebase |
|
||||
| Activity heatmaps | ✅ | agentsview.io documentation |
|
||||
| Real-time via SSE | ✅ | GitHub description |
|
||||
| Multi-agent: Claude + Codex + Gemini | ✅ | GitHub README |
|
||||
| Single binary, local-first | ✅ | agentsview.io |
|
||||
| "Nothing leaves your machine" | ⚠️ | Marketing claim — credible given architecture, but not verified via traffic analysis |
|
||||
| 49 stars, created Feb 19 2026 | ✅ | GitHub (verified Feb 23 2026) |
|
||||
| v0.3.2, 7 releases in 4 days | ✅ | GitHub Releases |
|
||||
| Session export HTML/GitHub Gist | ✅ | GitHub README |
|
||||
|
||||
**Correction**: Initial WebFetch described a "Rust backend" — incorrect. GitHub shows Go (56.8%). Corrected.
|
||||
|
||||
**Note on LinkedIn post**: https://www.linkedin.com/posts/wesmckinn_agentsview-activity-7431693909841309696-paBN — could not be fetched (requires authentication). Not factored into scoring.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Final Decision
|
||||
|
||||
- **Final score**: **3/5**
|
||||
- **Action**: **Integrate** — `observability.md` + mention in `third-party-tools.md`
|
||||
- **Timing**: 2-4 weeks (wait for repo to reach ~200+ stars)
|
||||
- **Confidence**: **Medium** — real gap confirmed, tool verified functional, but adoption too recent for high confidence. Wes McKinney's credibility (pandas) is a strong positive signal.
|
||||
|
|
@ -0,0 +1,101 @@
|
|||
# Resource Evaluation: Anthropic AI Fluency Index
|
||||
|
||||
**URL**: https://www.anthropic.com/research/AI-fluency-index
|
||||
**Date evaluated**: 2026-02-23
|
||||
**Type**: Research report — Anthropic Education Science
|
||||
**Authors**: Kristen Swanson, Drew Bent, Saffron Huang, Zoe Ludwig, Rick Dakan, Joe Feller
|
||||
|
||||
---
|
||||
|
||||
## 📄 Content Summary
|
||||
|
||||
- **Anthropic research** on 9,830 Claude.ai conversations over a 7-day window (January 2026)
|
||||
- **Framework**: 4D AI Fluency (24 behaviors total; 11 directly observable in conversation data)
|
||||
- **Finding 1 — Iteration multiplies fluency**: 85.7% of conversations showed iteration. Iterative users had 2.67 fluency behaviors vs 1.33 for non-iterative — 2× more effective. They are 5.6× more likely to question reasoning and 4× more likely to identify missing context.
|
||||
- **Finding 2 — Artifact Paradox**: Artifact production (code, docs) made users more directive (+14.7pp) but reduced critical evaluation: −5.2pp identifying missing context, −3.7pp fact-checking, −3.1pp questioning reasoning.
|
||||
- **Finding 3 — Explicit collaboration**: Only 30% of users set collaboration terms explicitly. Those who do produce structurally more effective sessions.
|
||||
- **Future directions**: Explicit mention of Claude Code platform analysis as next research target.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Score: 4/5
|
||||
|
||||
| Score | Meaning |
|
||||
|-------|---------|
|
||||
| 5 | Essential — major gap |
|
||||
| **4** | **High value — significant improvement** |
|
||||
| 3 | Relevant — useful complement |
|
||||
| 2 | Marginal — secondary info |
|
||||
| 1 | Out of scope |
|
||||
|
||||
**Justification**: Source Anthropic first-party, published today. Provides empirical backing for three core guide recommendations that were previously asserted without data (plan review, CLAUDE.md investment, critical output evaluation). The Artifact Paradox is particularly critical for Claude Code: 100% of Claude Code outputs are artifacts.
|
||||
|
||||
---
|
||||
|
||||
## ⚖️ Gap Analysis
|
||||
|
||||
| Aspect | This resource | Guide (before integration) |
|
||||
|--------|--------------|--------------------------|
|
||||
| **Iteration improves results** | ✅ 2.67 vs 1.33 behaviors (Anthropic data) | ⚠️ Recommended but no empirical basis |
|
||||
| **Plan review before execution** | ✅ 5.6× ratio quantified | ⚠️ Shift+Tab recommended, no data |
|
||||
| **CLAUDE.md ROI** | ✅ 30% stat, explicit collaboration benefit | ⚠️ Documented but no motivating data |
|
||||
| **Artifact Paradox** | ✅ −5.2pp / −3.7pp / −3.1pp documented | ❌ Absent from guide |
|
||||
| **Claude Code specificity** | ❌ Study on Claude.ai (code future) | ✅ CLI-native focus |
|
||||
| **AI Fluency Framework** | ✅ 4D, 24 behaviors | ❌ Absent from guide |
|
||||
|
||||
---
|
||||
|
||||
## 📍 Integration Applied
|
||||
|
||||
### 1. Rev the Engine section (~line 2522)
|
||||
**What**: Callout with 5.6× stat as empirical backing for plan review
|
||||
**Why**: Justifies the "Rev the Engine" pattern with Anthropic-sourced data instead of anecdotal "30-40% catch rate"
|
||||
|
||||
### 2. CLAUDE.md Best Practices (~line 4381)
|
||||
**What**: Callout with the 30% stat as motivation for explicit collaboration setup
|
||||
**Why**: The challenge agent correctly flagged this as belonging in the CLAUDE.md section, not generic prompting
|
||||
|
||||
### 3. Common Pitfalls — Artifact Paradox (~line 13382)
|
||||
**What**: Full callout with all data points + 5 concrete counter-measures
|
||||
**Why**: Core finding directly applicable to Claude Code's nominal use case (100% output = artifacts)
|
||||
|
||||
---
|
||||
|
||||
## 🔥 Challenge Response (technical-writer)
|
||||
|
||||
The challenge agent raised the score from 3/5 to **4/5** and identified:
|
||||
|
||||
- The "Claude.ai vs CLI" gap is a false objection — behavioral patterns are human, not interface-specific
|
||||
- The Artifact Paradox is the most critical finding for Claude Code (100% of outputs are artifacts)
|
||||
- The 5.6× ratio justifies plan review more powerfully than existing anecdotal claims
|
||||
- The 30% stat belongs in the CLAUDE.md section, not generic prompting
|
||||
|
||||
---
|
||||
|
||||
## ✅ Fact-Check
|
||||
|
||||
| Claim | Verified | Source |
|
||||
|-------|----------|--------|
|
||||
| 9,830 conversations analyzed | ✅ | Article methodology section |
|
||||
| 85.7% iteration rate | ✅ | Article finding #1 |
|
||||
| 2.67 vs 1.33 fluency behaviors | ✅ | Article finding #1 |
|
||||
| 5.6× more likely to question reasoning | ✅ | Article finding #1 |
|
||||
| 4× more likely to identify missing context | ✅ | Article finding #1 |
|
||||
| −5.2pp missing context identification (artifacts) | ✅ | Article finding #2 |
|
||||
| −3.7pp fact-checking (artifacts) | ✅ | Article finding #2 — exact quote: "check facts (-3.7pp)" |
|
||||
| −3.1pp questioning reasoning (artifacts) | ✅ | Article finding #2 — exact quote: "question the model's reasoning (-3.1pp)" — NOT "3.1% of users" |
|
||||
| 30% define collaboration terms explicitly | ✅ | Article exact quote: "In only 30% of conversations do users tell Claude how they'd like it to interact with them" |
|
||||
| Publication date 2026-02-23 | ✅ | Article byline (today) |
|
||||
|
||||
**No corrections needed.** All stats verified directly in source.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Final Decision
|
||||
|
||||
- **Score**: 4/5
|
||||
- **Action**: Integrated (3 insertion points)
|
||||
- **Confidence**: High — Anthropic first-party, all stats verified
|
||||
|
||||
**Evaluation completed**: 2026-02-23
|
||||
**Next review**: 2026-06-23 (check for follow-up Claude Code platform study)
|
||||
|
|
@ -0,0 +1,128 @@
|
|||
---
|
||||
title: "Veille Claude Code Releases 2.1.44 → 2.1.50 (17-23 fev 2026)"
|
||||
type: "weekly-watch"
|
||||
date: "2026-02-23"
|
||||
score: 4
|
||||
action: "integrate"
|
||||
sources:
|
||||
- "Texte copie (analyse veille structuree par version)"
|
||||
- "https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md"
|
||||
- "https://releasebot.io/updates/anthropic/claude-code"
|
||||
---
|
||||
|
||||
# Veille CC Releases 2.1.44 → 2.1.50 (17-23 fev 2026)
|
||||
|
||||
## Resume
|
||||
|
||||
Analyse detaillee de 6 releases Claude Code (17-21 fev 2026) couvrant : worktree isolation native, nouveaux hooks `WorktreeCreate`/`WorktreeRemove`/`ConfigChange`, breaking change keybinding (`Ctrl+F` remplace double-ESC), corrections massives de fuites memoire, et migration modele Sonnet 4.6 1M context.
|
||||
|
||||
## Score: 4/5
|
||||
|
||||
**Justification**: Les releases YAML et claude-code-releases.md sont deja a jour (2.1.50). Les features majeures (worktree isolation, hooks WorktreeCreate/WorktreeRemove, claude agents CLI, env vars 1M) sont dans ultimate-guide.md. La valeur de cette veille = audit de couverture qui revele 8+ gaps dans les sections thematiques + **1 bug documentation actif critique** (ESC/double-ESC).
|
||||
|
||||
## Bug Critique Identifie et Corrige
|
||||
|
||||
**Fichier**: `guide/ultimate-guide.md` lignes ~5738-5741
|
||||
|
||||
**Probleme**: Le guide indiquait `ctrl+c ctrl+c` / `ESC ESC` pour tuer les agents de fond. Faux depuis v2.1.47.
|
||||
|
||||
**Risque**: Utilisateurs croyant leurs agents tues alors qu'ils tournent en fond (consommation tokens silencieuse, conflits d'ecriture parallele).
|
||||
|
||||
**Fix applique**: Corrige le 2026-02-23. ESC ne cancel plus que le thread principal. `Ctrl+F` = seul moyen de gerer les agents de fond (overlay).
|
||||
|
||||
## Gaps Identifies
|
||||
|
||||
| Gap | Localisation cible | Priorite | Status |
|
||||
|-----|-------------------|----------|--------|
|
||||
| Bug ESC/double-ESC → `Ctrl+F` | ultimate-guide.md ~5738-5741 | **P0 BUG** | ✅ CORRIGE |
|
||||
| `ConfigChange` hook event | ultimate-guide.md Section 7 Hooks (Event Types table) | **P1** | ✅ FAIT |
|
||||
| `disableAllHooks` managed hierarchy (breaking) | ultimate-guide.md Section Enterprise/Settings | **P1** | ✅ FAIT (note dans ConfigChange section) |
|
||||
| `startupTimeout` LSP config | ultimate-guide.md Section LSP | P2 | ✅ FAIT |
|
||||
| `last_assistant_message` Stop/SubagentStop hooks | ultimate-guide.md Section Hooks Stop event | P2 | ✅ FAIT |
|
||||
| `--from-pr` CLI flag | ultimate-guide.md Section Workflows GitHub | P2 | ✅ FAIT |
|
||||
| `enabledPlugins` / `extraKnownMarketplaces` via `--add-dir` | ultimate-guide.md Section Plugins | P2 | ✅ FAIT |
|
||||
| `SDKRateLimitInfo` / `SDKRateLimitEvent` | ultimate-guide.md Section SDK reference | P3 | ⏳ |
|
||||
| `spinnerTipsOverride` setting | ultimate-guide.md Section Settings config | P3 | ⏳ |
|
||||
| `chat:newline` keybinding | ultimate-guide.md Section Keybindings | P3 | ⏳ |
|
||||
| `added_dirs` in statusline JSON workspace | ultimate-guide.md Section Statusline | P3 | ⏳ |
|
||||
|
||||
## Plan d'integration Progressive
|
||||
|
||||
### Phase 1 — Hooks (P1, 1 session)
|
||||
|
||||
**`ConfigChange` hook** — Ajouter dans la table des evenements hooks (autour de la section WorktreeCreate/WorktreeRemove existante) :
|
||||
|
||||
```markdown
|
||||
| `ConfigChange` | When config files change during session | Enterprise: audit + block live config changes |
|
||||
```
|
||||
|
||||
Avec exemple :
|
||||
```json
|
||||
{
|
||||
"hooks": {
|
||||
"ConfigChange": [
|
||||
{
|
||||
"matcher": "",
|
||||
"hooks": [{ "type": "command", "command": "scripts/audit-config-change.sh" }]
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**`disableAllHooks` managed hierarchy** — Note dans la section Enterprise Settings :
|
||||
> `disableAllHooks` (v2.1.49+) ne peut plus desactiver les hooks managed par la politique entreprise. Les hooks du niveau `managed` overrident toujours les settings utilisateur.
|
||||
|
||||
**`last_assistant_message` in Stop/SubagentStop** — Ajouter dans la section hooks Stop/SubagentStop :
|
||||
> Le champ `last_assistant_message` est maintenant expose dans les inputs des evenements `Stop` et `SubagentStop` (v2.1.47+). Utile pour acceder a la reponse finale sans parser les transcripts.
|
||||
|
||||
### Phase 2 — CLI & LSP (P2, 1 session)
|
||||
|
||||
**`--from-pr` flag** — Dans la section GitHub/DevOps workflows :
|
||||
```bash
|
||||
# Resume session linked to a specific PR
|
||||
claude --from-pr 123
|
||||
# Sessions created via gh pr create are auto-linked
|
||||
```
|
||||
|
||||
**`startupTimeout` LSP** — Dans la section configuration LSP :
|
||||
```json
|
||||
{
|
||||
"lsp": {
|
||||
"servers": {
|
||||
"tsserver": { "startupTimeout": 15000 }
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**`enabledPlugins` via `--add-dir`** — Dans la section Plugins :
|
||||
> `enabledPlugins` et `extraKnownMarketplaces` peuvent etre definis dans les settings d'un repertoire `--add-dir`, permettant une politique de plugins au niveau repo.
|
||||
|
||||
### Phase 3 — Settings & Keybindings (P3, batch)
|
||||
|
||||
Mettre a jour les tableaux existants :
|
||||
- **Settings table** : `spinnerTipsOverride` (custom tips, `excludeDefault` option)
|
||||
- **Keybindings table** : `chat:newline` (configurable multi-line input)
|
||||
- **Statusline JSON** : `added_dirs` field dans l'objet `workspace`
|
||||
- **SDK reference** : `SDKRateLimitInfo` / `SDKRateLimitEvent` types
|
||||
|
||||
## Fait-Check
|
||||
|
||||
| Affirmation | Statut | Source |
|
||||
|-------------|--------|--------|
|
||||
| Releases 2.1.44-2.1.50 dates 17-21 fev 2026 | ✅ | claude-code-releases.yaml |
|
||||
| `WorktreeCreate`/`WorktreeRemove` en 2.1.50 | ✅ | claude-code-releases.yaml ligne 21 |
|
||||
| `Ctrl+F` remplace double-ESC depuis 2.1.47 | ✅ | claude-code-releases.md ligne 82 |
|
||||
| `ConfigChange` hook en 2.1.49 | ✅ | claude-code-releases.md ligne 56 |
|
||||
| `CLAUDE_CODE_SIMPLE` desactive MCP/hooks/CLAUDE.md depuis 2.1.50 | ✅ | claude-code-releases.md ligne 38 |
|
||||
| Fix glibc < 2.30 RHEL 8 en 2.1.50 | ✅ | claude-code-releases.yaml (2.1.50 highlights) |
|
||||
| Bug doc ESC lignes 5738-5741 | ✅ CONFIRME | ultimate-guide.md (verifie + corrige) |
|
||||
| Sonnet 4.5 1M retire du plan Max | ✅ | claude-code-releases.md (2.1.49 breaking) |
|
||||
|
||||
## Challenge (technical-writer)
|
||||
|
||||
- **Score maintenu** : 4/5
|
||||
- **Bug ESC sous-evalue dans l'analyse initiale** : c'est un risque operationnel reel (agents fantomes), pas un simple gap de feature. Traite en P0.
|
||||
- **3 gaps manques initialement** : `last_assistant_message`, `--from-pr`, bug ESC actif
|
||||
- **Valeur principale** : service de quality assurance/audit de couverture sur un guide de 20K lignes, pas une source de contenu primaire
|
||||
96
docs/resource-evaluations/ui-ux-pro-max-skill.md
Normal file
96
docs/resource-evaluations/ui-ux-pro-max-skill.md
Normal file
|
|
@ -0,0 +1,96 @@
|
|||
# Resource Evaluation: UI UX Pro Max Skill
|
||||
|
||||
**Date**: 2026-02-23
|
||||
**Evaluator**: Claude Code (Sonnet 4.6) + technical-writer agent challenge
|
||||
**Score**: 4/5
|
||||
|
||||
---
|
||||
|
||||
## Resource
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **URL** | https://github.com/nextlevelbuilder/ui-ux-pro-max-skill |
|
||||
| **Site** | https://ui-ux-pro-max-skill.nextlevelbuilder.io/ |
|
||||
| **Author** | Organisation "nextlevelbuilder" (anonyme) |
|
||||
| **License** | MIT |
|
||||
| **Version** | v2.2.1 (26 jan 2026) |
|
||||
| **Created** | 30 nov 2025 |
|
||||
| **Stars** | 33,658 (vérifiés gh CLI) |
|
||||
| **Forks** | 3,327 (vérifiés gh CLI) |
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Skill multi-plateforme (15 assistants AI) fournissant un moteur de design intelligence pour Claude Code et ses équivalents. Engine Python offline (BM25 sur JSON de règles locales). Feature flagship v2.0 : Design System Generator → génère MASTER.md + pages/ overrides.
|
||||
|
||||
**Contenu** : 67 styles UI, 96 palettes couleurs, 57 typographies, 25 charts, 99 UX guidelines, 100 règles industrie.
|
||||
|
||||
---
|
||||
|
||||
## Fact-Check Results
|
||||
|
||||
| Claim | Status | Source |
|
||||
|-------|--------|--------|
|
||||
| 33,658 stars | ✅ Vérifié | `gh api repos/nextlevelbuilder/ui-ux-pro-max-skill` |
|
||||
| 3,327 forks | ✅ Vérifié | gh CLI |
|
||||
| Créé 30 nov 2025 | ✅ Vérifié | `created_at` gh CLI |
|
||||
| Mis à jour 23 fev 2026 | ✅ Vérifié | `updated_at` gh CLI |
|
||||
| Site HTTP 200 | ✅ Vérifié | `curl -s -o /dev/null -w "%{http_code}"` |
|
||||
| v2.2.1 latest | ✅ Vérifié | Perplexity + releases page |
|
||||
| 67 styles | ⚠️ README claim | Non compté individuellement |
|
||||
| 96 palettes | ⚠️ README claim | Non compté individuellement |
|
||||
| Python 80.6%, TS 18% | ✅ Vérifié | GitHub languages bar |
|
||||
| BM25 engine | ✅ Vérifié | README technique |
|
||||
| Auteur identifié | ⚠️ Org anonyme | "nextlevelbuilder", aucun individu nommé |
|
||||
|
||||
---
|
||||
|
||||
## Gap Analysis
|
||||
|
||||
| Aspect | Cette ressource | Guide (avant intégration) |
|
||||
|--------|----------------|--------------------------|
|
||||
| Skill design UI/UX spécialisé | ✅ Leader du marché | ❌ Absent |
|
||||
| Design System Generator | ✅ Feature flagship | ❌ Absent |
|
||||
| Multi-plateforme AI (15 outils) | ✅ Couvert | ⚠️ Partiel |
|
||||
| Community skills section | ✅ Exemple majeur | ✅ Autres entrées présentes |
|
||||
|
||||
---
|
||||
|
||||
## Challenge (technical-writer agent)
|
||||
|
||||
L'agent a challengé le score et le plan avec ces arguments :
|
||||
|
||||
1. **Placement** : Section 5 "Skills" peut induire en erreur — ce n'est pas un skill Claude Code natif mais un outil externe avec CLI Python. Reconnu dans la documentation (sous-section dédiée "Community Skill Repositories", pas dans la mécanique de création de skills).
|
||||
|
||||
2. **Score ajusté initial** : 2.75/5 proposé par l'agent (avant vérification des stars). Post-vérification, 4/5 maintenu car traction organique confirmée.
|
||||
|
||||
3. **Sécurité** : Note `npm install -g` insuffisante → enrichie dans la doc finale avec alternative git clone et instructions d'audit.
|
||||
|
||||
4. **Protocole de test recommandé** (non exécuté avant intégration) :
|
||||
- Star history curve (star-history.com) → vérifier organicité
|
||||
- `npm view uipro-cli scripts` → chercher preinstall/postinstall suspect
|
||||
- Clone + lecture `search.py` head → vérifier absence de requêtes réseau runtime
|
||||
- Test Design System Generator en environnement isolé
|
||||
|
||||
---
|
||||
|
||||
## Decision
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Score** | 4/5 |
|
||||
| **Action** | Intégré dans `guide/ultimate-guide.md §5.5` |
|
||||
| **Placement** | Section 5.5 Community Skill Repositories — "Design Intelligence: UI UX Pro Max" |
|
||||
| **Confidence** | Haute (traction vérifiée) / Moyenne (claims fonctionnels non audités) |
|
||||
| **Tests pending** | Star history curve, npm audit, search.py source review |
|
||||
|
||||
---
|
||||
|
||||
## References
|
||||
|
||||
- Perplexity searches : jimmysong.io mention, mcpmarket.com listing, YouTube tutorial (fev 2026), hylarucoder benchmark repo
|
||||
- gh CLI verification : stars, forks, dates
|
||||
- README v2.0 : Design System Generator workflow documenté
|
||||
- Technical-writer agent challenge : session 2026-02-23
|
||||
Loading…
Add table
Add a link
Reference in a new issue