Project setup

Make the next feature easy to locate, run, and verify. Inspect the repository, manifests, lockfile, and local instructions first. Improve existing conventions before introducing new ones.

Work

• Confirm runtime, package manager, framework, deploy target, and actual commands. Distinguish existing tooling from proposed additions.
• Place route composition, feature logic, reusable primitives, validation, and data access near their owners. Do not create empty folders for hypothetical scale.
• Choose one token source and identify how primitives consume it. Reuse an existing UI library; a new repository does not require a custom Button.
• Document environment variable names and safe placeholders. Keep secret validation and access server-side; never import a secret-bearing environment object into browser code.
• Set the smallest useful verification path: types/lint/build and a meaningful check of the first critical flow. Add infrastructure when it addresses a concrete risk.
• On existing projects, preserve user edits and change only the foundation implicated by the task. Explain migration effects on consumers.

Deliver

For planning, give actual/proposed paths, commands, and an ordered setup sequence. For implementation, create the authorized foundation and run its checks rather than stopping at a checklist.

## Foundation plan