Files
claude-howto/resources.md
T
Luong NGUYEN 1e16914a8d docs: sync to Claude Code v2.1.257 (#180)
* docs: sync to Claude Code v2.1.257

Audit against Claude Code v2.1.257 (repo baseline was v2.1.245, 12 releases
behind). Facts verified against the official docs and cross-checked against
the locally installed 2.1.257 binary.

Critical (P0):
- lesson-quiz L06 Q9 asked how many hook events exist, offering 16/25/31/40.
  With the real answer now 33, no option was correct. Option C 31 -> 33;
  answer letter unchanged.
- 03-skills taught SKILL.md `name`/`description` as required. Official docs
  now state all frontmatter fields are optional and `name` defaults to the
  directory name. Corrected in all five languages.

Hook events 31 -> 33 (PreModelSwitch/PostModelSwitch, v2.1.251) across 30
occurrences in 22 files, including three that read 25. Delta proved by
set-diff against the official event table: no phantom events. Both events
added to the 06-hooks tables with matcher, blocking behavior and 30s timeout,
plus detailed per-event sections.

CLI corrections verified against the binary:
- `claude plugin tag` takes a path, not a version
- `claude plugin init` / `validate` require their arguments
- `plugin init` scaffolds at ~/.claude/skills/<name>/, not project-local
- `--channels` entries must be tagged plugin:<name>@<marketplace>
- `--remote` is a deprecated alias for `--cloud`
- no `claude remote-control` subcommand exists, only the --remote-control flag

Also: CATALOG summary-table totals recomputed in all five languages (column 4
is a derived total, so the count change invalidated it); stale Opus 4.6/4.7
rosters aligned to canonical; self-assessment Advanced Features rescored 0-3
to stop a real gap being graded as mastery; 9 dangling quiz Review pointers
repaired; new features documented (--restricted, Fable 5.1,
experimental.cacheTtl, CLAUDE_CODE_SUBAGENT_MODEL_FORCE).

Deliberately out of scope: pre-existing translation staleness whose fix is
translation authorship rather than correction (ja/uk April-2026 root-doc
bodies, zh stubs, vi/README stub, translated CATALOG "New Features").

Claude-Session: https://claude.ai/code/session_01128xfEd8W7c2cMRw6N7uiF

* fix(hooks): complete the 31 → 33 hook-event propagation across all languages

The v2.1.257 sync bumped the hook-event count in the lesson and catalog
summaries but left 14 files still asserting 31, four of which the same
commit restamped 2.1.257. It also bumped the prose count in
claude_concepts_guide.md without adding the two rows, making that file
contradict itself where it had been internally consistent before.

Adds PreModelSwitch and PostModelSwitch (v2.1.251) everywhere an
exhaustive enumeration exists, and corrects the count wherever a list is
deliberately partial:

- README.md / INDEX.md in en, ja, zh, uk and vi/INDEX.md — count 31 → 33
  and both events added to the lifecycle group
- resources.md in all five languages — count only; these lists end in
  "and more" and are partial by design
- claude_concepts_guide.md — the two missing table rows

Also brings every hook-event table up to the 33 its own summary row
claims. The English CATALOG.md listed 29; the translated catalogs listed
25 and the ja/uk concept guides 27 and 28. Completing them required
translating six events that had never reached the mirrors: Setup,
UserPromptExpansion, PermissionDenied, PostToolBatch, MessageDisplay and
DirectoryAdded.

Summary-table arithmetic is untouched — those columns count example
scripts, not events.

Verified: no stale count survives outside CHANGELOG history, every
exhaustive enumeration lists exactly 33, and pre-commit passes 23/23.

Claude-Session: https://claude.ai/code/session_01UXmqJZNk1BR4uerJA85NiW
2026-09-02 10:35:08 +02:00

15 KiB
Raw Blame History

Claude How To

List of good resources

Official Documentation

Resource Description Link
Claude Code Docs Official Claude Code documentation code.claude.com/docs/en/overview
Anthropic Docs Full Anthropic documentation docs.anthropic.com
MCP Protocol Model Context Protocol specification modelcontextprotocol.io
MCP Servers Official MCP server implementations github.com/modelcontextprotocol/servers
Anthropic Cookbook Code examples and tutorials github.com/anthropics/anthropic-cookbook
Claude Code Skills Community skills repository github.com/anthropics/skills
Agent Teams Multi-agent coordination and collaboration code.claude.com/docs/en/agent-teams
Scheduled Tasks Recurring tasks with /loop and cron code.claude.com/docs/en/scheduled-tasks
Chrome Integration Browser automation code.claude.com/docs/en/chrome
Keybindings Keyboard shortcut customization code.claude.com/docs/en/keybindings
Desktop App Native desktop application code.claude.com/docs/en/desktop
Remote Control Remote session control code.claude.com/docs/en/remote-control
Auto Mode Automatic permission management code.claude.com/docs/en/permissions
Channels Multi-channel communication code.claude.com/docs/en/channels
Voice Dictation Voice input for Claude Code code.claude.com/docs/en/voice-dictation

Anthropic Engineering Blog

Article Description Link
Code Execution with MCP How to solve MCP context bloat using code execution — 98.7% token reduction anthropic.com/engineering/code-execution-with-mcp

Mastering Claude Code in 30 Minutes

Video: https://www.youtube.com/watch?v=6eBSHbLKuN0

All Tips

  • Explore Advanced Features and Shortcuts

    • Regularly check Claude's new code editing and context features in their release notes.
    • Learn keyboard shortcuts to switch between chat, file, and editor views quickly.
  • Efficient Setup

    • Create project-specific sessions with clear names/descriptions for easy retrieval.
    • Pin most-used files or folders so Claude can access them at any time.
    • Set up Claude's integrations (e.g., GitHub, popular IDEs) to streamline your coding process.
  • Effective Codebase Q&A

    • Ask Claude detailed questions about architecture, design patterns, and specific modules.
    • Use file and line references in your questions (e.g., "What does the logic in app/models/user.py accomplish?").
    • For large codebases, provide a summary or manifest to help Claude focus.
    • Example prompt: "Can you explain the authentication flow implemented in src/auth/AuthService.ts:45-120? How does it integrate with the middleware in src/middleware/auth.ts?"
  • Code Editing & Refactoring

    • Use inline comments or requests in code blocks to get focused edits ("Refactor this function for clarity").
    • Ask for side-by-side before/after comparisons.
    • Let Claude generate tests or documentation after major edits for quality assurance.
    • Example prompt: "Refactor the getUserData function in api/users.js to use async/await instead of promises. Show me a before/after comparison and generate unit tests for the refactored version."
  • Context Management

    • Limit your pasted code/context to only what's relevant for the current task.
    • Use structured prompts ("Here's file A, here's function B, my question is X") for best performance.
    • Remove or collapse large files in the prompt window to avoid exceeding context limits.
    • Example prompt: "Here's the User model from models/User.js and the validateUser function from utils/validation.js. My question is: how can I add email validation while maintaining backward compatibility?"
  • Integrate Team Tools

    • Connect Claude sessions to your team's repositories and documentation.
    • Use built-in templates or create custom ones for recurring engineering tasks.
    • Collaborate by sharing session transcripts and prompts with teammates.
  • Boosting Performance

    • Give Claude clear, goal-oriented instructions (e.g., "Summarize this class in five bullet points").
    • Trim unnecessary comments and boilerplate from context windows.
    • If Claude's output is off track, reset context or rephrase questions for better alignment.
    • Example prompt: "Summarize the DatabaseManager class in src/db/Manager.ts in five bullet points, focusing on its main responsibilities and key methods."
  • Practical Use Examples

    • Debugging: Paste errors and stack traces, then ask for possible causes and fixes.
    • Test Generation: Request property-based, unit, or integration tests for complex logic.
    • Code Reviews: Ask Claude to identify risky changes, edge cases, or code smells.
    • Example prompts:
      • "I'm getting this error: 'TypeError: Cannot read property 'map' of undefined at line 42 in components/UserList.jsx'. Here's the stack trace and the relevant code. What's causing this and how can I fix it?"
      • "Generate comprehensive unit tests for the PaymentProcessor class, including edge cases for failed transactions, timeouts, and invalid inputs."
      • "Review this pull request diff and identify potential security issues, performance bottlenecks, and code smells."
  • Workflow Automation

    • Script repetitive tasks (like formatting, clean-ups, and repetitive renaming) using Claude prompts.
    • Use Claude to draft PR descriptions, release notes, or documentation based on code diffs.
    • Example prompt: "Based on the git diff, create a detailed PR description with a summary of changes, list of modified files, testing steps, and potential impacts. Also generate release notes for version 2.3.0."

Tip: For best results, combine several of these practices—start by pinning critical files and summarizing your goals, then use focused prompts and Claudes refactoring tools to incrementally improve your codebase and automation.

Recommended workflow with Claude Code

For a New Repository

  1. Initialize the Repo & Claude Integration

    • Set up your new repository with essential structure: README, LICENSE, .gitignore, root configs.
    • Create a CLAUDE.md file describing the architecture, high-level goals, and coding guidelines.
    • Install Claude Code and link it to your repository for code suggestions, test scaffolding, and workflow automation.
  2. Use Plan Mode and Specs

    • Use plan mode (shift-tab or /plan) to draft a detailed specification before implementing features.
    • Ask Claude for architecture suggestions and initial project layout.
    • Keep a clear, goal-oriented prompt sequence—ask for component outlines, major modules, and responsibilities.
  3. Iterative Develop & Review

    • Implement core features in small chunks, prompting Claude for code generation, refactoring, and documentation.
    • Request unit tests and examples after each increment.
    • Maintain a running task list in CLAUDE.md.
  4. Automate CI/CD and Deployment

    • Use Claude to scaffold GitHub Actions, npm/yarn scripts, or deployment workflows.
    • Adapt pipelines easily by updating your CLAUDE.md and requesting corresponding commands/scripts.
graph TD
    A[Start New Repository] --> B[Initialize Repository Structure]
    B --> C[Create README, LICENSE, .gitignore]
    C --> D[Create CLAUDE.md]
    D --> E[Document Architecture & Guidelines]
    E --> F[Install & Link Claude Code]

    F --> G[Enter Plan Mode]
    G --> H[Draft Feature Specification]
    H --> I[Get Architecture Suggestions]
    I --> J[Define Components & Modules]

    J --> K[Implement Feature Chunk]
    K --> L[Generate Code with Claude]
    L --> M[Request Unit Tests]
    M --> N[Review & Refactor]
    N --> O{More Features?}
    O -->|Yes| K
    O -->|No| P[Update Task List in CLAUDE.md]

    P --> Q[Setup CI/CD Pipeline]
    Q --> R[Scaffold GitHub Actions]
    R --> S[Create Deployment Scripts]
    S --> T[Test Automation]
    T --> U[Repository Ready]

    style A fill:#e1f5fe,stroke:#333,color:#333
    style G fill:#fff9c4,stroke:#333,color:#333
    style K fill:#e8f5e9,stroke:#333,color:#333
    style Q fill:#f3e5f5,stroke:#333,color:#333
    style U fill:#e8f5e9,stroke:#333,color:#333

For an Existing Repository

  1. Repository & Context Setup

    • Add or update CLAUDE.md to document repo structure, coding patterns, and key files. For legacy repos, use CLAUDE_LEGACY.md covering frameworks, version maps, instructions, bugs, and upgrade notes.
    • Pin or highlight main files Claude should use for context.
  2. Contextual Code Q&A

    • Ask Claude for code reviews, bug explanations, refactors, or migration plans referencing specific files/functions.
    • Give Claude explicit boundaries (e.g., "modify only these files" or "no new dependencies").
  3. Branch, Worktree, and Multi-Session Management

    • Use multiple git worktrees for isolated features or bug fixes and launch separate Claude sessions per worktree.
    • Keep terminal tabs/windows organized by branch or feature for parallel workflows.
  4. Team Tools and Automation

    • Synchronize custom commands via .claude/commands/ for cross-team consistency.
    • Automate repetitive tasks, PR creation, and code formatting via Claude's slash commands or hooks.
    • Share sessions and context with team members for collaborative troubleshooting and review.
graph TD
    A[Start with Existing Repository] --> B{Legacy Codebase?}
    B -->|Yes| C[Create CLAUDE_LEGACY.md]
    B -->|No| D[Create/Update CLAUDE.md]
    C --> E[Document Frameworks & Version Maps]
    D --> F[Document Structure & Patterns]
    E --> G[Pin Key Files for Context]
    F --> G

    G --> H[Identify Task Type]
    H --> I{Task Category}
    I -->|Bug Fix| J[Ask Claude for Bug Analysis]
    I -->|Code Review| K[Request Code Review]
    I -->|Refactor| L[Plan Refactoring Strategy]
    I -->|Migration| M[Create Migration Plan]

    J --> N[Set Explicit Boundaries]
    K --> N
    L --> N
    M --> N

    N --> O{Multiple Features?}
    O -->|Yes| P[Create Git Worktrees]
    O -->|No| Q[Work on Main Branch]
    P --> R[Launch Separate Claude Sessions]
    R --> S[Organize Terminal Tabs]
    Q --> S

    S --> T[Setup Team Automation]
    T --> U[Sync .claude/commands/]
    U --> V[Configure Slash Commands]
    V --> W[Setup Hooks for Automation]
    W --> X[Share Session Context with Team]

    X --> Y{More Tasks?}
    Y -->|Yes| H
    Y -->|No| Z[Workflow Complete]

    style A fill:#e1f5fe,stroke:#333,color:#333
    style C fill:#fce4ec,stroke:#333,color:#333
    style D fill:#fff9c4,stroke:#333,color:#333
    style P fill:#e8f5e9,stroke:#333,color:#333
    style T fill:#f3e5f5,stroke:#333,color:#333
    style Z fill:#e8f5e9,stroke:#333,color:#333

Tips:

  • Start each new feature or fix with a spec and plan mode prompt.
  • For legacy and complex repos, store detailed guidance in CLAUDE.md/CLAUDE_LEGACY.md.
  • Give clear, focused instructions and break down complex work into multi-phase plans.
  • Regularly clean up sessions, prune context, and remove completed worktrees to avoid clutter.

These steps capture the core recommendations for smooth workflows with Claude Code in both new and existing codebases.


New Features & Capabilities

Key Feature Resources

Feature Description Learn More
Auto Memory Claude automatically learns and remembers your preferences across sessions Memory Guide
Remote Control Programmatically control Claude Code sessions from external tools and scripts Advanced Features
Web Sessions Access Claude Code through browser-based interfaces for remote development CLI Reference
Desktop App Native desktop application for Claude Code with enhanced UI Claude Code Docs
Extended Thinking Deep reasoning toggle via Alt+T/Option+T or MAX_THINKING_TOKENS env var Advanced Features
Permission Modes Fine-grained control: manual (formerly default), acceptEdits, plan, auto, dontAsk, bypassPermissions Advanced Features
7-Tier Memory Managed Policy, Project, Project Rules, User, User Rules, Local, Auto Memory Memory Guide
Hook Events 33 events: PreToolUse, PostToolUse, PostToolUseFailure, Stop, StopFailure, SubagentStart, SubagentStop, Notification, Elicitation, and more Hooks Guide
Agent Teams Coordinate multiple agents working together on complex tasks Subagents Guide
Scheduled Tasks Set up recurring tasks with /loop and cron tools Advanced Features
Chrome Integration Browser automation with headless Chromium Advanced Features
Keyboard Customization Customize keybindings including chord sequences Advanced Features
Monitor Tool Watch a background command's stdout stream and react to events instead of polling (v2.1.98+) Advanced Features
/goal mode Register a session-level completion condition; Claude keeps working until met (v2.1.139+) Slash Commands
claude agents (Agent View) List, inspect, and resume background agents from the terminal; --json for machine-readable output (v2.1.139+, --json added v2.1.145) code.claude.com/docs/en/agent-view
/run, /verify, /run-skill-generator Bundled skills to launch your project, confirm a fix works, and generate per-project run/verify skills (v2.1.145+) Skills Guide

Last Updated: August 19, 2026 Claude Code Version: 2.1.235 Sources: