daily-planning

# 🧑‍💻 Copilot Instructions for Planejador Pessoal

## Project Overview

- **Planejador Pessoal** is a Laravel-based personal planning system with task management, user profiles, and Jira integration.
- Frontend uses Inertia.js, TypeScript, and Vite for SPA experience.
- Dockerized development via Laravel Sail for consistency.

## Key Architecture & Patterns

- **Backend:**
    - Business logic in `app/` (Controllers, Models, Services, Providers).
    - Events/Listeners pattern for async and cross-component actions (see `app/Events/`, `app/Listeners/`).
    - Jobs for background processing (`app/Jobs/`).
    - Service layer for external integrations (e.g., `app/Services/JiraService.php`).
- **Frontend:**
    - SPA components in `resources/js/components/` (Vue + TypeScript).
    - Views in `resources/views/`.
    - Use Inertia.js for server-driven navigation and state.
- **Database:**
    - Migrations in `database/migrations/` define schema.
    - Seeders in `database/seeders/` for initial data.
    - Factories in `database/factories/` for test data.

## Developer Workflows

- **Setup & Run:**
    - Use Laravel Sail for all local dev commands:
        - `composer install`
        - `cp .env.example .env`
        - `sail up -d`
        - `sail artisan key:generate`
        - `sail artisan migrate --seed`
- **Testing:**
    - Run tests with: `sail artisan test`
    - Feature and unit tests in `tests/Feature/` and `tests/Unit/`.
- **Linting:**
    - Use ESLint for JS/TS: `npx eslint resources/js/`
- **Frontend Build:**
    - Vite config in `vite.config.ts`.
    - Build assets: `npm run build` (uses Vite).

## Conventions & Integration

- **Branching:**
    - Use `feature/*` for new features, `fix/*` for bugfixes.
- **Auth Providers:**
    - Social login (GitHub, Google) requires `.env` config (see README for details).
- **Jira Integration:**
    - Credentials stored in `jira_credentials` table and managed via `JiraService.php`.
- **Routes:**
    - Defined in `routes/web.php`, `routes/auth.php`, etc.
- **External Services:**
    - All external API logic should be encapsulated in `app/Services/`.

## Examples

- **Event Handling:**
    - To trigger async actions, dispatch events from controllers and handle in listeners.
- **Task Management:**
    - CRUD logic for tasks in `app/Http/Controllers/` and `app/Models/Task.php`.
- **Frontend-Backend Communication:**
    - Use Inertia.js for passing data from controllers to Vue components.

## References

- See `README.md` for setup, environment, and integration details.
- Database schema: `database/migrations/`
- Main business logic: `app/`
- Frontend SPA: `resources/js/components/`

---

If any section is unclear or missing, please provide feedback to improve these instructions.