statamic-with-eloquentlisted

# Statamic CMS Development ## When to Apply Activate this skill when: - Creating or editing Statamic collections, blueprints, fieldsets, or globals - Working with Statamic entries, taxonomies, or navigations - Building page templates or content block partials - Creating or modifying View Composers for Statamic views - Working with Bard, Replicator, or other Statamic fieldtypes - Querying content via Statamic facades - Running `php please` commands ## Documentation Use `search-docs` with `packages: ["statamic/cms"]` for version-specific Statamic documentation. ## Blade-Only Templating This project uses **Blade exclusively** — no Antlers. All templates are `.blade.php` files. Statamic variables are accessed as regular PHP variables in Blade. ```blade {{-- Correct: Blade syntax --}} <h1>{{ $title }}</h1> {{-- WRONG: Antlers syntax — never use this --}} {{ title }} ``` ## Eloquent Driver This project uses the Statamic Eloquent Driver with a **hybrid storage strategy**. Check `config/statamic/eloquent-driver.php` to see which resources use `eloquent` (database) vs `file` (disk). - **Entries, terms, globals variables, nav trees, revisions** → stored in database - **Blueprints, fieldsets, collections, forms** → stored as YAML files on disk - All Eloquent tables use a configurable prefix (see `STATAMIC_ELOQUENT_PREFIX` env var) **Always query content via Statamic facades** — they abstract the storage driver. ## Querying Content Use Statamic facades, never raw DB querie