Documentation / Reference
Distribution
Creator Core is available as a clean public GitHub template, a public npm runtime, and editable shadcn registry bundles. The public release is MIT licensed; third-party dependencies and optional vendor assets retain their own terms.
Three ways to use the system
| Distribution | Best for | What stays in your product |
|---|---|---|
| Public template | A new application using the connected foundation | Routes, visual components, branding, schema, services, docs, and agent guidance |
| Runtime package | Shared motion and action behavior | Your existing interface, provider integration, and product data |
| Editable registry bundles | Adding motion primitives or animated metrics to an existing compatible app | Installed visual source and its customizations |
The complete starter provides the integrated system. Installing the runtime or a presentation bundle alone does not configure accounts, application data, or deployment.
Start a product
Create a repository with the public template, clone your new repository, then initialize the clean copy before dependency installation or product edits:
bun run init:product --name my-product --dry-run
bun run init:product --name my-product
Initialization verifies that the source matches a published release and that the exact runtime package contains the expected provenance. It installs the matching public package, removes maintainer-only files, changes the Worker names and product defaults, and activates consumer dependency updates. It preserves existing environment files.
Follow getting started for your service projects, required environment, first real browser test, and deployment setup. The canonical maintained repository must not run product initialization.
Install into an existing app
bunx --bun shadcn add itsNintu/creator-core-kit/motion-primitives#v0.2.7 --dry-run
bunx --bun shadcn add itsNintu/creator-core-kit/animated-metrics#v0.2.7 --dry-run
Remove --dry-run for the selected installation after reviewing the changes. Bundles use the actual maintained component source and declare their exact runtime dependency. Preserve the included license and third-party notice files when copying or updating editable source.
The registry targets the Next.js, React 19, Tailwind 4, and shadcn Base UI stack. Add to an existing app covers compatibility, runtime setup, and the entry points.
Public package access
The runtime is published to https://registry.npmjs.org. Public installation does not need a GitHub Packages token, a package-read permission, or a Dependabot package secret.
If an older project uses private @itsnintu/creator-core-runtime, follow the public npm migration to replace the dependency and import prefix with @nintu/creator-core-runtime. Remove its old scope route only when no other dependency needs it; keep unrelated private registry configuration intact.
Follow the release boundary
Use published tags and release notes. A version in a local checkout is not proof that it has been published. Initialization refuses unmatched or incompatible source/package versions.
The public repository contains exported release source with its own clean history. The private canonical repository and historical vendor material are not published by changing their access. Package publication does not deploy your application or synchronize its backend.
Keep updates deliberate
Review runtime dependency updates, merge editable component changes with your own source, and follow migration notes for scaffolding or backend changes. These are separate operations described in updating a product.