Boundary
Understand what Terminal is attached to
`Terminal` is scoped to the active Flutty workspace rather than to a separate local shell.
Commands run against the current project runtime
The tab stays tied to the project that is open in generate.
The working directory is workspace-aware
Command output stays relevant to the same codebase you are previewing and inspecting.
Use Terminal for technical checks
This is the place for command-line validation, runtime inspection, and lower-level recovery steps.
Practice
Run commands deliberately
Start from the current working directory
Confirm where the shell is pointing before assuming paths.
Use short validation commands first
Check files, processes, or command availability before heavier steps.
Keep Terminal inside the same recovery loop
If a command reveals a runtime issue, move back to `Website`, `Code`, or the chat thread with that evidence.