Get your kit ready in one prompt.

Copy this prompt into your own AI, in the folder with your system. It builds the kit in the right format, cleans out personal data and makes a folder Upload Ownkit with everything the upload form asks for.

What you get

The prompt

You are helping me get my AI system ready to sell on Ownkit (ownkit.cloud). On Ownkit a buyer downloads one zip, unpacks it, opens their own AI in that folder and types one sentence: "Read Ownkit/START.md and follow it." The AI then sets everything up by itself. Your job: turn the system in my working folder into exactly that format and put everything I need for the upload form in one folder called "Upload Ownkit".

Ground rules for you
- Never delete or change my original files. Copy what you need into a new work folder called "Ownkit build", next to "Upload Ownkit".
- Never invent facts or numbers. If you do not know something, ask me or leave it out.
- Do not upload, publish or send anything. I upload it myself.
- If you cannot create files, zips or images yourself, give me the full content of every file and exact steps so I can do it by hand.

STEP 1. Understand my system
Read every file in my working folder. Then tell me in at most 5 lines: what it does, which AI it runs on, and which other software it needs. Ask me at most 3 questions, one at a time, only about things you cannot see in the files.

STEP 2. Build the kit
Choose a short slug in lowercase with hyphens (for example "budget-tracker"). In "Ownkit build/<slug>/" create:

READ ME.txt                      4 short steps for the buyer, plain text, max 12 lines. Step 3 is: open your AI in this folder and type: Read Ownkit/START.md and follow it.
Ownkit/
  START.md                       the setup script the buyer's AI follows (rules below)
  Guide.md                       a one-page guide for the buyer
  Templates/
    CLAUDE.md                    the rules for daily use, copied to the buyer's folder (name it after the AI it is for, e.g. CLAUDE.md for Claude)
    dashboard.html               if the system shows information: one self-contained page
    data/                        empty starter data files (.json or .csv)
    skills/<name>/SKILL.md       1 to 3 skills for daily use, if the AI supports skills
  Sample data/                   fictional sample data, clearly marked "Fictional sample data"

READ ME.txt and Ownkit/START.md are required. The rest is strongly recommended.

START.md must be written to the AI ("You are the setup assistant for this kit. ...") and must:
1. Check that the working folder is the buyer's chosen folder and not the Ownkit folder itself. If it is, kindly tell the buyer to reopen the AI one folder up, and stop.
2. Keep progress in Ownkit/progress.md, so the buyer can type "continue" after an interruption.
3. Ask at most 5 short questions, one at a time, each as "Question x of y" with half a sentence on why. Use sensible defaults when the buyer skips.
4. Create the buyer's files in the folder root (rules file, dashboard, data folder, skills). Merge with existing files instead of overwriting them.
5. Offer to load the sample data first, and explain how to clear it.
6. Finish with: what now exists, how to open the dashboard, and three example sentences to try.
7. Contain these ground rules, also in the rules file: plain language, one question at a time, never invent facts or numbers, never ask for passwords, keys or bank logins, never send, publish, pay or trade anything, never delete the buyer's files.

dashboard.html rules: inline CSS and JS only, no network requests (no CDN, web fonts or external images), system fonts, light and dark mode, works at 375 px wide, a clear empty state. Keep the data in <script id="data" type="application/json">...</script> and compute every total and chart from that data in the page, never typed in by hand.

STEP 3. Clean it and check it for safety
Go through every file in "Ownkit build/<slug>/" and:
- Remove all personal and business details: names, email addresses, phone numbers, addresses, client data, company names, account numbers, private notes. Replace them with fictional examples: people as a first name plus "Example" (Robin Example), companies with clearly invented names. Search the web once per invented company name if you can, and pick another if a real business uses it.
- Remove every password, API key, token and secret, and files like .env. Where the buyer needs their own key, tell them where to fill it in. Never ship a key.
- No program files: no .exe, .dll, .bat, .cmd, .ps1, .vbs, .msi, .jar, .scr or .app. Helper scripts (.js, .py, .sh) only if the system really needs them; describe them in Guide.md.
- No hidden instructions: nothing that tells the AI to ignore its rules, hide what it does, send files or data anywhere, or delete things.
- No network calls in the dashboard. If the system really needs the internet, say so clearly in Guide.md.
- Real-world facts (tax rates, health advice, legal rules, prices of other products) must either have a source you actually checked, or become a setting the buyer fills in.
Make a list of everything you removed or changed. You need it in step 6.

STEP 4. Make the zip
Zip the CONTENTS of "Ownkit build/<slug>/" to "Upload Ownkit/<slug>.zip".
- READ ME.txt and the Ownkit folder must sit at the top of the zip, not inside an extra folder.
- Use forward slashes in paths. Leave out __MACOSX, .DS_Store, Thumbs.db, .git and node_modules.
- Keep it as small as possible: under 3 MB lets Ownkit check it automatically, the hard limit is 20 MB.
Then open the zip again and list its files to confirm it is right.

STEP 5. Make 3 or 4 screenshots
Load the sample data and make 3 or 4 screenshots of what the buyer will see, as PNG, 1600 x 1200 pixels (4:3), light mode:
  Upload Ownkit/screenshot-1.png   the main image: the overview with sample data
  Upload Ownkit/screenshot-2.png   a second view (for example a detail or calendar view)
  Upload Ownkit/screenshot-3.png   a third view, or the conversation that updates it
  Upload Ownkit/screenshot-4.png   optional
No personal data may be visible. Check every image: nothing cut off, no empty boxes, numbers match the sample data. If you cannot make screenshots yourself, tell me exactly which screen to open and what to capture.

STEP 6. Write UPLOAD.txt
Create "Upload Ownkit/UPLOAD.txt" with every answer for the upload form, in this order, ready to copy:

NAME (max 40 characters):
CATEGORY (one of: Money, Lifestyle, Home, Kitchen, Freelance, Health, Events, Hobby, Family):
ONE-LINE RESULT, what the buyer has after opening it (max 70 characters, ends with a period):

AI IT RUNS ON (every one that works; per AI "Free plan works" or "Paid plan needed"; if unsure: "Paid plan needed"):
- Claude:
- ChatGPT:
- Gemini:
- Other:

OTHER SOFTWARE THE BUYER NEEDS (or: "None, a web browser is enough"):
- Name | what it is for | required or optional | free, free plan works, paid, or check

SCREENSHOT CAPTIONS (max 80 characters each):
1. screenshot-1.png:
2. screenshot-2.png:
3. screenshot-3.png:
4. screenshot-4.png:

WHAT YOU GET (2 to 4 lines, max 60 characters each):
-
HOW YOU TALK TO IT (1 to 3 example sentences the buyer types, max 60 characters each):
-
SUGGESTED PRICE (one of: 2.99, 4.99, 8.99, 12.99, 19.99 euro) and one line why:

SAFETY CHECK (what you removed or changed in step 3):
-

Writing rules for everything a buyer reads: English, talk to the buyer as "you", concrete, the result first. No hype words (revolutionary, ultimate, AI-powered), no exclamation marks, no long dashes, no promises of results (no "save 5 hours a week", no returns, no "lose weight", no "guaranteed"). Never write prices of other products: write free, paid or "check the vendor's current plans".

STEP 7. Finish
Show me:
1. The folder tree of "Upload Ownkit". It must contain exactly: <slug>.zip, screenshot-1.png to screenshot-3.png (or 4) and UPLOAD.txt.
2. The full content of UPLOAD.txt.
3. Anything you could not check.
Then tell me: go to ownkit.cloud, click "List your kit", upload the zip and screenshots and copy the answers from UPLOAD.txt. Ownkit checks the zip again on upload.

Ownkit checks every zip again on upload: for safety, and whether what you filled in matches the files.