AI Build registry starter kit

Builder @kento_mvp · Starter kits

A source pack for publishing build cards, detail pages, setup facts, access terms, and support requests.

Source accessv0.1.0Report expiredStarter Kit

Build registry starter kit interface mockup

Approved capture · 2026-07-09 · illustrative interface preview

Demo

Auto-captured preview

Stack

Lovable Cloud / Supabase / Email provider optional

External services

Lovable Cloud / Supabase +1

Setup effort

Standard setup · 3 steps, 3 providers, 2 required env vars

Source path

GitHub clone · JPY 34,800

Reuse terms

Starter Kit · Listed in terms

Known limitation

Payment, entitlement, and verification backend are not implemented.

Build Package boundary

You are not buying a business.

This record describes a reusable Build Package: source, setup context, reuse terms, and optional support. It does not transfer the operating business around it.

Included

Build registry route shells
Mock registry data
Supabase starter notes
Brand replacement checklist

Not included

Customer data or production database
Existing users, revenue, or profit
Domain transfer
Third-party accounts
API keys, tokens, or secrets
Full business ownership or operating entity

Available separately

Setup support
Customization support
Deployment review
Provider configuration
Migration help

Start from the Build, then connect your own data, accounts, domain, and operations.

Source package

Build registry starter repository with route shells, mock registry data, Supabase starter notes, and brand replacement checklist.

Delivery artifactGitHub clone

Included artifactsBuild registry route shells · Mock registry data · Supabase starter notes · Brand replacement checklist

LicenseStarter Kit

Commercial useListed in terms

RedistributionRedistribution not allowed

Support scopeProject Room available for Supabase setup and listing model adaptation.

Version policyAccess is tied to BuildVersion v0.1.0 and prototype source boundaries.

Package access fee

JPY 34,800。Access is granted only after review and remains tied to the version record and access record.