Laravel Astro Landing Laravel Package

Getting Started

Install the package and wire it into Laravel Boost:

composer require lauroguedes/laravel-astro-landing
php artisan boost:install     # select "astro-landing-development" when prompted

If you already run Boost, the equivalent is to add the skill name to the skills array in boost.json and then run php artisan boost:update.

Where to look first:

1. boost.json at the project root — this is the source of truth for which skills your agents get. Commit it.
2. The shipped skill source inside vendor/lauroguedes/laravel-astro-landing (the SKILL.md with YAML frontmatter) — read it once so you know what instructions your agent is actually following.
3. The generated skill directory that Boost writes to for your agent of choice — confirm the file is there, not just that the command exited 0.

First use case: ask your agent to scaffold or refactor an Astro landing page inside the Laravel app (marketing page, waitlist page, content-driven landing with an Astro island talking to a Laravel API). The skill supplies Astro-specific conventions the agent would otherwise guess at.

As of v1.2.1 the skill actually installs. Prior to this release php artisan boost:update silently skipped astro-landing-development because its frontmatter failed to parse, while the package's guidelines still installed — so the package looked healthy but the skill was never there.

Implementation Patterns

Two installation paths, pick one and stick to it. Interactive (boost:install) is best for first setup; declarative (boost.json + boost:update) is best for teams and CI, because the file is diffable and reviewable.

Treat boost.json like a lockfile. Add the skill entry in the same PR as the composer.json bump, so a fresh clone plus composer install && php artisan boost:update reproduces the exact agent setup.

Re-run boost:update after every composer update of this package. The skill content lives in vendor/ and is copied into your agent's skills directory on update; a plain composer update alone will not refresh it.

Verify by artifact, not by exit code. After updating, list the skills directory and confirm the astro-landing-development file exists and its frontmatter is intact. This is the check that would have caught the pre-1.2.1 bug immediately.

Separate the two payloads mentally. The package ships guidelines (always installed, injected into agent context) and the skill (conditionally installed, listed in boost.json). When a task goes wrong, decide which one was supposed to drive the behaviour before debugging.

Adopt the frontmatter test pattern for your own skills. v1.2.1 added a CI test that parses the frontmatter of every shipped skill. Mirror that in any app or package where you author skills:

it('has valid frontmatter', function () {
    $raw = File::get(resource_path('boost/skills/astro-landing-development/SKILL.md'));
    $yaml = Str::between($raw, "---\n", "\n---");
    expect(Symfony\Component\Yaml\Yaml::parse($yaml))->toBeArray();
});

Keep the skill list short and scoped. Skills compete for context; add astro-landing-development to projects that actually have an Astro landing surface, and remove it from backend-only services.

Gotchas and Tips

Silent skill failure is the headline pitfall. A malformed YAML frontmatter block does not fail boost:update — the skill is skipped and the command still succeeds. v1.2.1 fixes the specific instance (an unquoted colon in the description) but the failure mode is inherent to how Boost parses skills. Never trust a clean exit as proof of installation.

Quote every skill description. YAML rejects a colon inside an unquoted mapping value. Also watch #, leading >, {, and trailing colons — quoting the whole description sidesteps all of it.

If the skill never appeared, editing boost.json alone is not enough. Per the upgrade notes: either add astro-landing-development to the skills list and run boost:update, or run boost:install and select it. A boost.json entry that was never successfully installed can look correct while producing nothing.

Upgrade is non-breaking and trivial: composer update lauroguedes/laravel-astro-landing && php artisan boost:update. No app code, config, or migration changes.

Guidelines installing is not evidence the skill installed. This is exactly the false-positive that hid the bug — guidelines and skills have independent install paths.

Debugging checklist when agent behaviour looks off: (1) does the skill file exist, (2) does its frontmatter parse, (3) is the name in boost.json spelled exactly as the package ships it, (4) did you re-run boost:update after the last composer operation.

Extension point: copy the shipped SKILL.md into your own app-level skills directory and customise it (your routing conventions, your API client, your component library) rather than fighting the vendor copy, which will be overwritten on the next boost:update.