Files

Luong NGUYEN 5caeff2f1c refactor: Reorganize repository structure for optimal learning path

Reorder folders based on learning dependencies, complexity, and frequency of use:
- 01-slash-commands (unchanged) - Quick wins for beginners
- 02-memory (was 03) - Essential foundation
- 03-skills (was 05) - Auto-invoked capabilities
- 04-subagents (was 02) - Task delegation
- 05-mcp (was 04) - External integration
- 06-hooks (was 07) - Event automation
- 07-plugins (was 06) - Bundled solutions
- 08-checkpoints (unchanged) - Safe experimentation
- 09-advanced-features (unchanged) - Power user tools

Documentation improvements:
- Add LEARNING-ROADMAP.md with detailed milestones and exercises
- Simplify README.md for better scannability
- Consolidate Quick Start and Getting Started sections
- Combine Feature Comparison and Use Case Matrix tables
- Reorder README sections: Learning Path → Quick Reference → Getting Started
- Update all cross-references across module READMEs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-09 17:54:58 +01:00

1.7 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

1.7 KiB Raw Blame History