Uses / The working set
Dependable tools over a crowded dock. This is the opinionated core of the setup, not every application installed.
Primary system
Enough power for local services, containers, design review, and the browser tabs that arrive with real delivery work.
~/products/active
$ php artisan queue:work
$ npm run build
local system ready
Hardware / operating system
Working workflow
Build the product, reason through the uncertain parts, then check the real interface. Each tool has a specific job in that route.
Build
A deliberately small loop for turning product decisions into working software.
The editor I still trust for daily Laravel work.
My primary terminal for development and operations.
A deliberately boring local Laravel environment.
Fast database inspection and quick framework experiments.
Focused API checks while shaping and debugging flows.
Think
The model changes with the question: implementation, architecture, or product shape.
Implementation, repository work, and longer coding tasks.
Architecture exploration, review, and writing through ambiguity.
Useful when an editor-shaped AI workflow fits the task.
Notes, product shape, and interface conversations before code.
Inspect
The work is not finished until the real interface and production path hold up.
The browser I use for focused daily work.
Compatibility, DevTools, and production checks.
The macOS and WebKit sanity check that cannot be skipped.
Two quiet utilities that remove small daily friction.
Tools in context
