Create a repository

Create a Lupinum repository from the correct tested starter.

Use this procedure before product code enters a new repository.

Prepare the identity

Decide the repository name, package name or names, one-sentence purpose, final documentation domain, license, and repository profile. Lupinum public libraries use the MIT license unless a product decision states otherwise.

Check npm and GitHub name availability. Use the final scoped names before the first public release. When no users exist, prefer a hard cutover over permanent aliases.

Generate the repository

Create the repository from the matching tested starter. Replace all declared placeholders. Delete optional components that the product does not use.

Run:

bash

pnpm install
pnpm verify
pnpm audit:all
pnpm docs:build
pnpm release:verify

For a deployed app, omit package-release checks that the starter marks as not applicable.

Open the first pull request

Push a normal feature branch. Open a real pull request so all review and deployment systems run. Confirm the issue forms, PR template, package preview, CodeRabbit, CI, security scans, and Vercel preview.

Configure external controls

Complete the repository launch checklist. Record the settings that cannot be stored in Git. Do not mark the repository ready from file checks alone.