Foundation
Shared primitives, validation, security, and diagnostics used across Playstack capabilities.
Foundation packages establish the contracts every other Playstack capability can share without pulling a framework, database, or vendor toward the application core.
Packages
| Package | Plan | Responsibility |
|---|---|---|
@playstack/core | Errors, results, clocks, identifiers, and operation context. | |
@playstack/errors | Runtime-neutral error reporting and safe fan-out. | |
@playstack/errors-react | React error reporting context and resettable boundaries. | |
@playstack/nest-errors | NestJS error reporter injection and exception filtering. | |
@playstack/validation | Shared schemas and portable HTTP validation errors. | |
@playstack/crypto | Web Crypto operations with explicit key ownership. | |
@playstack/prisma-runtime | Explicit runtime selection for generated Prisma clients. | |
@playstack/skills | Versioned repository guidance for agents composing Playstack packages. | |
@playstack/lint | Deterministic checks for package and application integration boundaries. |
Start here
Most applications begin with @playstack/core. Add validation or crypto only when a capability needs those contracts, and keep framework bindings at the outside edge of the application. Tooling remains independently adoptable: the CLI, Skills corpus, and lint rules do not enter the runtime graph.
Localization previews
The independently adoptable i18n core, React binding and Nest binding provide locale policy, typed catalogs and application composition. All three are classified Free under the Laravel localization baseline. The UI localization guide covers shared English artifacts and host-owned translations.