Group the editor, terminal, browser and supporting tools you already use, while keeping project files and automated workflows outside the launcher arrangement.
A development folder works best when it represents a real session. Start with the editor, terminal and browser you repeatedly open together. Database, device or deployment utilities can stay in a separate occasional-tools group instead of starting with every project.
Use Open All with a deliberate membership
Relaunch can launch the available apps in a folder together. That is useful for a small starting set, but it does not choose a repository, run shell commands or restore every application’s project state.
Test each app individually before adding it to the shared launch group. If the setup needs inputs or a sequence of actions, use a workflow you understand in Shortcuts or the relevant development tool.
Separate visual context from process state
A Work layout can bring development tools forward in the grid. Switching to Personal later does not stop a server, terminate a terminal task or close an editor. Handle those processes deliberately in their owning tools.
Keep the setup portable
Use clear app and folder names.
Back up the working arrangement.
Install the required tools separately on another Mac.
Verify the project workflow there rather than treating a synced grid as a complete development environment.