docs: add AI productivity research, trust calibration, and exploration workflow

## New Content

### Trust & Verification (ultimate-guide.md)
- Section 1.7 "Trust Calibration: When and How Much to Verify" (~155 lines)
  - Research-backed stats (ACM, Veracode, CodeRabbit, Cortex.io)
  - Verification spectrum by code type
  - Solo vs Team strategies with workflow diagrams
  - "Prove It Works" checklist
- New pitfall: "Trust AI output without proportional verification"
- CLAUDE.md size guideline: 4-8KB optimal, >16K degrades coherence

### AI Productivity (learning-with-ai.md)
- Section "The Reality of AI Productivity" (~55 lines)
  - Productivity curve phases (Wow Effect → Targeted Gains → Plateau)
  - High-gain vs low/negative-gain task categorization
  - Team success factors
- Productivity trajectory table by pattern (Dependent/Avoidant/Augmented)
- 5 new sources (GitHub, McKinsey, Stack Overflow, Uplevel, DORA)

### Session Limits (architecture.md)
- "Session Degradation Limits" section
  - Turn limits (15-25), token thresholds (80-100K)
  - Success rates by scope (1-3 files: ~85%, 8+ files: ~40%)

### Exploration Workflow
- NEW: guide/workflows/exploration-workflow.md
  - Anti-anchoring prompts, 3-5 approaches pattern
- iterative-refinement.md: Script Generation Workflow (3-7 iteration pattern)
- anchor-catalog.md: Anti-Anchoring Techniques, Exploration/Iteration Prompts

### Reference Updates
- adoption-approaches.md: Empirical data section
- reference.yaml: New deep_dive entries, updated line numbers

Sources: MetalBear engineering blog, arXiv studies, Addy Osmani (Jan 2026)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Florian BRUNIAUX 2026-01-19 19:16:33 +01:00
parent a9d302326c
commit fd17414abb
10 changed files with 775 additions and 20 deletions

View file

@ -237,6 +237,45 @@ LLMs are statistical pattern matchers. When you use **precise technical vocabula
---
## Prompting Patterns
### Anti-Anchoring Techniques
LLMs can fixate on their first suggestion, narrowing your solution space. These patterns combat anchoring bias:
| Pattern | Prompt Template | Effect |
|---------|-----------------|--------|
| Fresh start | "Ignore any prior ideas. Generate 4 novel approaches to [X]" | Forces diversity |
| Reflection loop | "Generate 3 options, then critique each, then recommend" | Self-correction |
| Quantified comparison | "Rank by [metric1], [metric2], [metric3] with scores 1-10" | Objective trade-offs |
| Devil's advocate | "What are the strongest arguments against your recommendation?" | Surface hidden costs |
| Constraint flip | "Now solve with [opposite constraint]" | Expand solution space |
### Exploration Prompts
Use these when you need multiple approaches before committing:
| Goal | Semantic Anchor Prompt |
|------|------------------------|
| Architecture choice | "Compare [A], [B], [C] using C4 model criteria: context fit, container complexity, component count" |
| Performance trade-off | "Analyze time complexity (Big O), space complexity, and cache-friendliness for each approach" |
| Team fit | "Evaluate learning curve, debugging difficulty, and ecosystem maturity (1-10 scale)" |
| Risk assessment | "For each option: what's the worst-case failure mode and recovery cost?" |
### Iteration Prompts
For progressive refinement of scripts and automation:
| Stage | Prompt Pattern |
|-------|----------------|
| Initial | "Create a [language] script that [goal]. Include basic error handling." |
| Constrain | "Add: [specific constraint]. Remove: [unwanted behavior]." |
| Harden | "Add input validation, logging, and handle edge case: [specific case]." |
| Optimize | "Optimize for [metric]. Target: [specific threshold]." |
| Document | "Add usage examples and inline comments for non-obvious logic." |
---
## CLAUDE.md Template with Semantic Anchors
```markdown