程式碼搜尋與導航

在大型專案中快速定位程式碼、理解程式碼關係是開發者的核心需求。傳統IDE需要記大量快捷鍵、用多個搜尋面板、頻繁切換檔案視窗。而Claude Code透過自然語言就能完成所有程式碼搜尋和導航任務,讓你專注於理解程式碼邏輯本身,而不是記憶複雜的操作命令。

搜尋程式碼片段

基礎文字搜尋

最簡單的搜尋方式就是用自然語言描述你想找的內容:

在整个项目中搜索"handleError"

Claude Code會自動使用ripgrep(rg)進行高效搜尋:

🔍 Searching for "handleError" in project...

Found 23 occurrences in 8 files:

📄 src/controllers/UserController.js
  Line 45:   handleError(error, res)
  Line 89:   handleError(error, res)
  Line 134:  handleError(error, res)

📄 src/controllers/PostController.js
  Line 23:   handleError(error, res)
  Line 67:   handleError(error, res)

📄 src/middleware/errorHandler.js
  Line 12: function handleError(error, req, res, next) {
  Line 15-18: Definition of handleError function

📄 src/utils/api.js
  Line 78:   handleError(err)

... (4 more files)

Would you like me to:
1. Show the handleError function definition
2. Find all usages of handleError
3. Analyze the error handling pattern

智慧上下文搜尋

Claude Code理解程式碼語義,可以進行智慧搜尋:

找到所有处理用户登录失败的代码

Claude Code會分析程式碼邏輯而不只是文字:

🔍 Semantic search for "login failure handling"...

Found 3 relevant code sections:

1. src/controllers/AuthController.js (lines 45-67)
   ```javascript
   if (!user) {
     logger.warn('Login attempt with non-existent user', { email });
     return res.status(401).json({
       error: 'Invalid credentials',
       code: 'AUTH_FAILED'
     });
   }

2. src/middleware/auth.js (lines 23-45)

   // Token validation failure
   if (!token) {
     return res.status(401).json({
       error: 'Authentication required',
       code: 'NO_TOKEN'
     });
   }

3. src/services/loginService.js (lines 89-112)

   // Password mismatch handling
   const isValid = await bcrypt.compare(password, user.password);
   if (!isValid) {
     logger.warn('Invalid password attempt', { userId: user.id });
     throw new AuthenticationError('Invalid credentials');
   }

Pattern detected: 401 status codes + error logging + warning logs

### 對比傳統方式

**傳統IDE方式:**
1. 按 `Ctrl+Shift+F` 開啟全域性搜尋
2. 輸入搜尋關鍵詞
3. 在結果列表中逐個點選檢視
4. 需要自己判斷哪些結果相關
5. 手動跳轉到每個檔案

**Claude Code方式:**

找出所有可能导致内存泄漏的代码模式

Claude Code會:
- 理解"記憶體洩漏"的程式碼特徵
- 搜尋未清理的事件監聽器、定時器、閉包等
- 提供詳細分析和修復建議
- 標註風險等級

## 查詢函式定義

### 快速定位定義

想知道某個函式在哪裡定義:

找到sendEmail函数的定义

Claude Code會精確定位:

````text
📍 Function Definition: sendEmail

📄 src/services/emailService.js (lines 45-89)

```javascript
/**
 * 傳送郵件
 * @param {Object} options - 郵件選項
 * @param {string} options.to - 收件人郵箱
 * @param {string} options.subject - 郵件主題
 * @param {string} options.html - HTML內容
 * @param {string} options.text - 純文字內容(可選)
 * @returns {Promise[Object]} 傳送結果
 */
async sendEmail({ to, subject, html, text }) {
  try {
    // 驗證郵箱格式
    if (!this.isValidEmail(to)) {
      throw new Error('Invalid email address');
    }

    // 構建郵件選項
    const mailOptions = {
      from: process.env.EMAIL_FROM,
      to,
      subject,
      html,
      text: text || this.htmlToText(html)
    };

    // 傳送郵件
    const info = await this.transporter.sendMail(mailOptions);

    // 記錄日誌
    logger.info('Email sent successfully', {
      messageId: info.messageId,
      to,
      subject
    });

    return info;
  } catch (error) {
    logger.error('Failed to send email', {
      error: error.message,
      to,
      subject
    });
    throw new EmailServiceError('Failed to send email', error);
  }
}

Metadata:

• File: src/services/emailService.js
• Class: EmailService
• Exported as: module.exports (singleton)
• Dependencies: nodemailer, logger
• Error handling: Yes (try-catch + custom error)
• Lines of code: 45

### 智能跳转

Claude Code可以理解不同的引用方式:

__CODE_BLOCK_11__

即使引用方式不同,也能准确定位:

__CODE_BLOCK_12__javascript
static async login(email, password) {
  // ... implementation
}
__CODE_BLOCK_13__

### 链式定义查找

当调用链很长时,Claude Code可以追踪完整链路:

__CODE_BLOCK_14__

Claude Code会构建完整的调用图:

__CODE_BLOCK_15__

## 跳转到引用

### 查找所有使用位置

了解函数或变量在哪里被使用:

__CODE_BLOCK_16__

Claude Code会提供完整的引用分析:

__CODE_BLOCK_17__

### 依赖关系分析

理解模块之间的依赖关系:

__CODE_BLOCK_18__

Claude Code会构建依赖图:

__CODE_BLOCK_19__

## 全局搜索

### 跨文件类型搜索

Claude Code可以同时搜索多种文件类型:

__CODE_BLOCK_20__

__CODE_BLOCK_21__

### 按目录范围搜索

限制搜索范围以提高精度:

__CODE_BLOCK_22__

__CODE_BLOCK_23__

### 组合条件搜索

使用多个条件进行精确搜索:

__CODE_BLOCK_24__

Claude Code会执行复合分析:

__CODE_BLOCK_25__

## 正则表达式搜索

### 基础正则搜索

对于复杂的模式匹配,Claude Code可以使用正则表达式:

__CODE_BLOCK_26__

Claude Code会自动构建合适的正则表达式:

__CODE_BLOCK_27__

### 复杂模式匹配

搜索更复杂的代码模式:

__CODE_BLOCK_28__

Claude Code会构建复杂的正则模式:

__CODE_BLOCK_29__

### 代码气味检测

使用正则表达式检测常见的代码问题:

__CODE_BLOCK_30__

__CODE_BLOCK_31__

## 符号导航

### 类和接口导航

快速浏览类的结构和继承关系:

__CODE_BLOCK_32__

__CODE_BLOCK_33__

### 模块导出导航

理解模块的导出结构:

__CODE_BLOCK_34__

__CODE_BLOCK_35__

### TypeScript类型导航

对于TypeScript项目,查看类型定义:

__CODE_BLOCK_36__

__CODE_BLOCK_37__typescript
interface User {
  // Basic fields
  id: string;
  email: string;
  name: string;

  // Optional fields
  phone?: string;
  avatar?: string;
  bio?: string;

  // Timestamps
  createdAt: Date;
  updatedAt: Date;
  lastLoginAt?: Date;

  // Relationships
  orders?: Order[];
  reviews?: Review[];
  role: UserRole;

  // Methods
  getFullName(): string;
  isAdmin(): boolean;
}
__CODE_BLOCK_38__typescript
// Extended types that inherit from User
interface AdminUser extends User {
  permissions: Permission[];
  department: string;
}

interface GuestUser extends User {
  isGuest: true;
  sessionToken: string;
}
__CODE_BLOCK_39__

## 跨文件搜索

### 多项目搜索

在monorepo或多项目结构中搜索:

__CODE_BLOCK_40__

__CODE_BLOCK_41__

### 配置文件搜索

搜索和对比配置文件:

__CODE_BLOCK_42__

__CODE_BLOCK_43__

### 依赖关系搜索

查找模块间的依赖关系:

__CODE_BLOCK_44__

__CODE_BLOCK_45__

## 实用技巧和最佳实践

### 技巧1: 智能搜索模式

使用更精确的搜索描述:

❌ 模糊搜索:
__CODE_BLOCK_46__
结果: 返回上百个可能不相关的文件

✅ 精确搜索:
__CODE_BLOCK_47__
结果: 返回5-10个高度相关的代码片段

### 技巧2: 组合搜索条件

使用多个条件缩小范围:

__CODE_BLOCK_48__

Claude Code会执行多维度分析:

__CODE_BLOCK_49__

### 技巧3: 代码模式识别

让Claude Code识别特定的代码模式:

__CODE_BLOCK_50__

__CODE_BLOCK_51__javascript
    class Database {
      constructor() {
        if (Database.instance) {
          return Database.instance;
        }
        this.connection = null;
        Database.instance = this;
      }
    }
    module.exports = new Database();
    __CODE_BLOCK_52__javascript
    const Cache = (function() {
      let instance;
      function createInstance() {
        return new CacheService();
      }
      return {
        getInstance: function() {
          if (!instance) {
            instance = createInstance();
          }
          return instance;
        }
      };
    })();
    __CODE_BLOCK_53__javascript
    class Logger {
      static instance = null;

      static getInstance() {
        if (!Logger.instance) {
          Logger.instance = new Logger();
        }
        return Logger.instance;
      }
    }
    __CODE_BLOCK_54__

### 技巧4: 性能分析

搜索性能相关的代码:

__CODE_BLOCK_55__

__CODE_BLOCK_56__javascript
   for (const user of users) {
     const orders = await db.query(
       'SELECT * FROM orders WHERE user_id = ?',
       [user.id]
     ); // Query inside loop!
   }
   __CODE_BLOCK_57__javascript
   const allData = await fs.readFile('large-file.json');
   const data = JSON.parse(allData); // 500MB file!
   __CODE_BLOCK_58__javascript
   const regex = /^(a+)+$/; // Dangerous pattern
   __CODE_BLOCK_59__javascript
   async function exportData() {
     const data = fs.readFileSync('file.json'); // Blocks!
   }
   __CODE_BLOCK_60__javascript
   {allRows.map(row => <Row data={row} />)} // Too slow!
   __CODE_BLOCK_61__

### 技巧5: 安全漏洞检测

搜索潜在的安全问题:

__CODE_BLOCK_62__

__CODE_BLOCK_63__javascript
   const query = `SELECT * FROM users WHERE id = ${userId}`;
   // Direct string interpolation!
   ```
   Severity: CRITICAL
   Impact: Data breach, data loss
   Fix: Use parameterized queries
   ```javascript
   const query = 'SELECT * FROM users WHERE id = ?';
   await db.query(query, [userId]);
   ```

2. src/components/Comment.jsx (Line 56)
   Vulnerability: XSS (Cross-Site Scripting)
   ```javascript
   <div dangerouslySetInnerHTML={{ __html: userComment }} />
   // Unsanitized user input!
   ```
   Severity: CRITICAL
   Impact: Session hijacking, data theft
   Fix: Sanitize input or use DOMPurify
   ```javascript
   import DOMPurify from 'dompurify';
   <div dangerouslySetInnerHTML={{
     __html: DOMPurify.sanitize(userComment)
   }} />
   ```

3. src/services/auth.js (Line 123)
   Vulnerability: Timing attack on password comparison
   ```javascript
   if (user.password === inputPassword) // Unsafe comparison
   ```
   Severity: HIGH
   Impact: Password bypass possible
   Fix: Use bcrypt.compare()
   ```javascript
   await bcrypt.compare(inputPassword, user.password);
   ```

4. src/config.js (Line 12)
   Vulnerability: Hardcoded secret key
   ```javascript
   const JWT_SECRET = 'my-secret-key-123';
   ```
   Severity: CRITICAL
   Impact: Token forgery, authentication bypass
   Fix: Use environment variable with strong key

5. src/utils/crypto.js (Line 45)
   Vulnerability: Weak random number generation
   ```javascript
   const token = Math.random().toString(36); // Predictable!
   ```
   Severity: HIGH
   Impact: Session hijacking
   Fix: Use crypto.randomBytes()
   ```javascript
   const token = require('crypto').randomBytes(32).toString('hex');
   ```

6. src/api/payment.js (Line 234)
   Vulnerability: Logging sensitive data
   ```javascript
   logger.info('Payment:', { cardNumber, cvv }); // Leaking CVV!
   ```
   Severity: CRITICAL
   Impact: PCI-DSS compliance violation, fraud
   Fix: Never log sensitive data

🟡 High Priority (5):
- Missing CSRF tokens
- Insecure cookie settings (no httpOnly, sameSite)
- CORS misconfiguration
- Missing rate limiting
- Weak password requirements

🟢 Medium Priority (7):
- Missing security headers
- Outdated dependencies
- Error messages leak info
- Missing input validation
- No HTTPS enforcement

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🚨 Immediate Action Required:
1. Fix SQL injection (30 minutes)
2. Fix XSS vulnerabilities (1 hour)
3. Remove hardcoded secrets (15 minutes)
4. Fix timing attack (15 minutes)
5. Stop logging sensitive data (10 minutes)

Total time: ~2 hours

📋 Security Checklist:
□ Parameterized all database queries
□ Sanitized all user inputs
□ Using environment variables for secrets
□ Implementing proper password hashing
□ Using secure random generation
□ Not logging sensitive data
□ Implementing CSRF protection
□ Securing cookies with httpOnly, sameSite, secure
□ Configuring CORS correctly
□ Adding rate limiting

Would you like me to fix these critical security issues?
```

## 常見問題解答

### Q: 如何搜尋註釋中的TODO標記?

**A:** 有幾種方式:

```
# 方式1: 简单搜索
搜索所有的TODO注释

# 方式2: 按优先级搜索
找到所有标记为urgent或critical的TODO

# 方式3: 按时间搜索
找出所有30天前的TODO注释

# 方式4: 按作者搜索
搜索所有我写的TODO注释(假设注释中有作者)
```

Claude Code會找到所有TODO並提供分析:

```
📝 TODO Analysis

Found 47 TODOs in the codebase:

By Priority:
  • Critical: 5 (blocking release)
  • High: 12 (important features)
  • Medium: 18 (improvements)
  • Low: 12 (nice to have)

By Age:
  • > 90 days: 8 (stale)
  • 30-90 days: 15 (needs attention)
  • < 30 days: 24 (recent)

By Category:
  • Features: 20
  • Bug fixes: 8
  • Refactoring: 12
  • Documentation: 7

🎯 Recommended Actions:
1. Address 5 critical TODOs (blocking release)
2. Convert stale TODOs to GitHub issues
3. Schedule high-priority TODOs for next sprint
```

### Q: 如何查詢未使用的程式碼?

**A:** 讓Claude Code分析依賴關係:

```
找出所有未被使用的:
1. 函数
2. 组件
3. 导入的模块
4. 类型定义
```

Claude Code會進行深度分析:

```
🔍 Unused Code Detection

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Unused Functions (12):
  src/utils/helpers.js
    • formatPhoneNumber() - defined but never called
    • parseUserAgent() - defined but never called
    • ... (10 more)

Unused Components (5):
  src/components/
    • OldDashboard.jsx - imported in no files
    • BetaFeature.jsx - imported in no files
    • ... (3 more)

Unused Imports (34):
  src/pages/Home.jsx
    Line 3: import { unusedFunction } from './utils'
    Line 5: import { useState, useEffect } from 'react'
           // Only useEffect is used

  ... (32 more)

Unused Type Definitions (7):
  src/types/
    • LegacyUser - not referenced anywhere
    • OldApiResponse - not referenced anywhere
    • ... (5 more)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

💰 Cleanup Potential:
  • Lines of code: ~2,400
  • Files: 12 completely unused
  • Import cleanup: 34 files
  • Bundle size reduction: ~15%

⚠️ Caution:
Before deleting, verify:
1. Not used dynamically (e.g., string references)
2. Not exported for external use
3. Not used in tests (separate test imports)
4. Not part of public API

Would you like me to:
1. Create a cleanup plan
2. Delete automatically (with git backup)
3. Show more details first
```

### Q: 如何理解複雜的程式碼邏輯?

**A:** 讓Claude Code進行程式碼分析:

```
解释一下src/services/paymentService.js中的processPayment方法是如何工作的
```

Claude Code會提供詳細的解釋:

```
📖 Code Explanation: processPayment method

📄 Location: src/services/paymentService.js (lines 123-234)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 Purpose:
Processes payment transactions through multiple payment providers
with automatic fallback and error handling.

📋 Algorithm Overview:

Step 1: Validation (lines 125-145)
  • Validates payment amount (must be > 0)
  • Checks card number format (Luhn algorithm)
  • Verifies expiry date is in future
  • Ensures CVV is 3-4 digits
  If validation fails → throws ValidationError

Step 2: Load User Payment Methods (lines 147-167)
  • Fetches stored payment methods from database
  • Decrypts card details (using encryption key)
  • Checks if card is still valid
  If no valid cards → throws NoPaymentMethodError

Step 3: Primary Payment Attempt (lines 169-189)
  • Attempts payment with primary provider (Stripe)
  • Sends amount + card details
  • Waits for response (max 30 seconds)
  If successful → saves transaction, returns result
  If failed with network error → proceeds to Step 4
  If failed with payment error → throws PaymentError

Step 4: Fallback Payment Attempt (lines 191-211)
  • Attempts payment with backup provider (PayPal)
  • Same data as primary attempt
  If successful → saves transaction, returns result
  If failed → throws PaymentFailedError

Step 5: Record Transaction (lines 213-234)
  • Saves transaction record to database
  • Includes: provider, amount, status, timestamp
  • Updates user's payment history
  • Sends confirmation email

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔄 Flow Diagram:
  User Input
      ↓
  [Validation] ← fail → ValidationError
      ↓ pass
  [Load Methods] ← fail → NoPaymentMethodError
      ↓ success
  [Primary Payment] ← network error → [Fallback Payment]
      ↓ success                          ↓ success
  [Record Transaction] ←─────────────── [Record Transaction]
      ↓
  Return Success

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

💡 Key Design Patterns:
1. **Strategy Pattern**: Multiple payment providers
2. **Circuit Breaker**: Automatic fallback on failure
3. **Transaction Logging**: Complete audit trail
4. **Error Handling**: Specific error types
5. **Security**: Encrypted card details

⚠️ Potential Issues:
1. Synchronous card loading (could be slow)
2. No retry mechanism for transient failures
3. Fallback always triggered (even for invalid cards)
4. Transaction logging happens after payment (race condition)

🎯 Improvement Suggestions:
1. Load payment methods asynchronously
2. Add retry logic with exponential backoff
3. Validate card before attempting payment
4. Log transaction before payment (intent)
5. Add idempotency key to prevent double charges

Would you like me to implement any of these improvements?
```

### Q: 如何查詢程式碼的演進歷史?

**A:** 結合Git歷史進行分析:

```
显示UserController.js的演进历史,包括:
1. 什么时候创建的
2. 主要的修改节点
3. 代码行数变化
4. 贡献者
```

Claude Code會分析Git歷史:

```
📜 Code Evolution: UserController.js

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📅 Creation:
  Date: 2024-03-15 (9 months ago)
  Author: Zhang San
  Initial commit: a1b2c3d
  Initial lines: 45

📊 Size Evolution:
  • 2024-03-15: 45 lines (initial)
  • 2024-04-20: 89 lines (+44, validation added)
  • 2024-06-15: 134 lines (+45, error handling)
  • 2024-08-10: 156 lines (+22, logging)
  • 2024-10-05: 167 lines (+11, tests)
  • Current: 167 lines

  Growth: 122 lines in 9 months (~13 lines/month)

🔄 Major Commits (5):

1. 2024-10-05 (2 weeks ago) by Li Si
   Commit: f3e4d5c
   Message: "Add unit tests for UserController"
   Changes: +11 lines, -0 lines
   Files modified: 2 (controller + tests)
   Impact: Test coverage increased from 45% to 78%

2. 2024-08-10 (2 months ago) by Wang Wu
   Commit: b2c3d4e
   Message: "Add comprehensive logging to UserController"
   Changes: +22 lines, -0 lines
   Added: Logger integration, 8 log points
   Impact: Better debugging capability

3. 2024-06-15 (4 months ago) by Zhang San
   Commit: a1b2c3d
   Message: "Implement error handling middleware"
   Changes: +45 lines, -12 lines
   Added: Try-catch blocks, custom errors
   Removed: Inline error responses
   Impact: Consistent error responses

4. 2024-04-20 (6 months ago) by Li Si
   Commit: 9f8e7d6
   Message: "Add input validation to all endpoints"
   Changes: +44 lines, -3 lines
   Added: express-validator middleware
   Impact: Better security, data integrity

5. 2024-03-15 (9 months ago) by Zhang San
   Commit: 8d7f6e5
   Message: "Initial implementation of UserController"
   Changes: +45 lines (initial commit)
   Features: CRUD operations for users

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

👥 Contributors:
  • Zhang San: 2 commits (40%)
  • Li Si: 2 commits (40%)
  • Wang Wu: 1 commit (20%)

📈 Quality Metrics:
  • Test coverage: 78% (started at 0%)
  • Code complexity: Medium (cyclomatic complexity: 8)
  • Technical debt: Low (no major issues)
  • Documentation: Good (JSDoc on all methods)

🔍 Code Quality Evolution:
  • Initial: Basic CRUD, no error handling
  • +2 months: Added validation
  • +4 months: Added error handling
  • +6 months: Added logging
  • +8 months: Added tests
  Current: Production-ready, well-tested

💡 Observations:
✓ Consistent improvement over time
✓ Multiple contributors (good knowledge sharing)
✓ Focus on quality (tests, logging, validation)
⚠️ Slower growth recently (maintainance mode)

🎯 Recommendations:
1. Consider adding integration tests
2. Document API endpoints (Swagger)
3. Add performance monitoring
4. Consider code review checklist

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Would you like me to:
1. Show detailed diff for any commit
2. Compare two versions
3. Analyze contributor patterns
4. Generate changelog
```

## 總結

程式碼搜尋與導航是Claude Code的核心優勢之一。相比傳統IDE的快捷鍵和複雜搜尋面板,Claude Code透過自然語言就能完成所有搜尋和導航任務。

### 核心優勢

**1. 智慧理解**
- 理解程式碼語義,不只是文字匹配
- 識別程式碼模式和設計模式
- 分析依賴關係和影響範圍

**2. 全面分析**
- 跨檔案、跨專案搜尋
- 組合多個搜尋條件
- 提供上下文和建議

**3. 自然互動**
- 無需記憶快捷鍵
- 用自然語言描述需求
- 對話式探索程式碼

**4. 深度洞察**
- 效能問題檢測
- 安全漏洞掃描
- 程式碼質量分析
- 演進歷史追蹤

### 最佳實踐

**搜尋技巧:**
1. ✅ 用精確描述而不是模糊關鍵詞
2. ✅ 組合多個條件縮小搜尋範圍
3. ✅ 讓Claude Code分析程式碼而不只是查詢文字
4. ✅ 利用程式碼理解功能學習複雜邏輯

**導航技巧:**
1. ✅ 追蹤完整呼叫鏈理解系統架構
2. ✅ 分析依賴關係評估修改影響
3. ✅ 檢視程式碼演進歷史理解設計決策
4. ✅ 使用符號導航快速定位定義和引用

**分析技巧:**
1. ✅ 定期搜尋未使用的程式碼並清理
2. ✅ 檢測安全漏洞和效能問題
3. ✅ 分析程式碼模式並統一重構
4. ✅ 理解程式碼質量指標

### 實用場景

**日常開發:**
- 快速定位函式定義和引用
- 理解複雜的程式碼邏輯
- 查詢相似程式碼進行復用

**程式碼審查:**
- 分析程式碼影響範圍
- 檢測潛在問題
- 理解修改上下文

**重構最佳化:**
- 找到所有需要修改的地方
- 分析程式碼結構
- 識別重構機會

**學習理解:**
- 理解系統架構
- 學習設計模式
- 追蹤程式碼演進

掌握這些搜尋和導航技巧,能更高效地理解和操作程式碼庫,把精力集中在解決問題而不是尋找程式碼上。

## 下一步

- 學習 [程式碼編輯與重構](/claude-code/02-核心功能/code-editing) - 深入瞭解程式碼級別的編輯操作
- 探索 [Agent模式](/claude-code/02-核心功能/agent-mode) - 讓Claude Code自主完成複雜任務
- 掌握 [Think模式](/claude-code/03-高階特性/think-mode) - 使用思維鏈提升複雜任務處理能力