skills copilot-instructions.md

Project Instructions & Best Practices

As an AI agent working on this repository, you MUST adhere to the following core principles and coding standards. These are synthesized from the individual skills in the skills/ directory (covering Flutter, Dart, GitHub, and other development workflows).

Core Tech Stack

• Language: Dart 3 (Strong typing, null safety, exhaustive switch expressions)
• Framework: Flutter
• State Management: BLoC / Cubit (Event-driven, logic separation)
• Dependency Injection: injectable / get_it
• Architecture: Clean Architecture (Data → Domain → Presentation)

Coding Standards

• Naming: PascalCase for classes, camelCase for variables/functions, snake_case for files.
• Strong Typing: NO dynamic. Use Object? or explicit types.
• Conciseness: Keep files < 300 lines. Keep functions short (< 50 lines).
• Null Safety: Avoid ! operator. Prefer pattern matching or early returns.
• Logging: Use AppLogger. NEVER use print() or raw debugPrint().

Architecture & Data

• Repository Pattern: DataSources handle raw IO (Dio, Isar, Firebase). Repositories handle orchestrating and domain mapping.
• Models: Use fromJson/toJson factories. Data models live in data/, Domain entities in domain/, and UI states in presentation/.
• Forms: Manage form state in BLoCs. Use pure validator functions in the domain layer.

UI & UX (Design System)

• Design Tokens: ZERO hardcoded colors or spacing. Use AppColors, AppSpacing, and AppRadius.
• Widget Lifecycle: Declare controllers/nodes as late final in initState() and dispose in dispose().
• Performance: NO heavy work in build(). Mandate isolates for JSON parsing > 1MB.
• Patterns: NO nested ScrollViews in same direction. NO private _buildWidget methods (extract into classes). Use Slivers for complex lists.

Git Workflow

• Atomic Commits: One commit = one logical change. Follow Conventional Commits: type(scope): description.
• Commit Bodies: Include sub-messages to explain the "why" and "how" of changes.
• Pull Requests: Ensure zero analysis warnings and passing tests before PR. Provide descriptive titles and internal/external change summaries.
• Changelogs: Follow Keep a Changelog standards. Do not copy commit logs directly. Read the git history of the target branch, then summarize the changes under clear categories (Added, Changed, Fixed, Removed).