andyngdz

Master code organization - encapsulation with wrapper methods, file modularity (split >150 lines), one function one responsibility, descriptive naming, minimal comments

Use when starting work - guidelines for asking questions and commit policies

Use when adding error handling - exception patterns, HTTP codes, domain exceptions

Use when adding logging to features - structured logging with LoggerService categories

Use when exiting plan mode - where to save implementation plans

Apply Martin Fowler's refactoring patterns - extract variables to eliminate repetition, split temporary variables, replace temp with query for cleaner, more maintainable code

Use when writing tests - test structure, mocking patterns, pre-commit checks

Master type safety patterns - fix type errors at source, never use type: ignore or any, prefer Pydantic models, use type stubs for external libraries

Use when refactoring or implementing features - validation, component design, API research

Use when starting work - guidelines for asking questions and commit policies

Use always - non-negotiable rules for TypeScript safety, socket events, and React patterns

Use when working with Electron - IPC security, renderer isolation, Node API access

Use when writing tests - test structure, verification steps, coverage goals