Laravel Astro Landing Laravel Package

Product Decisions This Supports

• Build vs. buy for agent context. The package is essentially a distribution channel for opinionated guidance: it ships an astro-landing-development skill that Laravel Boost installs into a project's boost.json skill list and refreshes via php artisan boost:update. A PM can treat "buy" here as adopting a curated, versioned skill rather than having the team write and maintain its own prompt/guidelines library for Astro landing pages.
• Tooling roadmap for AI-assisted delivery. Whether to standardize on Laravel Boost as the mechanism for distributing agent skills across the team. This release is the first evidence that the skill pipeline actually works end to end — worth confirming before committing roadmap scope to it.
• Scope decision: Laravel app + Astro landing pages. Adoption implies a concrete architecture choice — Astro for marketing/landing surfaces beside a Laravel application. That's a stack decision, not just a dependency decision, and should be made alongside the front-end lead.
• Feature-level use cases. Fast iteration on campaign pages, waitlists, and pre-launch landings generated inside an existing Laravel codebase, where the agent has Laravel-aware conventions plus Astro-specific guidance available in the same context window.
• Risk/quality posture for agent-generated code. The release adds a test that parses the frontmatter of every shipped skill, so a malformed skill now fails CI instead of being silently skipped in customer apps. That converts an adoption risk (agents quietly working without the guidance you think they have) into a caught build failure — a meaningful reliability signal when justifying the dependency.

When to Consider This Package

Consider it when most of the following hold:

• The team already uses, or is actively evaluating, Laravel Boost and a boost.json-based skill workflow. Without Boost, the skill has no delivery mechanism and the package's value largely evaporates.
• Astro is already the chosen or shortlisted framework for landing/marketing pages, and pages will live in or next to a Laravel codebase.
• The pain point is consistency of agent output — you want recurring landing pages built to a house style rather than re-prompting from scratch each time.
• You want a small, versioned, upgradeable artifact (composer update + php artisan boost:update) rather than a hand-maintained internal prompt library.
• You can tolerate a young, single-maintainer, low-traffic package. The v1.2.1 fix is a reminder that the skill plumbing is early: a YAML quoting bug silently skipped the skill entirely while the package's guidelines installed normally.

Look elsewhere when:

• No Laravel Boost in the stack — evaluate the skill's content directly or skip it.
• No Astro, or the front-end direction is unsettled (Next.js, plain Blade, a marketing CMS). Adopting now bakes in a stack choice before it's been made.
• You need a mature marketing platform — page builder, localization workflows, CMS, A/B tooling, and analytics governance are out of scope for a skill package.
• You require enterprise support, SLAs, or audited change history.
• The team needs to pin and review prompt content under change control; skill text shipped from a third party should be read before it enters agent context.

Practical adoption note for v1.2.1: teams that attempted adoption on earlier versions may have silently received guidelines only. Verify astro-landing-development is actually present in boost.json and installed; if it was never added, add it to the skills list or re-run php artisan boost:install and select it, then run boost:update.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small, low-cost dependency that packages our conventions for building Astro landing pages into a format our AI coding assistants can load automatically. It targets a recurring, low-differentiation cost — rebuilding campaign and pre-launch pages — and makes agent output more predictable. The just-released v1.2.1 is a maintenance fix, not a scope change, but it matters: a formatting bug had been causing the skill to be skipped without any error, so some teams may believe they were using it when they weren't. The maintainer also added a CI check that would have caught it. Net: low risk, cheap to trial, easy to reverse — one Composer update and one Artisan command.

For engineering leads (bullet summary):

• The package's real payload is a Laravel Boost skill plus package guidelines; there is no runtime library surface to integrate with.
• v1.2.1 fixed a broken YAML frontmatter (unquoted colon in a description) that made Boost fail to parse the skill, so boost:update skipped it while guidelines installed fine. Descriptions are now quoted.
• New guardrail: a test parses the frontmatter of every shipped skill, so this class of failure now breaks CI upstream rather than degrading silently in our app.
• Upgrade path: composer update lauroguedes/laravel-astro-landing then php artisan boost:update. If the skill is missing from boost.json, add astro-landing-development or re-run boost:install.
• Ask before we commit: confirm the skill's content matches our house conventions, and decide whether third-party skill text needs review in PRs before it reaches agent context.