Understand the f0 website/video AI router’s specialist routes, project-type boundaries, and when a CMS or custom-code request takes priority over general design work.
Where: Editor → AI assistant panel (or ⌘⇧K) — Open the assistant and type a request
Key ideas
- The router chooses a specialist: The f0 Assistant routes requests among research-to-design, design, interactions, element editing, image/video generation, settings, HTML, code components, and video direction.
- Project type changes the meaning: VideoDirector is only valid for a video project; an ambiguous “scene” in a website should not be sent to the flowMotion video director.
- Some requests have priority routes: CMS/WordPress/publishing terms route to settings; custom JavaScript/WebGL/API integrations route to Code Component; follow-up edits after a design route to Element Editor.
Steps
- Open the f0 AI Assistant and state the requested outcome and whether it is a new design, an edit to existing elements, interaction behavior, media generation, site settings, code, or video work.
- Select the target element/page when useful; selection scopes many edit routes, while clearing selection signals broader work.
- For CMS/WordPress/publishing tasks, name the target system and route; for custom scripts/WebGL/API work, ask for a Code Component.
- Use a Video project for Video Director requests. In a website project, describe video media separately from editing a flowMotion timeline.
- Review the planned route and proposed changes; clarify when the wrong project type or scope is selected.
Specialist route map
- Research-to-design: end-to-end research and new design workflows.
- Design: a new full-fidelity page, section, or styled element; Interactions: triggers, animation, scroll effects, and carousels.
- Element Editor: scoped revisions to existing selections; image generation: create/edit/analyze images; video generation: generate prompt/image-based video.
- Settings: CMS, WordPress, publishing, site and integration setup; HTML: direct markup work when no more specific route applies.
- Code Component: custom JavaScript-powered interactivity such as WebGL, particles, shaders, widgets, or API integrations.
- Video Director: scenes, clips, trims, transitions, audio beds, presentation stops, and rendering in a project whose projectType is video.
Routing exceptions and limits
- An active research-to-design plan generally remains on its orchestrator route until the plan completes.
- CMS/WordPress/publishing keywords take priority over general design/interactions routing.
- A post-design follow-up edit routes to Element Editor unless the user asks for a new page/section/design.
- Code Component supports all project types, but it is distinct from direct HTML work and from the native flowMotion video director.
- Routing is probabilistic; when the user’s intent is ambiguous, the assistant should clarify instead of silently choosing a high-impact route.
Tips
- Select the narrowest target before an edit request.
- Ask for a plan or stop-before-run boundary for multi-page, expensive, or destructive work.
Limitations and important notes
- Available routes, tools, attachments, and models depend on the current surface, plan, and permissions.
- AI output still requires visual, responsive, accessibility, factual, and cost review.
Troubleshooting
The assistant edits the wrong scope
Undo, select the exact element/group, remove irrelevant attachments, and restate whether structure or content may change.