Project kit On-device
Nine prompts from idea to repo instructions. Each stage's reply feeds the next.
Why
- Most projects fail on the problem, not the code. One page forces the problem into words before anything is built.
- It is the page you send to anyone you want help from — a developer, a partner, a first customer.
What good looks like
- The problem is stated without mentioning the solution.
- The user is one specific person, not "everyone who…".
- The metric has a number and a date.
Paste only the sections under these headings from the reply you got. Only these travel to the next stage.
Headings and structure stay in English in every export — that is what the models were trained on. Your own text is left as written.
≈ 237 tokens
## Role You are a product strategist who writes one-page briefs that a developer and a non-technical founder can both read. ## Context (No context captured yet — add inputs in earlier stages.) ## Task Write a one-page brief for this idea. Sharpen the problem before describing any solution. Name the one person it is for. Propose one measurable sign of success for the first month. ## Constraints - If an input you need is missing, ask at most three questions before proceeding; otherwise proceed. - No filler, no marketing tone, no praise of the idea. - Mark anything you assumed with "(assumed)". - Answer in the language the inputs are written in; keep headings in English. ## Output format Return exactly these sections, in this order, with these headings and nothing before the first one: ## Problem statement ## Target user ## Success metric Keep each section under 150 words. Plain language first, detail second. Use bullet lists where the content is a list.
Everything runs on your device. Nothing you paste is sent anywhere, and it's cleared when you close the tab.Download all first.
Project kit turns an idea into nine prompts, one per stage from the one-pager to CLAUDE.md. Send each prompt to any assistant, paste the named sections of its reply into the capture boxes, and only those sections travel to the next stage. Headings stay in English in every export. Your inputs live in this tab only, so download the kit before you close it.
About this tool
What you provide
- Plain-words answers for each of nine stages.
- Sections pasted from an assistant's reply.
What you get
- One Markdown prompt per stage, or chat-message JSON.
- A .zip of nine prompts, your extracts and a README manifest.
Limits
- The token figure is an estimate.
- Nothing is saved after the tab closes.
- Headings stay in English in every export.
How to use it
-
Answer the stage
Fill the plain-words inputs for the current stage.
-
Send the prompt
Copy the prompt, send it to any assistant, and paste each named section of the reply into its capture box.
-
Move on and download
Go to the next stage, and use Download all (.zip) before you close the tab.
Frequently asked questions
What actually travels from one stage to the next?
Only the sections you paste into the capture boxes. A stage never sees whole replies or earlier inputs, apart from the project name and one-line idea.
Why are the headings in English?
Models were trained mostly on English headings, so every prompt and export keeps them in English. Your own text is left as written.
Is my project saved anywhere?
Only in this tab's session storage. Closing the tab clears it, so use Download all (.zip) first. Nothing is uploaded.