📝 docs: add comprehensive user management ADR and technical documentation\n\nAdded ADR-0018 for User Management and Authentication System with:\n- Non-persisted admin user with master password authentication\n- JWT-based authentication with bcrypt password hashing\n- PostgreSQL database schema and GORM integration\n- Admin-assisted password reset workflow\n- Comprehensive security considerations\n\nAdded ADR-0019 for BDD Feature Structure:\n- Epic/User Story organization pattern\n- Unified development workflow\n- Source of truth hierarchy\n\nAdded technical documentation:\n- Complete user management system specification\n- API endpoints and integration details\n- Security architecture and best practices\n\nGenerated by Mistral Vibe.\nCo-Authored-By: Mistral Vibe <vibe@mistral.ai>

CONTRIBUTING.md

@@ -436,4 +436,25 @@ By contributing to DanceLessonsCoach, you agree that your contributions will be
 
 ---
 
-**Thank you for contributing!** 🎉
+**Thank you for contributing!** 🎉
+## 📝 Naming Conventions
+
+### Files
+- Use kebab-case: `my-file-name.md`
+- Include purpose: `bdd-feature-structure.md`
+- Avoid generics: Not `status.md`, use `project-status.md`
+
+### Directories
+- Use kebab-case: `my-directory/`
+- Group by feature: `epic_user-management/`
+- Avoid nesting >3 levels deep (max: `features/epic/user-story/`)
+
+### ADRs
+- Sequential numbering: `0019-bdd-feature-structure.md`
+- Clear titles: Describe the decision
+- Consistent format: Follow ADR template
+
+### Commits
+- Use gitmoji: `:sparkles: feat`, `:bug: fix`, `:memo: docs`
+- Reference issues: `Fixes #123` or `Related to #456`
+- Keep concise: 50-72 characters