mirror of https://github.com/luongnv89/claude-howto.git synced 2026-08-21 12:17:15 +02:00

Files

T

Luong NGUYEN b9a973bf32 docs: accuracy pass against Claude Code v2.1.220 (#155 )

Internal accuracy pass against v2.1.220 — no missing upstream features, but broken example code, disagreeing counts, and metadata drift.

Functional fixes: pre-commit.sh now exits 2 so it actually blocks; dependency-check.sh reads file_path from stdin JSON instead of $1; database-mcp.json uses ${DATABASE_URL}; broken fences repaired; three command templates had invalid skill names.

Factual corrections: /fork and /subtask unswapped and /subtask added; /fewer-permission-prompts; permissions.defaultMode; dontAsk/auto unreversed; 31 hook events verified name-by-name; subagent depth 3; skill precedence enterprise > project > personal; /output-style removed not deprecated; permissionDecision gained defer.

Follow-up review fixed defects the pass left behind: zh/vi headers claiming 31 events above 25-name lists, a surviving hardcoded DB credential in the MCP README examples, an unbalanced fence swallowing a metadata footer, and non-canonical tool names. All four translated CATALOG summary tables were recounted so their arithmetic holds.

Full detail in CHANGELOG.md under v2.1.220-r2.

2026-08-04 15:41:12 +07:00

1.9 KiB

Raw Blame History

My Development Preferences

About Me

Experience Level: 8 years full-stack development
Preferred Languages: TypeScript, Python
Communication Style: Direct, with examples
Learning Style: Visual diagrams with code

Code Preferences

Error Handling

I prefer explicit error handling with try-catch blocks and meaningful error messages. Avoid generic errors. Always log errors for debugging.

Comments

Use comments for WHY, not WHAT. Code should be self-documenting. Comments should explain business logic or non-obvious decisions.

Testing

I prefer TDD (test-driven development). Write tests first, then implementation. Focus on behavior, not implementation details.

Architecture

I prefer modular, loosely-coupled design. Use dependency injection for testability. Separate concerns (Controllers, Services, Repositories).

Debugging Preferences

Use console.log with prefix: [DEBUG]
Include context: function name, relevant variables
Use stack traces when available
Always include timestamps in logs

Communication

Explain complex concepts with diagrams
Show concrete examples before explaining theory
Include before/after code snippets
Summarize key points at the end

Project Organization

I organize my projects as:

project/
  ├── src/
  │   ├── api/
  │   ├── services/
  │   ├── models/
  │   └── utils/
  ├── tests/
  ├── docs/
  └── docker/

Tooling

IDE: VS Code with vim keybindings
Terminal: Zsh with Oh-My-Zsh
Format: Prettier (100 char line length)
Linter: ESLint with airbnb config
Test Framework: Jest with React Testing Library

Last Updated: August 4, 2026 Claude Code Version: 2.1.220 Sources:

https://code.claude.com/docs/en/memory Compatible Models: Claude Fable 5, Claude Opus 5, Claude Sonnet 5, Claude Sonnet 4.6, Claude Opus 4.8, Claude Haiku 4.5

1.9 KiB Raw Blame History