Launchframe
Intake
Turn a vague app idea into a locked project brief.
What you need before starting
- Know the working app idea and what the setup flow should produce.
- Keep route scope limited to the required setup pages for v1.
Project brief
Fill these fields to lock context for commands and prompts in later phases.
Clears saved brief, preview, and checklist progress for this flow.
Project basics
Lock the name, repository, folder, and project summary first.
Pages and usage
Capture the main user action, secondary actions, and route summary.
Use one action per line for readable prompt output.
Use one route per line to keep the setup flow explicit.
Visual direction and UX rules
Capture the visual tone and the required interaction rules.
List one rule per line when possible.
Shared components, UI states, and done state
Capture what the agent must build and how completion is judged.
Live preview
Updates as you type; used by generated outputs on later pages.
Current project input
Driven by the shared project context used across the flow.
- Project name
- —
- Repo name
- —
- Folder name
- —
- One-line description
- —
- Target audience
- —
- Primary goal
- —
- Primary visitor action
- —
Secondary actions
—
Routes and pages
—
Visual direction
—
UX rules
—
Constraints
—
Required shared components
—
Required UI states
—
Definition of done
—
Before scaffold
Check these off when the brief is ready to continue.