The kit you cloned still looks like One Shot: the module is named `Oneshot`, the landing page sells
the kit itself, and the logo reads `> oneshot_`. Before you build your product on top of it, run the
**`bootstrap-app`** skill in Claude Code. It's the one step in this whole guide you should do first,
before adding any feature, because building on top of the kit's own scaffolding is the exact trap
this skill exists to avoid.

```
/bootstrap-app
```

Or just tell Claude Code what you're building; `CLAUDE.md` tells it to reach for this skill first
on a fresh product.

## What it changes

Almost everything about the app's identity is centralized, so `bootstrap-app` touches a small
number of files to rebrand the whole thing:

- **`config/initializers/app_identity.rb`**: one file for the app name, description, support
  email, legal entity, theme color, and the sender name on transactional email. This alone
  rebrands the `<title>`, meta and Open Graph tags, the PWA manifest, the logo, and every mailer.
- **`app/assets/stylesheets/application.css`**: the design token block at the top (`--spark` and
  friends). Change the values, keep the token structure.
- **`app/views/pages/home.html.erb`**: the landing page copy. This one genuinely is
  per-product, so it gets rewritten, not just re-pointed at a config value.
- **The Rails module name** (`Oneshot`): the one true find-and-replace, and it's limited to code
  identifiers (`config/application.rb`, `config.ru`, deploy config, the session cookie key), not
  app content.

## What it removes

Two things exist only because this repository sells One Shot itself, and neither belongs in your
product:

- The **example `Project` slice**: a working, account-scoped, billed resource kept around
  purely as a copy-from template. Once you understand the shape (see
  [Adding a Resource](/docs/building-features/adding-a-resource)), it goes.
- The **shiponeshot.com kit-sale flow**: the license purchase, GitHub repo access grant, and
  the `/buy` and `/license` routes. Unless you're also selling a downloadable kit the way this
  repository does, this whole flow is dead weight in a product it was never written for.

## What it never touches

`bootstrap-app` does not touch the plumbing you're paying for: authentication, the billing seam,
mailers, tenancy, Pundit, security hardening, the PWA shell, or the mobile app wrappers. Those stay
exactly as they are. Rebranding is cosmetic and structural cleanup, not a rewrite.

## Verifying the rename

The skill ends by running `bin/check`. The kit's own specs assert against
`Rails.application.config.x.app_name` rather than the literal string "One Shot", so a correct
rebrand keeps the suite green without you having to hunt down and edit test strings by hand.

## Next

For the full step-by-step this skill follows, see
[The bootstrap-app Skill](/docs/claude-code/skill-bootstrap-app). Once you're rebranded, move on to
[Core Concepts](/docs/core-concepts/accounts-and-tenancy) to understand the one rule that keeps a
multi-tenant app safe.