GitHub Spark Prompt Generator

Generate a compelling, feature-rich prompt for GitHub Spark — a no-code app builder that creates entire apps from a single prompt.

What This Produces

A single, self-contained prompt that:

• Opens with a vivid, specific description of the app's purpose
• Enumerates features as user-facing capabilities and visible elements
• Conveys the desired look, feel, and UX personality
• Ends with an extensibility hook for easy future iteration
• Does not include: file/folder structure, coding standards, implementation instructions, framework choices, or README requests

Procedure

Step 1 — Gather the App Idea

Read the user's argument or the conversation. If the app idea is clear and specific, proceed to Step 2. If it's vague or missing key details, ask only the questions that are genuinely unanswered:

Do not ask about anything already evident from the idea.

Step 2 — Draft the Spark Prompt

Use the template below as a structural guide. Write in flowing, specific prose — avoid generic phrases like "user-friendly" or "intuitive".

DO:

• Open with a punchy one-sentence elevator pitch naming the app and its purpose
• Use evocative, concrete language: "a pulsing live feed", "drag-and-drop kanban lanes", "a glanceable at-a-glance dashboard"
• Describe everything from the user's perspective: "users can…", "the app surfaces…", "tapping X reveals…"
• Include a visual/UX direction: color mood, layout style, motion character
• Close with an extensibility statement tailored to the app's natural growth axes

DON'T:

• Mention filenames, directories, or project layout
• Specify languages, frameworks, libraries, or patterns
• Give implementation instructions ("use a REST API", "persist in localStorage")
• Request a README or any documentation

Step 3 — Validate

Before presenting, run through this checklist:

• Is the core purpose immediately clear in the first sentence?
• Are all features described as user actions or visible elements, not technical choices?
• Is the language vivid and specific, not generic?
• Is there a clear UX/visual direction?
• Does the prompt end with an extensibility hook?

Revise any section that fails a check.

Step 4 — Present and Offer to Iterate

1. Deliver the final prompt in a fenced code block for easy copying
2. Note 1–2 assumptions made (scope, tone, key feature prioritization)
3. Ask if any feature, tone, or scope adjustment is needed
4. Offer to write a follow-up iteration prompt once the first Spark version is built

Prompt Template

[App Name] is a [vivid one-sentence description of what the app does and who it's for].

**Core Experience**
[2–3 sentences on the primary workflow and what makes it feel great to use. Be specific about layout, interactions, and visual energy.]

**Features**
- [Feature 1: user capability or visible element]
- [Feature 2]
- [Feature 3]
- [Feature 4]
- [Feature 5+]

**Look & Feel**
[1–2 sentences on color palette mood, typography style, motion/transition character, and overall visual personality.]

**Extensibility**
The app should be designed so that [specific growth axis — e.g., new categories, additional views, or extra data fields] can be added with minimal friction as the tool evolves.