SealShare/CLAUDE.md

=== 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.5. 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 <vendor/package> 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
• Use TitleCase for Enum keys: FavoritePerson, BestLake, Monthly.
• 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, which is the fastest way to deploy and scale production Laravel applications.
• Activate the deploying-to-cloud skill whenever deploying to Laravel Cloud, configuring Cloud environments or resources, using the Cloud CLI, or troubleshooting Cloud deployments.

=== tests rules ===

Test Enforcement

• Test every code change by adding or updating a test.
• Run the affected tests and ensure they pass.
• Test the changed behavior and its important failure modes, but do not add tests beyond them.
• Read the testing-best-practices skill before writing tests.

=== 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.

=== laravel-octane/core rules ===

Laravel Octane

This application uses Laravel Octane, a long-running PHP server. The application bootstraps once and handles many requests within the same process.

• Never store request-specific state in singletons or static properties, because it can leak across requests.
• Use config('octane.server') to detect the active driver (swoole, roadrunner, or frankenphp).
• Prefer scoped bindings ($this->app->scoped()) over singletons for per-request services.

When working on Octane-specific features (concurrency, shared tables, memory, driver configuration, testing), invoke octane-development for detailed rules.

=== livewire/core rules ===

Livewire

• Livewire allows you 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.

=== 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 project uses Pest. Create tests with php artisan make:test --pest {name}.
• Do not include the test suite directory in {name}. Use SomeFeatureTest, not Feature/SomeFeatureTest.
• Read the testing-best-practices skill for guidance on coverage, naming, structure, dependency isolation, and review.
• Do not delete tests or test files without approval. They are part of the application.

Running Tests

• Run the narrowest set of tests that covers the change. Pass a file path or --filter=testName to php artisan test --compact.
• Rerun a test after each change to it.
• Run vendor/bin/pest to call the test runner directly. It accepts the same file path and --filter=testName arguments.
• After the feature tests pass, ask the user to run the complete suite with php artisan test --compact.

=== nonameweb/livewire-material/core rules ===

Livewire Material

This application uses nonameweb/livewire-material: Material 3 Expressive components for Laravel and Livewire, built on Tailwind CSS. It replaces UI kits such as maryUI, daisyUI and Flux in this application.

• Components are anonymous Blade components, unprefixed unless config/livewire-material.php sets a prefix. Before writing or changing a view that uses them, activate the livewire-material-development skill for the props, slots and traps of each component.
• Never write maryUI tags (<x-mary-*>) or daisyUI classes (btn, card, badge, bg-base-200, text-base-content…). They compile to nothing and fail silently.
• Every layout includes <x-theme-script /> in <head> before @vite. The colour scheme is generated with php artisan material:scheme — never edit resources/css/material-scheme.css by hand. With colour profiles (livewire-material.profiles), run it without a seed after changing them; the active profile comes from Scheme::resolveProfileUsing().
• While the application runs locally, every token and component renders in the application's own scheme at /material (the showcase).
• HTTP error pages and the Markdown mail theme come from the package. Change error wording by publishing --tag=livewire-material-errors; select the mail theme with MAIL_MARKDOWN_THEME=livewire-material::mail.theme.

=== nonameweb/livewire-material/material-3 rules ===

Material 3

Every view in this application is Material 3 Expressive (m3.material.io), through nonameweb/livewire-material. These rules decide what to write; the material-3-design skill carries the tables, the numbers and Google's source pages behind each one — activate it before designing a screen.

Colour

• A colour is always a role: bg-primary, text-on-surface-variant, border-outline-variant. Never a hex, an arbitrary value, a palette tone or an opacity; Tailwind's palette does not compile.
• Pair a role only with its on- partner: bg-primary text-on-primary, bg-secondary-container text-on-secondary-container. That pair is the one whose contrast is guaranteed at every contrast level; mixing pairs (bg-primary-container text-on-surface) is not.
• primary is the one key action on a screen (a filled button; the FAB in primary-container). secondary-container is the quiet fill (tonal buttons, selected navigation, selected chips). tertiary is a contrasting accent, used rarely. error, success, warning, info mean state and nothing else: the -container for a tinted panel, the role itself for its text and icon.
• Ink is text-on-surface; lower emphasis is text-on-surface-variant (text-body, text-meta); decoration is text-outline (text-quiet). Never dim ink with an opacity: 38% means disabled.
• border-outline is a boundary that must be read (a text field, the edge of a target). border-outline-variant (border-divider, border-structure, border-chrome) is a divider or a card edge. Never outline on a divider.
• Fixed and dim roles (primary-fixed, surface-dim, …) are for a colour that must not change with the theme; if unsure, don't. Inverse roles only on an inverse surface (the snackbar).
• A link is text-primary and underlined (link); colour alone signals nothing.
• Contrast: 4.5:1 for text, 3:1 for large text, icons and grouped controls; disabled is exempt. Three contrast levels exist (<html data-contrast>: standard, medium, high) and every role changes with them — which is why only roles are allowed.

Surfaces and elevation

• The page is bg-surface. Panels separate by tone first: surface-container-lowest … surface-container-highest is a hierarchy of emphasis, not of height. Navigation chrome is surface-container; a dialog, a menu, the search bar are surface-container-high; a modal sheet is surface-container-low; a filled card is surface-container-highest. A region keeps its role at every width.
• Shadows (shadow-elevation-1…5) are for what floats or lifts: 1 for elevated cards, buttons and modal sheets; 2 for menus, the navigation bar, a scrolled app bar; 3 for the FAB, dialogs, pickers and search; one level more on hover; nothing rests above 3. Fewer shadows carry more meaning.
• A scrim is bg-scrim/32.

Shape

• Corners come from the scale rounded-corner-{none|xs|sm|md|lg|lg-increased|xl|xl-increased|xxl|full}; Tailwind's rounded-* does not compile.
• By family: full buttons, icon buttons, chips' avatars, badges, switches, sliders, the search bar, navigation indicators; xs text fields, menus, snackbars, plain tooltips; sm chips; md cards, rich tooltips; lg the FAB and a side sheet's inner corners; xl dialogs, bottom sheets, the search view, pickers, carousel items; xxl large hero containers.
• Nested shapes: inner radius = outer radius − padding; never the same radius inside and out.
• A press squares a round shape (the components do it; nothing morphs on hover). The 35 <x-shape>s are decoration, never meaning, used sparingly.

Type

• Every text element carries one type-* style: display for hero figures and short marketing lines; headline for page and section titles; title for card, dialog and list-section titles; body for paragraphs (body-lg for reading); label inside components (buttons, chips, tabs, captions). Never text-sm, font-medium, leading-*, tracking-* — they do not compile.
• type-emphasized-* is opt-in: a selected item, a primary action, a headline, a badge — not decoration.
• 40–60 characters per line; tabular-nums on figures that change; text must scale to 200% without loss (containers grow, rows wrap, no fixed heights on text, no ellipsis without a way to read the rest).

Motion

• Position, size and shape move on the spatial springs (they overshoot): transition-transform duration-(--md-sys-motion-spatial-default-duration) ease-spatial-default — fast for small elements, slow for large ones. Colour and opacity move on the effects springs (ease-effects-*), which never overshoot. Always pair an easing with its duration.
• Entering decelerates, a permanent exit accelerates, a temporary exit (a sheet, a drawer) takes the emphasized curve; exits are shorter than entrances.
• Everything that moves goes through these tokens, so reduced motion makes it instant; a literal duration is a bug.

States and targets

• Interactive elements carry state-layer focus-ring: hover 8%, focus 10%, pressed 10%, dragged 16% (data-dragged) of the content colour; disabled is disabled:text-on-surface/38 disabled:bg-on-surface/12 and has no hover. Every state shows two indicators: colour plus a shape, an outline, an icon or a word.
• Every target is at least 48×48px with 8px between targets (touch-target on anything drawn smaller); a denser layout is an opt-in prop, never a default.
• Keyboard: Tab between components, arrows within one, Enter and Space activate, Escape dismisses; a dialog takes focus and gives it back to what opened it.

Layout and breakpoints

• Widths are M3's window size classes, the only variants that compile: compact below 600px (the default), medium: 600, expanded: 840, large: 1200, extra-large: 1600, and max-medium: … for "below". In scripts, from() and upTo() from resources/js/breakpoints.js.
• What changes per class: compact — navigation bar, one pane, full-screen dialogs, a bottom sheet for choices; medium — collapsed rail, one pane; expanded — rail (collapsible), two panes, menus and basic dialogs; large and extra-large — the rail expanded, two panes, a third only at extra-large as a side sheet. <x-scaffold> does this; content lives in panes (<x-pane>, <x-list-detail> for a list's second pane), never beside the rail by hand.
• Margins are 16px below medium and 24px from it; spacing sits on the 4px grid, as padding and gaps on the parent, with margins only between layout regions. A fixed pane is 360px (expanded) or 412px (large); a side sheet at most 400px.
• Write logical properties (ps-*, me-*, start-*, text-start); directional icons mirror in RTL; charts and media controls stay LTR. Keep controls inside the safe area (--material-safe-*).

Accessibility

• Native elements first (<button>, <dialog>, <input>), then ARIA. One main, one banner, one contentinfo; every repeated nav labelled, without the word "navigation".
• Headings in order from a single H1; the level is structure, the type-* style is appearance.
• An icon-only control has an accessible name that does not include its role; decorative icons are hidden; an error is announced and tied to its field (aria-describedby); a toast uses a polite live region and never takes focus. A single-key shortcut needs a modifier or a focused component.

Icons

• <x-icon name="…"> is a Material Symbol Rounded: filled means active or selected, optical="20" when drawn at 20px or less, one weight per group, the size and colour of the text beside it.

Don'ts

• No icon in a snackbar; no disabled FAB (hide it); no horizontal radio rows; no hover morph on cards; no outline on dividers; no hex colours; no Tailwind breakpoints or scales; no segmented buttons, navigation drawer or bottom app bar — use <x-button-group connected>, the expanded rail and <x-toolbar>.