Weave Code
Cornerstone Laravel Package
shipwelldev/cornerstone
Cornerstone is a foundational Laravel package that bundles reusable building blocks, conventions, and scaffolding to help you start and structure applications faster. It aims to cut boilerplate so you can focus on your app's domain logic.
A strongly opinionated Laravel Livewire foundation from Ship Well Development. It provides application defaults, quality gates, an accessible example, and optional agent-mediated integration workflows without adding product features such as authentication, teams, or billing.
Frequently asked questions about Cornerstone
- What is shipwelldev/cornerstone and what does it add to a Laravel app?
- Cornerstone is a strongly opinionated Laravel Livewire foundation that bundles application defaults, reusable building blocks, quality gates, and an accessible example. It also offers optional agent-mediated integration workflows, but it deliberately does not add product features such as authentication, teams, or billing. Think of it as scaffolding and conventions for starting and structuring a new app faster, not a full SaaS starter kit.
- Does Cornerstone require snowflake IDs on all models?
- In v0.5.0 the package pushes an opinionated identifier strategy: snowflake IDs are required on the default User model and on all generated application models. That means new models created through Cornerstone conventions should use 64-bit snowflake keys. For existing models, verify the upgrade notes because the evaluation flags mandatory adoption as a potential breaking change.
- Can I use Cornerstone in an existing Laravel app with auto-increment or UUID keys?
- Brownfield adoption is possible but medium-to-high effort, because primary keys, foreign keys, factories, seeders, API serialization, and auth/session assumptions may all need changes. The package is a weaker fit for apps relying on auto-incrementing keys, UUIDs/ULIDs, legacy schemas, or third-party packages that assume integer IDs. Use a phased migration rather than a big-bang upgrade.
- How do I install and configure Cornerstone in a new Laravel Livewire project?
- Install it with Composer in a greenfield Laravel app that already aligns with the supported Livewire, Pest, Pest Browser, Pint, and Vite stack. Then follow the repository README for publishing defaults and generating models, and confirm the package's Composer constraints against your PHP, Laravel, and database versions. Exact configuration commands should be taken from the README because the package is pre-1.0 and conventions can change.
- Which Laravel, PHP, and database versions are supported?
- The provided evaluation does not list exact version constraints, so check the package's composer.json and README before committing. It references a Livewire/Pest/Vite stack and a Cornerstone support 0.3 compatibility dependency that should be explicitly verified. Also confirm your database supports 64-bit integer keys and the associated index behavior.
- Are snowflake IDs serialized as strings to avoid JavaScript precision loss?
- The evaluation flags JavaScript numeric precision loss as a real risk when exposing 64-bit snowflake IDs in JSON, and asks whether the package serializes them as strings by default. The provided context does not confirm the default serialization behavior. If you have JS/TS clients, verify and enforce string casting at API boundaries before production rollout.
- What does Cornerstone's architecture coverage actually enforce?
- Architecture coverage is a quality gate tied to the package's conventions, including the snowflake ID strategy on generated models. The provided context does not enumerate the exact assertions, so treat it as a compatibility and standards check that needs verification in your CI pipeline. Run it in an isolated branch and review failures before adopting the conventions broadly.
- How are foreign keys, polymorphic relations, and auth tables handled with snowflake IDs?
- These are explicitly flagged as open questions for v0.5.0, especially foreign keys, polymorphic relations, and third-party auth tables. You should verify how the package generates migrations and model traits, and whether Laravel auth scaffolding, Sanctum/Passport, or admin packages conflict with the default User model change. Plan for manual updates to relations and factories where the package does not cover them.
- Is Cornerstone production-ready given it's pre-1.0, and how often does it change?
- Cornerstone is pre-1.0, so expect convention and dependency churn even when your application code is stable. Pin the version, review changelogs for breaking changes, and assign an owner for upgrades and generated-model standards. Frequent dependency bumps increase maintenance cadence, so do not upgrade production apps until the snowflake-ID migration and API serialization strategy are approved.
- What are alternatives to Cornerstone, and what product features does it not include?
- Cornerstone is not an authentication, teams, or billing package; it focuses on application defaults, quality gates, scaffolding, and optional agent-mediated integration workflows. Alternatives include Laravel's official starter kits, Breeze or Jetstream for auth-oriented scaffolding, or your own internal scaffolding conventions. Choose Cornerstone when you want an opinionated Livewire foundation and are willing to adopt its snowflake-ID conventions.
Weaver
How can I help you explore Laravel packages today?