Payload Kits wires schema, render components, generated types, and import-map updates straight into your Payload v3 repo — so blocks belong, not just paste.
Command line
Install one of the shipped alpha kits and keep moving
$ npx payload-kit add feature-grid-basicpayload-kit: generating typespayload-kit: updating import mappayload-kit: install completeInstalled and updated files
Installed surface
Hero Basic
Headline, CTA, proof ribbon, and Payload-safe defaults.
Feature Grid Basic
Text-first feature grid with clean layout registration and an optional CTA row.
Alpha boundary
Two real public kits shipped today while init and doctor remain the next steps.
Built for your stack
Detect the repo, add the kit, and verify the result before shipping. Two steps are live in the public alpha today, the third is on the roadmap.
The current alpha starts with one real command: install a shipped kit and let the wrapper handle the Payload-aware wiring around it.
npx payload-kit add hero-basicThe second shipped kit proves the multi-kit path: files land cleanly, registrations dedupe correctly, and the repo still finishes in a usable state.
npx payload-kit add feature-grid-basicDoctor is next on the roadmap. It is not shipped yet, but it is the next operational layer after the two real public kits.
npx payload-kit doctorEvery install lands like a native repo update, not a pasted screenshot with a schema gap. The moat is that kits understand layouts, type generation, import-map updates, and the constraints agencies deal with every week.
Every kit is designed to drop into Payload layouts instead of fighting them with generic component-library assumptions.
Schema wiring, render components, and install tasks stay aligned so block output and repo structure move together.
Installs finish with generated types and refreshed admin imports so teams do not have to remember fragile cleanup steps.
The catalog stays curated, upgradeable, and consistent across kits, which matters more than chasing visual novelty.
Why teams trust the install
Curated kits that ship with the pieces agencies actually reuse — and the post-install hygiene other component CDNs leave behind.
Operationally legible
CLI surfaces tell you what changed, what was installed, and what still needs attention.
Built for repeated launches
Curated kits ship with the pieces agencies actually reuse instead of one-off demo fragments.
Catalog starts narrow on purpose
Hero Basic and Feature Grid Basic already move from idea to Payload-ready code through the shipped alpha install path.
The gallery stays narrow on purpose: every kit you see here installs cleanly into a Payload v3 repo today, with type generation and import-map updates handled for you.
A headline-first hero block with proof items and CTA support, shipped through the real payload-kit alpha flow.
A text-first feature grid for product and agency landing pages, installed through the same real alpha workflow.
The public catalog builds trust and adoption. The private Pro namespace unlocks the premium kits and bundles that matter when you are shipping repeatedly for clients.
Use the public registry to evaluate install quality, preview the kits, and adopt a dependable baseline into every new client project.
Unlock the private namespace for premium kits, higher-value bundles, and the install workflows that matter once delivery volume starts climbing.
Reliable installs, clean upgrades, and predictable repo wiring matter as much as the blocks themselves — especially when delivery volume starts climbing.
Repeated installs should finish cleanly without duplicate fragments or mysterious manual cleanup.
The CLI should spot unsupported project versions, missing peers, and drift before any fragile changes land.
Pro kits stay behind authenticated access while the install surface remains predictable for approved teams.
When a repo already has existing blocks, the tool should guide a clean merge instead of blindly overwriting work.
The first launch stays narrow on purpose so the install experience can be dependable. These answers set the expectation up front.
Built for agencies and freelancers who want curated blocks, reliable repo wiring, and a chance to influence the next layer of the install flow after the public gallery and the first shipped kits.
Early access
Join the waitlist for launch updates, public-kit drops, and early install access.