Is the project boundary clear?
You can name the folder or set of folders that make up this product.
Local browser diagnostic Windows projects
Check the context around a Windows development project, then turn the missing pieces into a prioritized, reusable checklist.
You can name the folder or set of folders that make up this product.
The first useful action is known and does not depend on memory or shell history.
Executable, arguments, and working directory are all explicit.
Dependent services and processes can be started in a deliberate sequence.
You know whether a command runs on Windows or inside a container.
Missing SDKs, executables, package managers, or engines can be identified early.
The current branch and uncommitted work are visible before the next task begins.
A failure can be compared with a known command, target, timing, and earlier result.
A release or hand-off does not rely on uploading private source to an unknown scanner.
From vague friction to an action list
Use it when returning to an old project, preparing a hand-off, or diagnosing why starting work takes too long. “Yes” should mean that another person—or you in three months—could actually find the stated context.
The score is deliberately simple. It does not run commands, inspect folders, test ports, connect to databases, or certify that a project is healthy.