On this page
  1. Packages
  2. Start here
  3. Localization previews

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

PackagePlanResponsibility
@playstack/coreErrors, results, clocks, identifiers, and operation context.
@playstack/errorsRuntime-neutral error reporting and safe fan-out.
@playstack/errors-reactReact error reporting context and resettable boundaries.
@playstack/nest-errorsNestJS error reporter injection and exception filtering.
@playstack/validationShared schemas and portable HTTP validation errors.
@playstack/cryptoWeb Crypto operations with explicit key ownership.
@playstack/prisma-runtimeExplicit runtime selection for generated Prisma clients.
@playstack/skillsVersioned repository guidance for agents composing Playstack packages.
@playstack/lintDeterministic 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.

Go

Playstack Pro tag
OriginsPricingBlogNewsletterChangelogStatusRoadmap
ContributorsCommunityIn Use ShowcaseCase StudiesPartnersSponsors
FAQsSupportContact

© 2026 Playstack. All rights reserved.

With OSS
Terms of ServicePrivacy PolicyCookie PolicyImprint

By

Commune Software