# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. ## Project BelaBlock — a score-keeping app for the card game Bela (Belote). Laravel 13 + Livewire 3 (Volt available) with Flux Pro UI components and Tailwind v4. Local DB is MySQL; tests run on in-memory SQLite (see `phpunit.xml`). Flux Pro is a paid package pulled from `composer.fluxui.dev` — `composer install` needs credentials (`auth.json` locally, `FLUX_USERNAME`/`FLUX_LICENSE_KEY` secrets in CI). ## Commands ```bash composer dev # server + queue listener + pail logs + vite, all concurrently composer test # config:clear then php artisan test composer pint # style check (dry run) composer pint-fix # apply style fixes composer stan # PHPStan/Larastan, level 9 over app/ composer check # stan + pint --test + tests --parallel (run this before pushing) npm run dev / build # vite ``` Single test / filtered runs: ```bash php artisan test --filter="guests are redirected to the login page" php artisan test tests/Feature/DashboardTest.php ./vendor/bin/pest --testsuite=Unit ``` Node 22 (`.nvmrc`), PHP 8.4+ (CI uses 8.5). ## Code style and conventions `ai-rules.md` (duplicated as `.junie/guidelines.md`) is the authoritative style guide — read it before writing PHP. It is enforced by Pint (`pint.json`, Laravel preset) and PHPStan level 9. Points that bite most often: - No PHPDoc on fully type-hinted methods; docblocks only for `@throws` and generics (`@return Collection`, `@param array $data`). Level 9 requires generics on every iterable. - `match()` instead of `switch`, early returns instead of `else`, happy path last. - Enums live in `App\Enums` with the `Enum` suffix, back a string value, and `use EnumValuesTrait` for `::values()`. - Tests are Pest (functional `it()`/`test()`, `expect()`, `uses()`, `beforeEach()`) — no PHPUnit classes. Descriptions are plain-English behavior sentences, not camelCase method names. Use `uses(RefreshDatabase::class);` per-file for DB tests, AAA structure inside each closure. Browser/UI-flow tests live in `tests/Browser/` (Pest's Playwright-backed browser plugin), reserved for a handful of critical end-to-end flows — everything else stays a `Livewire::test()` component test. Target elements by visible text, `wire:model`, or `name` (default locale is `en`); reserve `data-test="..."` for icon-only controls with no distinguishing text. - All user-facing strings go through `__()`; Croatian translations live in `lang/hr.json` (`lang/hr/` holds the framework files). English text is the translation key. - HTTP status codes come from `Symfony\Component\HttpFoundation\Response` constants. ## Architecture ### Domain model `Game` → `GameRound` → (`RoundScore`, `Declaration`), plus `GamePlayer` for editable player names. - `Game.session_id` (uuid) groups a *series* of games between the same players. "New game" creates a fresh `Game` row reusing the previous `session_id`, and player names are copied over via `transferPlayerNamesToNewGame()`. Series win counts are derived by counting finished games with the same `session_id` — there is no separate match/series table. - `GameRound.is_draft` is the central mechanism: the round currently being played is persisted as a draft row so dealer / trump suit / taker / declarations survive a page reload. `finalizeDraftRound()` flips `is_draft` to false and writes `RoundScore` rows. At most one draft round per game. - `RoundScore.final_score = base_score + declarations_score`; `fall` and `shtik` are per-player round flags. - Enum casts everywhere (`GameTypeEnum`, `TargetScoreEnum`, `StatusEnum`, `DefaultPlayerNameEnum`, `TrumpSuitEnum`, `DeclarationTypeEnum`). Player identity is a *type* (`player1`/`player2`/`team1`/`team2`), not a user id — only the game owner (`Game.user_id`) is a real user. - `DeclarationTypeEnum` carries the scoring rules (`getValue()`, `getMaxCount()`, `isMultiple()`, `isSpecial()`); `TrumpSuitEnum` carries labels, colors, and icon paths under `public/images/suit-icons/`. ### Service layer All persistence and game logic lives in `App\Services\GameService`, used through `App\Contracts\GameServiceInterface` (bound in `AppServiceProvider::register()`). Livewire components inject it in `boot()`, never in `mount()` — `boot()` runs on every request, `mount()` only on the first. Add new game operations to the interface + service rather than to components. Only `GameTypeEnum::TWO_PLAYER` is implemented; `THREE_PLAYER`/`DOUBLES` have score targets defined and `PLAIN` throws "To be implemented". ### Livewire structure `App\Livewire\Games\TwoPlayerGame` is the parent/orchestrator (route `games/two-player/{gameId?}`); the children in `Games\Components` (`GameInfo`, `DeclarationsList`, `ScoreModal`) communicate with it purely through dispatched events: - child → parent: `dealer-changed`, `trump-suit-changed`, `taker-changed`, `declarations-updated`, `score-added` - parent → children: `open-score-modal`, `reset-game-info`, `reset-declarations`, `player-name-changed` - `update-url` is handled in JS inside `two-player-game.blade.php` to swap the URL to the new game id without a redirect Every state-changing parent handler calls `saveDraftState()`, which upserts the draft round. Derived UI state (totals, winner, remaining points, disabled buttons) is exposed via `#[Computed]` methods, not stored properties. Views mirror components: `resources/views/livewire/games/...`. Custom Flux icon/navlist overrides live in `resources/views/flux/`. ### Auth Standard Laravel starter-kit auth as Livewire classes in `App\Livewire\Auth` (routes in `routes/auth.php`). Authorization on games is a manual `auth()->id() !== $this->game->user_id` → `abort(Response::HTTP_FORBIDDEN)` check; there are no policies. ## Git and CI Work happens on `develop`; PRs target `main`. Pushing to `staging` triggers an FTP deploy to cPanel (`.github/workflows/deploy-codithr-staging.yaml`) which runs `php artisan migrate --force` remotely. CI runs Pint (`lint.yml`) and Pest (`tests.yml`, including browser tests) on pushes/PRs to `develop` and `main`. === === foundation rules === # Laravel Boost Guidelines The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to ensure the best experience when building Laravel applications. ## Foundational Context This application is a Laravel application running on PHP 8.4. You are an expert with the Laravel ecosystem. Always use the APIs that match the installed major version of each package — do not assume a version. Before relying on a package's API, confirm its installed version: - PHP packages: run `composer show --direct` to list direct dependencies with versions, or `composer show ` for a single package. - JS packages: check `package.json` for the installed versions. ## Skills Activation This project has domain-specific skills available in `**/skills/**`. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck. ## Conventions - You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, and naming. - Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`. - Check for existing components to reuse before writing a new one. ## Verification Scripts - Do not create verification scripts or tinker when tests cover that functionality and prove they work. Unit and feature tests are more important. ## Application Structure & Architecture - Stick to existing directory structure; don't create new base folders without approval. - Do not change the application's dependencies without approval. ## Frontend Bundling - If the user doesn't see a frontend change reflected in the UI, it could mean they need to run `npm run build`, `npm run dev`, or `composer run dev`. Ask them. ## Documentation Files - You must only create documentation files if explicitly requested by the user. ## Replies - Be concise in your explanations - focus on what's important rather than explaining obvious details. === boost rules === # Laravel Boost ## Tools - Laravel Boost is an MCP server with tools designed specifically for this application. Prefer Boost tools over manual alternatives like shell commands or file reads. - Use `database-query` to run read-only queries against the database instead of writing raw SQL in tinker. - Use `database-schema` to inspect table structure before writing migrations or models. - Use `get-absolute-url` to resolve the correct scheme, domain, and port for project URLs. Always use this before sharing a URL with the user. - Use `browser-logs` to read browser logs, errors, and exceptions. Only recent logs are useful, ignore old entries. ## Searching Documentation (IMPORTANT) - Use `search-docs` before changes that depend on Laravel ecosystem APIs, behavior, configuration, or version-specific syntax. Skip it for copy-only edits and other changes where package documentation is irrelevant. Reuse sufficient results already in context instead of searching again. - Pass a `packages` array to scope results when you know which packages are relevant. - Use multiple broad, topic-based queries: `['rate limiting', 'routing rate limiting', 'routing']`. Expect the most relevant results first. - Do not add package names to queries because package info is already shared. Use `test resource table`, not `filament 4 test resource table`. ### Search Syntax 1. Use words for auto-stemmed AND logic: `rate limit` matches both "rate" AND "limit". 2. Use `"quoted phrases"` for exact position matching: `"infinite scroll"` requires adjacent words in order. 3. Combine words and phrases for mixed queries: `middleware "rate limit"`. 4. Use multiple queries for OR logic: `queries=["authentication", "middleware"]`. ## Project Rules - This project contains committed, area-grouped rules in `.ai/rules` when that directory exists (settled decisions, non-obvious traps, standing constraints). Framework and package guidelines that only apply to specific paths (testing, frontend, components) also live there, under `.ai/rules/boost` — this is not just recorded decisions, it is load-bearing guidance you have not seen inline. Before you enter plan mode or create/edit any file, you MUST first: open @.ai/rules/index.md (it maps file globs to rule files), read every rule file whose globs cover the path(s) in scope, and run `grep -rin 'keyword' .ai/rules` to catch what a path match alone misses. Do not write code until you have read and are following every matching rule. If `.ai/rules` does not exist, continue without it. - Record durable rules with `record-rule` so the next agent or teammate inherits them instead of working them out again. Pass a `glob` (e.g. `app/Http/Controllers/**`), a short `title`, and a few-line `note`. Always use `record-rule`, never your native memory or notes tool — native memory is personal and session-scoped; only `.ai/rules` is shared with the team and persists in the repo. ## Artisan - Run Artisan commands directly via the command line (e.g., `php artisan route:list`). Use `php artisan list` to discover available commands and `php artisan [command] --help` to check parameters. - Inspect routes with `php artisan route:list`. Filter with: `--method=GET`, `--name=users`, `--path=api`, `--except-vendor`, `--only-vendor`. - Read configuration values using dot notation: `php artisan config:show app.name`, `php artisan config:show database.default`. Or read config files directly from the `config/` directory. ## Tinker - Execute PHP in app context for debugging and testing code. Do not create models without user approval, prefer tests with factories instead. Prefer existing Artisan commands over custom tinker code. - Always use single quotes to prevent shell expansion: `php artisan tinker --execute 'Your::code();'` - Double quotes for PHP strings inside: `php artisan tinker --execute 'User::where("active", true)->count();'` === php rules === # PHP - Always use curly braces for control structures, even for single-line bodies. - Use PHP 8 constructor property promotion: `public function __construct(public GitHub $github) { }`. Do not leave empty zero-parameter `__construct()` methods unless the constructor is private. - Use explicit return type declarations and type hints for all method parameters: `function isAccessible(User $user, ?string $path = null): bool` - Follow existing application Enum naming conventions. - Prefer PHPDoc blocks over inline comments. Only add inline comments for exceptionally complex logic. - Use array shape type definitions in PHPDoc blocks. === deployments rules === # Deployment - Laravel can be deployed using [Laravel Cloud](https://cloud.laravel.com/), which is the fastest way to deploy and scale production Laravel applications. === herd rules === # Laravel Herd - The application is served by Laravel Herd at `https?://[kebab-case-project-dir].test`. Use the `get-absolute-url` tool to generate valid URLs. Never run commands to serve the site. It is always available. - Use the `herd` CLI to manage services, PHP versions, and sites (e.g. `herd sites`, `herd services:start `, `herd php:list`). Run `herd list` to discover all available commands. === tests rules === # Test Enforcement - Every change must be programmatically tested. Write a new test or update an existing test, then run the affected tests to make sure they pass. - Run the minimum number of tests needed to ensure code quality and speed. Use `php artisan test --compact` with a specific filename or filter. === laravel/core rules === # Do Things the Laravel Way - Use `php artisan make:` commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using `php artisan list` and check their parameters with `php artisan [command] --help`. - If you're creating a generic PHP class, use `php artisan make:class`. - Pass `--no-interaction` to all Artisan commands to ensure they work without user input. You should also pass the correct `--options` to ensure correct behavior. ### Model Creation - When creating new models, create useful factories and seeders for them too. Ask the user if they need any other things, using `php artisan make:model --help` to check the available options. ## APIs & Eloquent Resources - For APIs, default to using Eloquent API Resources and API versioning unless existing API routes do not, then you should follow existing application convention. ## URL Generation - When generating links to other pages, prefer named routes and the `route()` function. ## Testing - When creating models for tests, use the factories for the models. Check if the factory has custom states that can be used before manually setting up the model. - Faker: Use methods such as `$this->faker->word()` or `fake()->randomDigit()`. Follow existing conventions whether to use `$this->faker` or `fake()`. - When creating tests, make use of `php artisan make:test [options] {name}` to create a feature test, and pass `--unit` to create a unit test. Most tests should be feature tests. ## Vite Error - If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run `npm run build` or ask the user to run `npm run dev` or `composer run dev`. === livewire/core rules === # Livewire - Livewire allow to build dynamic, reactive interfaces in PHP without writing JavaScript. - You can use Alpine.js for client-side interactions instead of JavaScript frameworks. - Keep state server-side so the UI reflects it. Validate and authorize in actions as you would in HTTP requests. === volt/core rules === # Livewire Volt - Single-file Livewire components: PHP logic and Blade templates in one file. - Always check existing Volt components to determine functional vs class-based style. - IMPORTANT: Always use `search-docs` tool for version-specific Volt documentation and updated code examples. - IMPORTANT: Activate `volt-development` every time you're working with a Volt or single-file component-related task. === pint/core rules === # Laravel Pint Code Formatter - If you have modified any PHP files, you must run `vendor/bin/pint --dirty --format agent` before finalizing changes to ensure your code matches the project's expected style. - Do not run `vendor/bin/pint --test --format agent`, simply run `vendor/bin/pint --format agent` to fix any formatting issues. === pest/core rules === # Pest - This application uses Pest for testing. All tests are written in Pest's functional style (`it()`/`test()`, `expect()`). Use `php artisan make:test {name}` to create a new test. - If you see a test using PHPUnit classes, convert it to Pest. - Every time a test has been updated, run that singular test. - When the tests relating to your feature are passing, ask the user if they would like to also run the entire test suite to make sure everything is still passing. - Tests should cover all happy paths, failure paths, and edge cases. - You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files; these are core to the application. - Browser tests (`tests/Browser/`, Playwright-backed) are reserved for a handful of critical end-to-end UI flows; prefer a `Livewire::test()` component test otherwise. ## Running Tests - Run the minimal number of tests, using an appropriate filter, before finalizing. - To run all tests: `php artisan test --compact`. - To run all tests in a file: `php artisan test --compact tests/Feature/ExampleTest.php`. - To filter on a particular test name: `php artisan test --compact --filter="test name"` (recommended after making a change to a related file).