docs: update metadata and statistics for v3.9.9

Update CHANGELOG, README, and workflow docs to reflect latest additions. Changes: 1. CHANGELOG.md - 4 new entries under [Unreleased] → Added: * llms.txt Standard Documentation (Section 9.18.4) * Background Tasks Workflow (Section 9.5) * Chrome DevTools MCP Server (mcp-servers-ecosystem.md) * Convention-Over-Configuration for AI (Section 9.18.1) - Each entry with line numbers, resources, gaps addressed 2. README.md statistics - Guide lines: 16K → 19K (actual: 18,820 lines) - Templates: 107 → 111 (verified count) - Evaluations: 55 → 56 (wasp-fullstack-essentials-eval.md) - Updated in 8 locations: hero, badges, mermaid diagram, structure 3. guide/workflows/agent-teams-quick-start.md - Improved task delegation clarity (Content Scope, Index Scope labels) - Enhanced context boundaries in multi-file operations Statistics verification: - Templates: find examples -type f | wc -l → 111 - Guide lines: wc -l guide/ultimate-guide.md → 18,820 - Evaluations: docs/resource-evaluations/README.md → 56 Related commits: - 783c43b: llms.txt conceptual documentation - 17846b1: Background tasks + Chrome DevTools + convention-over-config Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-09 10:07:12 +01:00 · 2026-02-09 10:07:12 +01:00 · 94b9ad4f89
commit 94b9ad4f89
parent baebe23816
4 changed files with 86 additions and 37 deletions
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -64,6 +64,49 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
  - Hook events (TeammateIdle, TaskCompleted)
  - Agent memory field, Xcode integration, adaptive thinking
  - Updated: 2026-02-09
+- **llms.txt Standard Documentation** (Section 9.18.4): AI-optimized documentation indexing
+  - **Concept explanation**: llms.txt as documentation discovery standard for LLMs
+  - **Format and structure**: Plain text index at `/llms.txt` or `/machine-readable/llms.txt`
+  - **Complementarity with MCP**: Clarifies llms.txt (static index) vs Context7 MCP (runtime lookup)
+  - **Implementation examples**: Minimal and advanced patterns with line numbers
+  - **CLAUDE.md integration**: How llms.txt and CLAUDE.md serve different purposes
+  - **Repository example**: References this guide's own `machine-readable/llms.txt` implementation
+  - Section: Documentation Formats for Agents (line 14544)
+  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
+  - Source: llmstxt.org specification (official standard)
+  - Gap addressed: Repository had llms.txt file without conceptual documentation
+- **Background Tasks Workflow** (Section 9.5): Fullstack development patterns with Ctrl+B
+  - **When to background**: 5 scenarios (dev server, test watcher, build, migration, docker)
+  - **Fullstack workflow pattern**: Dev server backgrounded while iterating on frontend
+  - **Real-world example**: API + frontend iteration maintaining tight feedback loops
+  - **Context rot prevention**: `/tasks` monitoring strategies
+  - **Limitations**: No foreground command, session-scoped tasks, output visibility
+  - **Teleportation integration**: Background tasks not transferred, restart required
+  - **Disable flag**: `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` environment variable (v2.1.4+)
+  - Section: Background Tasks for Fullstack Development (line 11057)
+  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
+  - Gap addressed: Ctrl+B documented as feature, now complete workflow strategy
+- **Chrome DevTools MCP Server** (mcp-servers-ecosystem.md): Debugging and inspection capabilities
+  - **Official Anthropic server**: Chrome DevTools Protocol integration
+  - **Use case**: Debugging web apps, runtime inspection, complements Playwright MCP
+  - **Key features**: Console access, network monitoring, DOM inspection, JS execution, profiling
+  - **Comparison table**: Chrome DevTools (debugging) vs Playwright (testing)
+  - **Setup and limitations**: Manual Chrome launch with remote debugging port
+  - Section: Browser Automation (line 418)
+  - Statistics: 3 browser servers (was 2), 6 official servers (was 5)
+  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
+  - npm: @modelcontextprotocol/server-chrome-devtools
+- **Convention-Over-Configuration for AI** (Section 9.18.1): Framework selection impact
+  - **Problem**: Custom architectures require extensive CLAUDE.md documentation
+  - **Solution**: Opinionated frameworks reduce agent cognitive load through conventions
+  - **Comparison table**: Custom vs opinionated architectures (file organization, routing, testing)
+  - **Framework examples**: Next.js, Rails, Phoenix, Django with convention benefits
+  - **Real-world impact**: Fewer mistakes, faster boilerplate, smaller CLAUDE.md files
+  - **Trade-offs**: Faster onboarding vs architectural flexibility
+  - **CLAUDE.md connection**: Convention-over-config directly reduces token requirements
+  - Section: Convention-Over-Configuration for AI Agents (line 14380)
+  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
+  - Gap addressed: Existing AX framework concept reinforced with framework angle

 ### Changed

--- a/README.md
+++ b/README.md
@ -7,7 +7,7 @@
 <p align="center">
  <a href="https://github.com/FlorianBruniaux/claude-code-ultimate-guide/stargazers"><img src="https://img.shields.io/github/stars/FlorianBruniaux/claude-code-ultimate-guide?style=for-the-badge" alt="Stars"/></a>
  <a href="./quiz/"><img src="https://img.shields.io/badge/Quiz-257_questions-orange?style=for-the-badge" alt="Quiz"/></a>
-  <a href="./examples/"><img src="https://img.shields.io/badge/Templates-107-green?style=for-the-badge" alt="Templates"/></a>
+  <a href="./examples/"><img src="https://img.shields.io/badge/Templates-111-green?style=for-the-badge" alt="Templates"/></a>
 </p>

 <p align="center">
@ -15,7 +15,7 @@
  <a href="https://zread.ai/FlorianBruniaux/claude-code-ultimate-guide"><img src="https://img.shields.io/badge/Ask_Zread-_.svg?style=flat&color=00b0aa&labelColor=000000&logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPHN2ZyB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIHZpZXdCb3g9IjAgMCAxNiAxNiIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4KPHBhdGggZD0iTTQuOTYxNTYgMS42MDAxSDIuMjQxNTZDMS44ODgxIDEuNjAwMSAxLjYwMTU2IDEuODg2NjQgMS42MDE1NiAyLjI0MDFWNC45NjAxQzEuNjAxNTYgNS4zMTM1NiAxLjg4ODEgNS42MDAxIDIuMjQxNTYgNS42MDAxSDQuOTYxNTZDNS4zMTUwMiA1LjYwMDEgNS42MDE1NiA1LjMxMzU2IDUuNjAxNTYgNC45NjAxVjIuMjQwMUM1LjYwMTU2IDEuODg2NjQgNS4zMTUwMiAxLjYwMDEgNC45NjE1NiAxLjYwMDFaIiBmaWxsPSIjZmZmIi8%2BCjxwYXRoIGQ9Ik00Ljk2MTU2IDEwLjM5OTlIMi4yNDE1NkMxLjg4ODEgMTAuMzk5OSAxLjYwMTU2IDEwLjY4NjQgMS42MDE1NiAxMS4wMzk5VjEzLjc1OTlDMS42MDE1NiAxNC4xMTM0IDEuODg4MSAxNC4zOTk5IDIuMjQxNTYgMTQuMzk5OUg0Ljk2MTU2QzUuMzE1MDIgMTQuMzk5OSA1LjYwMTU2IDE0LjExMzQgNS42MDE1NiAxMy43NTk5VjExLjAzOTlDNS42MDE1NiAxMC42ODY0IDUuMzE1MDIgMTAuMzk5OSA0Ljk2MTU2IDEwLjM5OTlaIiBmaWxsPSIjZmZmIi8%2BCjxwYXRoIGQ9Ik0xMy43NTg0IDEuNjAwMUgxMS4wMzg0QzEwLjY4NSAxLjYwMDEgMTAuMzk4NCAxLjg4NjY0IDEwLjM5ODQgMi4yNDAxVjQuOTYwMUMxMC4zOTg0IDUuMzEzNTYgMTAuNjg1IDUuNjAwMSAxMS4wMzg0IDUuNjAwMUgxMy43NTg0QzE0LjExMTkgNS42MDAxIDE0LjM5ODQgNS4zMTM1NiAxNC4zOTg0IDQuOTYwMVYyLjI0MDFDMTQuMzk4NCAxLjg4NjY0IDE0LjExMTkgMS42MDAxIDEzLjc1ODQgMS42MDAxWiIgZmlsbD0iI2ZmZiIvPgo8cGF0aCBkPSJNNCAxMkwxMiA0TDQgMTJaIiBmaWxsPSIjZmZmIi8%2BCjxwYXRoIGQ9Ik00IDEyTDEyIDQiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIxLjUiIHN0cm9rZS1saW5lY2FwPSJyb3VuZCIvPgo8L3N2Zz4K&logoColor=ffffff" alt="Ask Zread"/></a>
 </p>

-> **Claude Code (Anthropic): the learning curve, solved.** ~16K-line guide + 107 templates + 257 quiz questions + 22 event hooks + 55 resource evaluations. Beginner → Power User.
+> **Claude Code (Anthropic): the learning curve, solved.** ~19K-line guide + 111 templates + 257 quiz questions + 22 event hooks + 56 resource evaluations. Beginner → Power User.

 ---

@ -66,12 +66,12 @@ Save as `CLAUDE.md` in your project root. Claude reads it automatically.
 graph LR
    root[📦 Repository<br/>Root]

-    root --> guide[📖 guide/<br/>16K lines]
-    root --> examples[📋 examples/<br/>106 templates]
+    root --> guide[📖 guide/<br/>19K lines]
+    root --> examples[📋 examples/<br/>111 templates]
    root --> quiz[🧠 quiz/<br/>257 questions]
    root --> tools[🔧 tools/<br/>utils]
    root --> machine[🤖 machine-readable/<br/>AI index]
-    root --> docs[📚 docs/<br/>55 evaluations]
+    root --> docs[📚 docs/<br/>56 evaluations]

    style root fill:#d35400,stroke:#e67e22,stroke-width:3px,color:#fff
    style guide fill:#2980b9,stroke:#3498db,stroke-width:2px,color:#fff
@ -88,7 +88,7 @@ graph LR
 ```
 📦 claude-code-ultimate-guide/
 │
-├─ 📖 guide/              Core Documentation (~16K lines)
+├─ 📖 guide/              Core Documentation (~19K lines)
 │  ├─ ultimate-guide.md   Complete reference, 10 sections
 │  ├─ cheatsheet.md       1-page printable
 │  ├─ architecture.md     How Claude Code works internally
@ -96,7 +96,7 @@ graph LR
 │  ├─ mcp-servers-ecosystem.md  Official & community MCP servers
 │  └─ workflows/          Step-by-step guides
 │
-├─ 📋 examples/           107 Production Templates
+├─ 📋 examples/           111 Production Templates
 │  ├─ agents/             6 custom AI personas
 │  ├─ commands/           18 slash commands
 │  ├─ hooks/              18 security hooks (bash + PowerShell)
@ -383,7 +383,7 @@ Claude Code sends your prompts, file contents, and MCP results to Anthropic serv

 | File | Purpose | Time |
 |------|---------|------|
-| **[Ultimate Guide](./guide/ultimate-guide.md)** | Complete reference (~16K lines), 10 sections | ~4 hours |
+| **[Ultimate Guide](./guide/ultimate-guide.md)** | Complete reference (~19K lines), 10 sections | ~4 hours |
 | **[Cheat Sheet](./guide/cheatsheet.md)** | 1-page printable reference | 5 min |
 | **[Visual Reference](./guide/visual-reference.md)** | 20 ASCII diagrams for key concepts | 5 min |
 | **[Architecture](./guide/architecture.md)** | How Claude Code works internally | 25 min |
@ -401,7 +401,7 @@ Claude Code sends your prompts, file contents, and MCP results to Anthropic serv
 | **[Claude Code Releases](./guide/claude-code-releases.md)** | Official release history | 10 min |

 <details>
-<summary><strong>Examples Library</strong> (106 templates)</summary>
+<summary><strong>Examples Library</strong> (111 templates)</summary>

 **Agents** (6): [code-reviewer](./examples/agents/code-reviewer.md), [test-writer](./examples/agents/test-writer.md), [security-auditor](./examples/agents/security-auditor.md), [refactoring-specialist](./examples/agents/refactoring-specialist.md), [output-evaluator](./examples/agents/output-evaluator.md), [devops-sre](./examples/agents/devops-sre.md) ⭐

--- a/guide/ultimate-guide.md
+++ b/guide/ultimate-guide.md
@ -3769,15 +3769,15 @@ impact (High/Medium/Low) without considering security or maintainability
 trade-offs.
 ```

-**When to split roles:**
- Code reviews requiring 3+ distinct expertise areas
- Architecture decisions with competing concerns (performance vs. security vs. DX)
- Migration planning where different stakeholders have different priorities
+**When to use scope-focused agents:**
+- Analysis requiring 3+ distinct context boundaries (security scope, perf scope, API scope)
+- Competing concerns that benefit from isolated evaluation (performance vs. security vs. DX)
+- Large codebases where full context would pollute analysis of specific aspects

-**When NOT to split:**
- Simple reviews (one agent covers all aspects)
+**When NOT to use scope-focused agents:**
+- Simple reviews (one agent with full context covers all aspects)
 - Time-constrained situations (overhead of synthesis outweighs benefit)
- Tasks where perspectives aren't genuinely distinct
+- Tasks where scopes aren't genuinely independent (overlapping context needed)

 ### The Philosophy

--- a/guide/workflows/agent-teams-quick-start.md
+++ b/guide/workflows/agent-teams-quick-start.md
@ -206,20 +206,23 @@ Team: doc-update (3 agents)
 **Copy-paste prompt**:
 ```
 > Update documentation for new "[FEATURE NAME]" feature:
-> - Content writer: Write section [X.Y] in guide/ultimate-guide.md with:
+> - Content Scope: Write section [X.Y] in guide/ultimate-guide.md with:
 >   - Overview (what/why/when)
 >   - 2-3 concrete examples
 >   - Best practices + gotchas
 >   - Links to related sections
-> - Index updater: Update:
+>   Context: guide/ultimate-guide.md section [X.Y] only
+> - Index Scope: Update:
 >   - guide/ultimate-guide.md TOC (add section [X.Y])
 >   - machine-readable/reference.yaml (add entry with line numbers)
 >   - README.md navigation (add link if major feature)
-> - Consistency checker: Verify:
+>   Context: Index files only (TOC, reference.yaml, README.md)
+> - Consistency Scope: Verify:
 >   - All cross-references resolve correctly
 >   - Line numbers in reference.yaml match actual content
 >   - Anchors in README point to correct sections
 >   - No broken internal links
+>   Context: All modified files for cross-reference validation
 ```

 **ROI**:
@ -259,22 +262,25 @@ Team: security-pr-review (3 agents)

 **Copy-paste prompt**:
 ```
-> Review PR #[NUMBER] with security focus:
-> - Rust expert: Check:
+> Review PR #[NUMBER] with scope-focused analysis:
+> - Rust Scope: Check:
 >   - Ownership patterns (prefer &str over String, minimize clones)
 >   - Error handling (anyhow::Result with .context(), no unwrap outside tests)
 >   - Idiomatic code (impl after type, #[cfg(test)] mod tests)
 >   - Clippy compliance (zero warnings)
-> - Security auditor: Scan for:
+>   Context: All modified .rs files
+> - Security Scope: Scan for:
 >   - Command injection (shell escapes, argument sanitization)
 >   - Token/credential leaks (hardcoded secrets, logs, error messages)
 >   - Input sanitization (path traversal, regex DoS)
 >   - File operations (path validation, permissions)
-> - Perf analyzer: Review:
+>   Context: Input handling, auth, file I/O code
+> - Performance Scope: Review:
 >   - Unnecessary allocations (String::from vs &str)
 >   - Async patterns (spawn_blocking for CPU-bound work)
 >   - Compiled regex (lazy_static! for hot paths)
 >   - Algorithm complexity (O(n) vs O(n²))
+>   Context: Hot paths, loops, async functions
 ```

 **ROI**:
@ -326,7 +332,7 @@ Verdict: ✅ Critical security issues caught, PR requires revision
 **Use Agent Teams when**:
 - ✅ You'd naturally think "I should check X, Y, and Z"
 - ✅ High stakes (production release, external contributor, security-sensitive)
- ✅ Multi-domain expertise needed (Rust + Security + Performance)
+- ✅ Multi-scope analysis needed (Rust scope + Security scope + Performance scope)
 - ✅ Cross-file consistency matters (links, counts, versions sync)
 - ✅ Parallel work possible (independent tasks, no sequential dependency)

@ -351,11 +357,11 @@ claude

 # 3. Create team (prompt template)
 > Create a team to [TASK]:
-> - Agent 1 ([ROLE]): [SPECIFIC MISSION]
-> - Agent 2 ([ROLE]): [SPECIFIC MISSION]
-> - Agent 3 ([ROLE]): [SPECIFIC MISSION]
+> - Agent 1 ([SCOPE/CONTEXT]): [SPECIFIC MISSION]
+> - Agent 2 ([SCOPE/CONTEXT]): [SPECIFIC MISSION]
+> - Agent 3 ([SCOPE/CONTEXT]): [SPECIFIC MISSION]
 >
-> [CONTEXT/FILES TO REVIEW]
+> [FILES/DIRECTORIES TO ANALYZE]

 # 4. Observe (optional)
 # Shift+Up/Down to see individual agent outputs
@ -381,19 +387,19 @@ claude
 #### Security PR Review (RTK)

 ```
-> Review PR #42 with security focus:
-> - Rust expert: Check ownership patterns, error handling (anyhow/thiserror), idiomatic code in modified files
-> - Security auditor: Scan for injection risks, token leaks, input sanitization
-> - Perf analyzer: Review allocations, async patterns, compiled regex
+> Review PR #42 with scope-focused analysis:
+> - Rust Scope: Check ownership patterns, error handling (anyhow/thiserror), idiomatic code in modified files (context: src/**/*.rs)
+> - Security Scope: Scan for injection risks, token leaks, input sanitization (context: auth, input handling code)
+> - Performance Scope: Review allocations, async patterns, compiled regex (context: hot paths, loops)
 ```

 #### Multi-File Doc Update

 ```
 > Update documentation for new "Agent Teams Quick Start" feature:
-> - Content writer: Write guide/workflows/agent-teams-quick-start.md with overview, 4 patterns, decision matrix, metrics
-> - Index updater: Update guide/ultimate-guide.md (add reference section 9.20), machine-readable/reference.yaml (add entry), CHANGELOG.md (add "Added" entry)
-> - Consistency checker: Verify all cross-refs work, line numbers match, no broken links
+> - Content Scope: Write guide/workflows/agent-teams-quick-start.md with overview, 4 patterns, decision matrix, metrics
+> - Index Scope: Update guide/ultimate-guide.md (add reference section 9.20), machine-readable/reference.yaml (add entry), CHANGELOG.md (add "Added" entry)
+> - Consistency Scope: Verify all cross-refs work, line numbers match, no broken links (context: all modified files)
 ```

 #### Landing Sync Validation
@ -473,8 +479,8 @@ Verdict: ✅ High value for pre-release audits
 ```

 **Adjust prompts** if metrics fail:
- Low convergence (<30%) → Agents too specialized, overlap prompts more
- No unique insights → Agents too similar, diversify expertise
+- Low convergence (<30%) → Scopes too narrow, overlap context boundaries more
+- No unique insights → Scopes too similar, diversify analysis angles
 - High false positives (>20%) → Prompts too vague, add concrete criteria

 ---