Laravel Project Patterns

Adapt fictional domain types and helpers to inspected contracts, keep reference-project identities confidential, and preserve real APIs such as sqid and HasSqid. For uncovered behavior, report the gap and follow the project’s conventions.

Inspect affected code, nearby examples and applicable configuration; use their actual namespaces and, for tests, suite paths. Call helper functions instead of facades whenever a helper exists, such as config()->integer(), now(), resolve(), str() and trans()->string().

Retrieve Missing Patterns

Reuse examples and candidate descriptions already in this context first. For missing behavior, write temporary JSON with request, paths (actual project paths), and code_context (concise inspected facts), then use:

uv run <skill-directory>/scripts/search.py search --task-file=<task.json> --session=<session.json>
uv run <skill-directory>/scripts/search.py read --session=<session.json> --ids <id> <id>