A blueprint for your app before you code

Without a plan, your agent decides the structure of your app for you. This app and workspace blueprint is where you record the decisions, inputs and acceptance checks first, so the work is easier to repeat and share.

It sets out the layout: the web app owns routes, app components, server operations and the local environment; a UI package holds shared presentation and tokens; a domain package holds shared pure business rules. You start with the web app only and add a package when two consumers need it. The root has one lockfile and workspace definition, and each package has a unique name, explicit exports and compatible peer dependencies.

Checks are listed in order: install from the root, typecheck, relevant tests, build, and visit the first user journey. For deployment you document the repository build context, app entrypoint, environment names and output settings. It also supplies the shared blank and filled brief, bug report, verification record and runnable task tracker used by the planning, debugging and testing guides.

You need only a text editor, and you keep the completed plan for your next project. Provider accounts, model weights, GPU compute and hosting are not included.