Navigation

Stellify has no file tree. You navigate the way you reason about a Laravel app — which branch, which route, which file, which method — and the navigation bar holds exactly that, as a breadcrumb of dropdowns:

Read left to right: you're on main, editing the Home route, with UserController open at the store() method. Change any level and everything to its right follows.

On the far right, three buttons switch how the canvas renders — Interface (visual builder), Code (method editor), Split (both) — followed by Settings (project configuration) and your profile (account and API tokens).

Branch Dropdown

Click a branch to switch to it — every edit you make from that moment lands on that branch, invisible to collaborators on main until you merge. Type a name and hit Create to branch off main (subscription required). The green dot marks main; the checkmark marks where you are now.

Diff, merge, and discard live alongside switching — see Version Control for that workflow.

Route Dropdown

Routes are the entry points of your app, and in Stellify they're also how you choose what to work on: select a route and the canvas loads that page.

Pages and API endpoints are listed separately, endpoints with their HTTP method badges. From here you:

• + New Page — create a route; give it a path and it's immediately editable on the canvas
• Route Settings — path, name, controller and method wiring, middleware, and the public flag that enables share links
• Share Page — grab the share/embed URLs for a public route
• Delete Page — remove the route (confirmed first)

Agents manage routes through create_route and save_route — a scaffolded feature usually arrives with its routes already wired, and this dropdown is where you inspect and adjust them.

File Dropdown

Files are grouped by what they are — controllers, models, middleware, services, Vue components — not by directory path.

• + New File — one file: pick the type, name it, start writing
• Create Resources — the whole stack at once: Model, Controller, Service, and Migration, pre-wired to each other. Prefer this over creating CRUD files individually; it's the same scaffold agents use via create_resources
• Close File — drop the file from the breadcrumb

With a JavaScript file selected, this menu also holds the bundling options.

Method Dropdown

The last breadcrumb lists the methods in the open file, each with its return type. Select one and the code view shows just that method — the unit you edit, run, and that agents target.

+ New Method adds an empty method to the file; configure its signature via the cog in the Code Editor.

AI Chat Panel

The chat panel opens from anywhere and already knows your position in the breadcrumb — ask for "a findByEmail method here" and it targets the open file without you spelling out paths.

Pick the model per task from the selector — Haiku for quick mechanical edits, Sonnet as the default, Opus for work that spans many files. The agent applies changes directly to your project; the canvas and code view update as it goes.

Next Steps

• Code Editor - What happens after you select a method
• Interface Builder - What happens on the canvas
• Version Control - Branch, diff, and merge