Kits and starter recipes - what they are, in plain English

What a kit actually is

A kit is one finished piece of an app - the sign-in, the booking calendar, the invoice sender - written out as a set of instructions your vibe coder follows. You are not buying code you have to understand. You paste it in and it gets built.

1. 1

   Every kit has a plain title and one-line description

   The description tells you what it does, not how it works. If you cannot tell what a kit does from its title and line, tell us and we will rewrite it.

   Browse the kits
2. 2

   Kits come in three sizes

   Quick touch (a small polish job), Add-on (a proper feature), Full feature (the core of an app). The size tells you how many steps it takes and roughly how long.

3. 3

   Kits are grouped into packs

   A pack is a family of kits for one kind of app - Bookings and scheduling, Invoicing and getting paid, Hiring and applicants, and so on. Pick a pack in the catalogue and you get a plain description and a Use it for list.

How to pick without guessing

1. 1

   Start from the job, not the tech

   Search for what you want to happen - book, invoice, refer, roster - rather than a technical word. The catalogue searches titles, descriptions and tags.

2. 2

   Use the pack filter

   Choose a pack and the page explains in one line who that pack is for and the everyday jobs it covers.

3. 3

   Let the Workshop pick

   In the Workshop, describe your idea and we match it to kits automatically, then tell you what is covered and what is missing.

   Open Workshop

Starter recipes

A starter recipe is a pack already assembled into a working app shape, so you do not have to tick twenty boxes.

1. 1

   Pick the recipe closest to your idea

   Each recipe lists the kits it includes, what it gets you and roughly how much building time it saves.

   See starter recipes
2. 2

   Check readiness before you export

   Recipes run a dependency check first, so you are told up front if something needs a database table or another kit before it will work.

3. 3

   Add and remove freely

   A recipe is a starting point. Add kits from any other pack - nothing is capped by pack.

Good to know

1. 1

   Your accounts, your keys

   If a kit touches an outside service, it uses your own account and keys. We never bill your users through our accounts.

2. 2

   Nothing is TV-specific

   Kits are for software apps. TV channels are a separate part of FrankenApp with their own hub and guides.

3. 3

   Missing something?

   If nothing on the shelf covers a feature you need, the Workshop writes a custom prompt for it so your build still holds together.