* docs: sync all tutorials with latest Claude Code official docs (April 2026) Update 44 documentation files to reflect the latest Claude Code features from code.claude.com. Key content changes include new slash commands (/ultraplan, /powerup, /sandbox), deprecated command removals (/pr-comments, /vim), corrected skill description budget (1%/8K), new hook events (PermissionDenied, InstructionsLoaded, ConfigChange), expanded Agent Teams section, new plugin components (LSP, bin/, settings.json), and new CLI flags (--bare, --tmux, --effort, --channels). Added "Last Updated: April 2026" metadata footer to all documentation files. * fix(docs): correct env var values and alphabetical ordering - CLAUDE_CODE_NEW_INIT=true → =1 in 02-memory and 09-advanced-features - CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=true → =1 in 09-advanced-features - Fix /powerup vs /plugin alphabetical order in slash commands table * fix(docs): correct env var values in locale files (vi, zh) Propagate CLAUDE_CODE_NEW_INIT=true → =1 and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=true → =1 corrections to Vietnamese and Chinese translations.
64 lines
1.7 KiB
Markdown
64 lines
1.7 KiB
Markdown
# 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**: April 2026
|