@su-record/vibe 2.9.2 → 2.9.3

package/commands/vibe.analyze.md

@@ -1,54 +1,72 @@
 ---
-description: Analyze project or specific feature/module
-argument-hint: "feature-name" or --code or --deps or --arch
+description: Analyze any target — code, document, website, or Figma design
+argument-hint: "feature-name" or file.pdf or https://... or --code or --deps or --arch
 ---
 
 # /vibe.analyze
 
-Analyze project or specific feature/module.
+Analyze any target: source code, documents, websites, or Figma designs.
 
 ## Usage
 
 ```
 /vibe.analyze                  # Full project quality analysis
-/vibe.analyze "login"          # Login related code exploration + context collection
+/vibe.analyze "login"          # Feature/module code exploration + context collection
 /vibe.analyze --code           # Code quality analysis only
 /vibe.analyze --deps           # Dependency analysis only
 /vibe.analyze --arch           # Architecture analysis only
+/vibe.analyze report.pdf       # Document analysis (PDF, markdown, slides)
+/vibe.analyze https://example.com  # Website analysis (UX, tech, SEO, accessibility)
+/vibe.analyze https://figma.com/design/...  # Figma design analysis
 ```
 
+## Input Type Auto-Detection
+
+Determine analysis mode from the argument pattern:
+
+| Pattern | Mode | Description |
+|---------|------|-------------|
+| `*.pdf`, `*.docx`, `*.pptx`, `*.md` (file path) | **Document** | Structure, content, quality, applicability |
+| `http(s)://figma.com/*` | **Figma** | Design structure, components, tokens |
+| `http(s)://*` | **Website** | UX, tech stack, SEO, accessibility |
+| `--code`, `--deps`, `--arch` | **Project Quality** | Code quality, dependencies, architecture |
+| String (feature name) | **Feature/Module** | Source code exploration + flow analysis |
+| No argument | **Project Quality** | Full project analysis |
+
+**Detection order**: file extension → URL pattern → flag → string.
+
 ## File Reading Policy (Mandatory)
 
-- **SPEC/Feature 파일**: 반드시 `Read` 도구로 전체 파일을 읽을 것 (Grep 금지)
-- **소스코드 파일**: 분석 대상 파일은 반드시 `Read` 도구로 전체 읽은 후 분석할 것
-- **Grep 사용 제한**: 파일 위치 탐색(어떤 파일에 있는지 찾기)에만 사용. 파일 내용 파악에는 반드시 Read 사용
-- **에이전트 spawn 시**: 프롬프트에 "대상 파일을 Read 도구로 전체 읽은 후 분석하라"를 반드시 포함할 것
-- **부분 읽기 금지**: Grep 결과의 주변 몇 줄만 보고 판단하지 말 것. 전체 맥락을 파악해야 정확한 분석 가능
+- **SPEC/Feature files**: Always use `Read` tool for the full file (never Grep for content)
+- **Source files**: Read the entire file before analyzing (no partial reads)
+- **Grep restriction**: Use only for locating files, not for understanding content
+- **Agent prompts**: Always include "Read target files in full before analyzing"
+- **No partial analysis**: Never judge a file by a few lines around a Grep match
 
 ## Context Reset
 
 **When this command runs, previous conversation is ignored.**
-- Explore and analyze code from scratch like new session
-- Base conversation only on newly collected information from this analysis
+- Explore and analyze from scratch like a new session
+- Base analysis only on newly collected information
 
 ---
 
-> **⏱️ Timer**: Call `getCurrentTime` tool at the START. Record the result as `{start_time}`.
+> **Timer**: Record start time at the beginning. Include elapsed time in the final report.
 
 ## Mode 1: Feature/Module Analysis (`/vibe.analyze "feature-name"`)
 
 ### Goal
 
-**Explore all source code** related to user's requested feature/module and **analyze flow** to:
+Explore all source code related to the requested feature/module and analyze flow to:
 1. Understand current implementation status
-2. Understand code structure and dependencies
-3. Build context for immediate response to future development/modification requests
+2. Map code structure and dependencies
+3. Build context for future development/modification requests
 
 ### Process
 
 #### 1. Request Analysis
 
-Extract key keywords from user request:
+Extract keywords from the user request:
 - Feature name (e.g., login, feed, payment)
 - Action (e.g., create, read, update, delete)
 - Scope (e.g., backend only, frontend only, full)
@@ -70,36 +88,34 @@ Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack:
 **MANDATORY: Always use explorer sub-agents. Never explore in main session.**
 
 > Why: 3 explorer-low agents return ~600 tokens of summaries to main session.
-> Direct Glob/Grep/Read in main session would add 5-15K tokens of raw file content.
+> Direct Glob/Grep/Read in main session would add 5-15K tokens of raw content.
 
-**Parallel exploration (ALL tasks in ONE message):**
+**Parallel exploration (ALL in ONE message):**
 
 ```text
-# 3 explorer agents in parallel (single message, multiple tool calls)
-Task(subagent_type="explorer-low", model="haiku",
-  prompt="Find all [FEATURE] related API endpoints in this project. List file paths, HTTP methods, routes, and auth requirements.")
+Agent(subagent_type="explorer-low", model="haiku",
+  prompt="Find all [FEATURE] related API endpoints. List file paths, HTTP methods, routes, and auth requirements.")
 
-Task(subagent_type="explorer-low", model="haiku",
-  prompt="Find all [FEATURE] related services, business logic, and utility functions. Map dependencies between them.")
+Agent(subagent_type="explorer-low", model="haiku",
+  prompt="Find all [FEATURE] related services, business logic, and utility functions. Map dependencies.")
 
-Task(subagent_type="explorer-low", model="haiku",
+Agent(subagent_type="explorer-low", model="haiku",
   prompt="Find all [FEATURE] related data models, schemas, and database queries. Document relationships and key fields.")
 ```
 
-**Additional exploration (scale by project size):**
+**Scale for large projects (6+ related files):**
 
 ```text
-# Large projects (6+ related files) — add 2 more in parallel
-Task(subagent_type="explorer-low", model="haiku",
+Agent(subagent_type="explorer-low", model="haiku",
   prompt="Find all test files related to [FEATURE]. Identify tested vs untested paths.")
 
-Task(subagent_type="explorer-low", model="haiku",
+Agent(subagent_type="explorer-low", model="haiku",
   prompt="Analyze [FEATURE] configuration, environment variables, and external integrations.")
 ```
 
 **After all agents return:**
-- Synthesize results → proceed to Flow Analysis (Step 4)
-- Only Read specific files in main session when agent summary needs clarification
+- Synthesize results → proceed to Flow Analysis
+- Only Read specific files in main session when agent summaries need clarification
 
 #### 4. Flow Analysis
 
@@ -109,7 +125,7 @@ Task(subagent_type="explorer-low", model="haiku",
 - Authentication/authorization requirements
 
 **Business Logic:**
-- Core methods and roles
+- Core methods and their roles
 - Validation rules
 - External service integrations
 
@@ -118,244 +134,384 @@ Task(subagent_type="explorer-low", model="haiku",
 - Relationships (1:N, N:M)
 - Key query patterns
 
-#### 5. Output Analysis Results
+#### 5. Output
 
 ```markdown
 ## [feature-name] Analysis Results
 
 ### Overview
-- **Feature description**: [one-line summary]
-- **Implementation status**: [Complete/In progress/Not implemented]
-- **Related files**: N files
+- **Feature**: [one-line summary]
+- **Status**: [Complete / In progress / Not implemented]
+- **Files**: N related files
 
 ### Structure
 
 #### API Endpoints
 | Method | Path | Description | Auth |
 |--------|------|-------------|------|
-| POST | /api/v1/auth/login | Login | - |
+| POST | /api/v1/auth/login | User login | None |
 
 #### Core Services
 - `auth_service.py`: Authentication logic
-  - `login()`: Login processing
-  - `verify_token()`: Token verification
+  - `login()`: Processes login
+  - `verify_token()`: Validates JWT
 
 #### Data Models
 - `User`: User table
   - Key fields: id, email, password_hash
   - Relationships: Session (1:N)
 
-### Reference File List
+### Reference Files
 - src/api/auth/router.py:L10-50
 - src/services/auth_service.py:L1-100
 ```
 
-#### 6. Complete & Next Action
+#### 6. Next Steps
+
+After analysis, suggest mode-specific follow-up actions:
+
+**After code/feature analysis:**
+
+| Task Scope | Approach |
+|------------|----------|
+| Simple fix (1-2 files) | Plan Mode |
+| Complex feature (3+ files) | `/vibe.spec` |
+
+**After document analysis:**
+
+| Goal | Approach |
+|------|----------|
+| Apply findings to project | `/vibe.spec "feature-name"` |
+| Derive improvement direction | Plan Mode |
+| Compare with another source | `/vibe.analyze [other target]` |
+
+**After website analysis:**
+
+| Goal | Approach |
+|------|----------|
+| Build similar product | `/vibe.spec` |
+| Improve existing UI | `/vibe.figma` |
+| Compare with another site | `/vibe.analyze [other URL]` |
+
+Wait for user's choice before proceeding.
+
+---
+
+## Mode 2: Document Analysis (PDF, Markdown, Slides)
+
+### Goal
+
+Analyze document **structure, key content, quality, and applicability** to:
+1. Extract and organize information from the document
+2. Map relevance to the current project
+3. Suggest follow-up actions (development, improvement, application)
+
+### Process
+
+#### 1. Read Document
+
+- **PDF**: Use `Read` tool with `pages` parameter (split large documents into chunks of 20 pages)
+- **Markdown/Text**: Use `Read` tool for the full file
+- **Image-heavy documents**: Analyze visual elements (slides, diagrams) alongside text
+
+#### 2. Classify Document Type
+
+| Type | Analysis Focus |
+|------|---------------|
+| Technical spec | API definitions, data models, sequence diagrams |
+| Presentation/slides | Key claims, frameworks, case studies |
+| PRD/requirements | User stories, acceptance criteria, scope |
+| Business document | Strategy, decision points, action items |
+| Research/academic | Methodology, conclusions, applicability |
+
+#### 3. Analyze Content (Parallel Sub-Agents)
+
+```text
+Agent(subagent_type="general-purpose", model="haiku",
+  prompt="Read the document at [PATH] and extract: 1) Section structure / table of contents 2) Key concepts and definitions 3) Main arguments or claims. Use the Read tool with pages parameter for PDFs.")
+
+Agent(subagent_type="general-purpose", model="haiku",
+  prompt="Read the document at [PATH] and extract: 1) Actionable recommendations 2) Data points, metrics, examples 3) References to external resources. Use the Read tool with pages parameter for PDFs.")
+```
+
+#### 4. Project Relevance Analysis
+
+- Map how document content applies to the current project
+- Check if patterns/tools/techniques mentioned are already implemented
+- Gap analysis: document recommendations vs current project state
 
-After analysis:
-1. Output analysis summary (include `⏱️ Started: {start_time}` and `⏱️ Completed: {getCurrentTime 결과}`)
-2. **Ask user to choose workflow** when development is requested:
+#### 5. Output
 
+```markdown
+## [Document Name] Analysis
+
+### Overview
+- **Type**: [Presentation / Technical spec / PRD / ...]
+- **Topic**: [one-line summary]
+- **Pages/Sections**: N
+- **Audience**: [Developers / PMs / Executives / ...]
+
+### Key Content
+1. **[Concept 1]**: Description
+2. **[Concept 2]**: Description
+
+### Frameworks/Models (if any)
+- [Systematic structure presented in the document]
+
+### Project Relevance
+| Recommendation | Current State | Gap |
+|----------------|---------------|-----|
+| ... | ... | ... |
+
+### Key Insights
+- [Most important takeaway]
+
+### Suggested Actions
+1. ...
 ```
-## Next Steps
 
-Choose a workflow to proceed with development:
+#### Fallback
 
-| Task Scope | Recommended Approach |
-|----------|----------|
-| Simple fix (1-2 files) | Plan Mode |
-| Complex feature (3+ files, research/verification needed) | /vibe.spec |
+If `Read` fails for a document format:
+1. Check file extension and try alternative parsing
+2. If binary format is unsupported, inform user and suggest converting to PDF/markdown
+3. Never produce an analysis based on partial or failed reads
+
+---
+
+## Mode 3: Website Analysis (URL)
+
+### Goal
 
-1. `/vibe.spec "feature-name"` - VIBE workflow (parallel research + SPEC verification)
-2. Plan Mode - Quick implementation (for simple tasks)
+Analyze website **tech stack, UX/UI, SEO, accessibility, and performance** to:
+1. Understand technical implementation
+2. Identify improvement opportunities
+3. Collect benchmarking insights
 
-Which approach would you like to use?
+### Process
+
+#### 1. Fetch Website
+
+- Use `WebFetch` tool to retrieve HTML
+- Fetch key pages (home, main feature pages, login, etc.)
+
+#### 2. Analyze (Parallel Sub-Agents)
+
+```text
+Agent(subagent_type="general-purpose", model="haiku",
+  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) Tech stack (framework, meta tags, scripts) 2) Page structure (header, nav, main sections, footer) 3) SEO elements (title, meta description, OG tags, structured data)")
+
+Agent(subagent_type="general-purpose", model="haiku",
+  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) Accessibility (ARIA labels, semantic HTML, alt texts, heading hierarchy) 2) Performance hints (script loading, image optimization) 3) Mobile responsiveness (viewport meta, media queries)")
+
+Agent(subagent_type="general-purpose", model="haiku",
+  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) UX patterns (navigation, CTA placement, form design) 2) Design system hints (CSS variables, component patterns) 3) Content strategy (copywriting tone, information hierarchy)")
 ```
 
-3. Wait for user's choice before proceeding
-4. If user chooses VIBE → wait for `/vibe.spec` command
-5. If user chooses Plan Mode → proceed with EnterPlanMode
+#### 3. Figma URL Handling
+
+If a Figma URL is detected, switch to **Figma-specific analysis**:
+- Use `get_design_context` or `get_screenshot` to collect design data
+- Analyze component structure, design tokens, layout patterns
+- Compare design intent with current project code
+
+#### 4. Output
+
+```markdown
+## [URL] Analysis
+
+### Overview
+- **Site type**: [SaaS / E-commerce / Portfolio / ...]
+- **Tech stack**: [Next.js, Tailwind, ...]
+- **Overall score**: N/100
+
+### Technical Analysis
+| Area | Detection | Details |
+|------|-----------|---------|
+| Framework | React/Next.js | SSR enabled |
+| CSS | Tailwind CSS | v3.4 |
+
+### UX/UI Analysis
+- **Navigation**: [assessment]
+- **CTA placement**: [assessment]
+- **Responsive design**: [assessment]
+
+### SEO Analysis (N/100)
+| Element | Status | Recommendation |
+|---------|--------|----------------|
+| Title | Present | Appropriate length |
+| Meta Description | Missing | Add description |
+
+### Accessibility (WCAG 2.1 AA)
+- **Semantic HTML**: [assessment]
+- **Keyboard navigation**: [assessment]
+- **Screen reader support**: [assessment]
+
+### Improvement Suggestions
+1. [highest priority]
+2. ...
+```
+
+#### Fallback
+
+If `WebFetch` fails:
+1. Retry once with a simplified URL (strip query params)
+2. If still failing, inform user of the error (timeout, DNS, etc.)
+3. Suggest user provide HTML file directly: `/vibe.analyze page.html`
 
 ---
 
-## Mode 2: Project Quality Analysis (--code/--deps/--arch)
+## Mode 4: Project Quality Analysis (--code/--deps/--arch)
 
-### Analysis Scope
+### Scope
 
 - **Default** (`/vibe.analyze`): Full analysis (code + dependencies + architecture)
-- **--code**: Code quality analysis only
-- **--deps**: Dependency analysis only
-- **--arch**: Architecture analysis only
+- `--code`: Code quality only
+- `--deps`: Dependency analysis only
+- `--arch`: Architecture analysis only
 
-### Code Quality Analysis (--code)
+### Code Quality (--code)
 
-- Complexity analysis (Cyclomatic Complexity)
+- Cyclomatic complexity analysis
 - Code quality validation
-- Coupling/cohesion check
+- Coupling/cohesion assessment
 
-### Dependency Analysis (--deps)
+### Dependencies (--deps)
 
 - Read `package.json` / `pyproject.toml` / `pubspec.yaml`
-- Analyze version conflicts, security vulnerabilities, packages needing updates
+- Detect version conflicts, security vulnerabilities, outdated packages
 
-### Architecture Analysis (--arch)
+### Architecture (--arch)
 
-- Find core modules
-- Identify module dependencies
-- Detect circular dependencies, layer violations
+- Identify core modules
+- Map module dependencies
+- Detect circular dependencies and layer violations
 
-### Analysis Report
+### Report
 
-`.claude/vibe/reports/analysis-{date}.md`:
+Save to `.claude/vibe/reports/analysis-{date}.md`:
 
 ```markdown
 # Project Analysis Report
 
 ## Overview
-- Analysis date: 2025-01-06 12:00
-- Analysis scope: Full
+- Analysis date: YYYY-MM-DD HH:MM
+- Scope: Full / Code / Deps / Arch
 
-## Code Quality (85/100)
-- Average complexity: 8.2 (good)
-- High complexity files: 3
+## Code Quality (N/100)
+- Average complexity: N (good/warning/critical)
+- High complexity files: N
 
-## Dependencies (92/100)
-- Total packages: 42
-- Updates needed: 3
+## Dependencies (N/100)
+- Total packages: N
+- Updates needed: N
+- Security issues: N
 
-## Architecture (78/100)
-- Circular dependencies: 2 found
-- Layer violations: 1
+## Architecture (N/100)
+- Circular dependencies: N found
+- Layer violations: N
 
 ## Improvement Suggestions
-1. Refactor service.py
-2. Apply lodash security patch
+1. ...
+2. ...
 ```
 
 ## Core Tools (Semantic Analysis)
 
 ### Tool Invocation
 
-All tools are called via:
-
 ```bash
 node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.TOOL_NAME({...args}).then(r => console.log(r.content[0].text)))"
 ```
 
-### Recommended Tools for Analysis
+### Available Tools
 
 | Tool | Purpose | When to Use |
 |------|---------|-------------|
 | `findSymbol` | Find symbol definitions | Locate function/class implementations |
 | `findReferences` | Find all references | Track usage patterns |
-| `analyzeComplexity` | Complexity analysis | Measure code complexity metrics |
+| `analyzeComplexity` | Complexity analysis | Measure complexity metrics |
 | `validateCodeQuality` | Quality validation | Check code quality standards |
-| `saveMemory` | Save analysis results | Store analysis findings |
-
-### Example Tool Usage in Analysis
-
-**1. Find function definition:**
-
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.findSymbol({symbolName: 'login', searchPath: 'src/'}).then(r => console.log(r.content[0].text)))"
-```
+| `saveMemory` | Save analysis results | Persist findings for future sessions |
 
-**2. Analyze complexity:**
-
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.analyzeComplexity({targetPath: 'src/services/', projectPath: process.cwd()}).then(r => console.log(r.content[0].text)))"
-```
-
-**3. Validate code quality:**
+---
 
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.validateCodeQuality({targetPath: 'src/', projectPath: process.cwd()}).then(r => console.log(r.content[0].text)))"
-```
+## Quality Gate (Mandatory)
 
-**4. Save analysis results:**
+### Mode-Specific Checklists
 
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.saveMemory({key: 'analysis-login-module', value: 'Found 5 related files, complexity avg 6.2', category: 'analysis', projectPath: process.cwd()}).then(r => console.log(r.content[0].text)))"
-```
+**Code/Feature Analysis:**
 
----
+| Category | Check Item | Weight |
+|----------|------------|--------|
+| Completeness | All related files identified | 20% |
+| Completeness | All API endpoints documented | 15% |
+| Completeness | All data models mapped | 15% |
+| Accuracy | File paths verified to exist | 10% |
+| Accuracy | Line numbers accurate | 10% |
+| Depth | Business logic explained | 10% |
+| Depth | Dependencies mapped | 10% |
+| Actionability | Next steps clearly defined | 10% |
 
-## Quality Gate (Mandatory)
+**Document Analysis:**
 
-### Analysis Quality Checklist
+| Category | Check Item | Weight |
+|----------|------------|--------|
+| Completeness | Full document read | 20% |
+| Completeness | All key concepts extracted | 20% |
+| Structure | Section structure identified | 15% |
+| Depth | Project relevance analyzed | 15% |
+| Depth | Gap analysis performed | 15% |
+| Actionability | Specific follow-up actions suggested | 15% |
 
-Before completing analysis, ALL items must be checked:
+**Website Analysis:**
 
 | Category | Check Item | Weight |
 |----------|------------|--------|
-| **Completeness** | All related files identified | 20% |
-| **Completeness** | All API endpoints documented | 15% |
-| **Completeness** | All data models mapped | 15% |
-| **Accuracy** | File paths verified to exist | 10% |
-| **Accuracy** | Line numbers accurate | 10% |
-| **Depth** | Business logic explained | 10% |
-| **Depth** | Dependencies mapped | 10% |
-| **Actionability** | Next steps clearly defined | 10% |
+| Completeness | HTML fetched and parsed | 15% |
+| Tech | Tech stack identified | 15% |
+| UX | UX/UI patterns analyzed | 15% |
+| SEO | SEO elements inspected | 15% |
+| A11y | Accessibility checked | 15% |
+| Performance | Performance hints analyzed | 10% |
+| Actionability | Improvements suggested | 15% |
 
-### Analysis Score Calculation
+### Score Calculation
 
 ```
-Score = Σ(checked items × weight) / 100
+Score = sum(checked items * weight) / 100
 
 Grades:
-- 95-100: ✅ EXCELLENT - Comprehensive analysis
-- 90-94:  ⚠️ GOOD - Additional exploration recommended
-- 80-89:  ⚠️ FAIR - Needs more exploration
-- 0-79:   ❌ POOR - Incomplete, re-analyze
+- 95-100: EXCELLENT — comprehensive analysis
+- 90-94:  GOOD — minor gaps, additional exploration recommended
+- 80-89:  FAIR — needs deeper exploration
+- 0-79:   POOR — incomplete, re-analyze
 ```
 
-### Analysis Depth Levels
+### Depth Levels
 
 | Level | Scope | Output |
 |-------|-------|--------|
-| **L1: Surface** | File names, basic structure | File list only |
-| **L2: Structure** | Functions, classes, imports | Structure map |
-| **L3: Logic** | Business logic, data flow | Flow diagrams |
-| **L4: Deep** | Edge cases, dependencies, risks | Full analysis |
-
-**Minimum required: L3 for feature analysis, L2 for project overview**
-
-### Analysis Output Requirements
+| L1: Surface | File names, basic structure | File list |
+| L2: Structure | Functions, classes, imports | Structure map |
+| L3: Logic | Business logic, data flow | Flow analysis |
+| L4: Deep | Edge cases, dependencies, risks | Full analysis |
 
-Every analysis MUST include:
+**Minimum**: L3 for feature analysis, L2 for project overview.
 
-1. **Overview Section**
-   - Feature description (1 sentence)
-   - Implementation status (Complete/In progress/Not implemented)
-   - Related file count
+### Forbidden Patterns
 
-2. **Structure Section**
-   - API endpoints table (Method, Path, Description, Auth)
-   - Core services list with key methods
-   - Data models with fields and relationships
-
-3. **Reference File List**
-   - Absolute or relative paths
-   - Line number ranges for key sections
-   - Brief description per file
-
-4. **Next Steps**
-   - Workflow choice prompt (Plan Mode vs VIBE)
-   - Specific action items if applicable
-
-### Forbidden Incomplete Patterns
-
-| Pattern | Issue | Required Fix |
-|---------|-------|--------------|
-| "and more..." | Incomplete list | List all items |
-| "etc." | Vague scope | Be specific |
-| "related files" without list | Missing details | Provide file paths |
-| Missing line numbers | Hard to navigate | Add `:L10-50` format |
+| Pattern | Problem | Fix |
+|---------|---------|-----|
+| "and more..." | Incomplete | List all items |
+| "etc." | Vague | Be specific |
+| "related files" without paths | Missing detail | Provide file paths |
+| Missing line numbers | Hard to navigate | Use `:L10-50` format |
 | No auth info on endpoints | Security gap | Always specify auth |
 
-### Code Quality Analysis Thresholds
+### Quality Thresholds
 
-When running `--code` analysis:
+**Code (`--code`):**
 
 | Metric | Good | Warning | Critical |
 |--------|------|---------|----------|
@@ -364,9 +520,7 @@ When running `--code` analysis:
 | High Complexity Files | 0 | 1-3 | >3 |
 | Circular Dependencies | 0 | 1 | >1 |
 
-### Dependency Analysis Thresholds
-
-When running `--deps` analysis:
+**Dependencies (`--deps`):**
 
 | Metric | Good | Warning | Critical |
 |--------|------|---------|----------|