Summary
FlowMaster currently supports Next.js and Astro route detection, but SvelteKit projects are not fully recognized. SvelteKit uses a file-based routing system under src/routes/ with conventions like +page.svelte, +layout.svelte, +server.ts, and +page.server.ts.
What needs to happen
- Detect SvelteKit projects (look for
svelte.config.js or svelte.config.ts)
- Parse
src/routes/ directory structure
- Map SvelteKit route files to appropriate node types:
+page.svelte → Page node
+layout.svelte → Layout node
+server.ts → API endpoint node
+page.server.ts → Server load function node
+error.svelte → Error boundary node
- Handle route groups
(group) and parameter routes [param]
Relevant files
flowmaster.md — the skill file where node types and detection logic are defined
Getting started
- Read through
flowmaster.md to understand existing node type definitions
- Look at how Next.js routes are currently detected as a reference
- Add SvelteKit-specific patterns following the same conventions
Summary
FlowMaster currently supports Next.js and Astro route detection, but SvelteKit projects are not fully recognized. SvelteKit uses a file-based routing system under
src/routes/with conventions like+page.svelte,+layout.svelte,+server.ts, and+page.server.ts.What needs to happen
svelte.config.jsorsvelte.config.ts)src/routes/directory structure+page.svelte→ Page node+layout.svelte→ Layout node+server.ts→ API endpoint node+page.server.ts→ Server load function node+error.svelte→ Error boundary node(group)and parameter routes[param]Relevant files
flowmaster.md— the skill file where node types and detection logic are definedGetting started
flowmaster.mdto understand existing node type definitions