Create the TaskFlow Root Repository A clean PowerShell build of the Git repository, pnpm workspace root, version pins, lockfile, and structural directories.
Create the TaskFlow Root Repository Now we build the repository from nothing. The lesson is intentionally small: create the root, make it a Git repository, establish package-manager metadata, and verify each file before frameworks enter the picture.
Step 1 - Choose the parent directory Run repository-creation commands from the directory that should contain taskflow, not from inside another project. This avoids accidental nested repositories and confusing workspace roots.
Get-Location
Get-ChildItem -ForceC:\Users\<you>\Desktop\Projects
Step 2 - Create and enter the repository folder New-Item -ItemType Directory -Name taskflow Set-Location .\taskflow Get-Location
Expected: the current path ends in taskflow. Do not continue until that is true.
Step 3 - Initialize Git
git init
git statusAt this point Git knows the folder is a repository, but there are no committed files yet. The hidden .git directory contains repository metadata; never edit it manually during normal work.
Step 4 - Create the minimal root package.json Use the editor and create package.json at the repository root:
{ "name": "taskflow", "version": "0.0.0", "private": true, "packageManager": "pnpm@12.4.2", "engines": { "node": ">=24.21.0 <25" }, "scripts": { "workspace:list": "pnpm list -r --depth -1" } }
Why private: true? The root package exists to coordinate the repository. It is not a package we intend to publish to a registry, so marking it private protects against accidental publication.
Step 5 - Pin Node for the repository Create a file named .node-version containing exactly:
fnm supports .node-version files. With automatic switching configured in Phase 01, entering the repository can select the course Node version without relying on memory.
Step 6 - Create pnpm-workspace.yaml packages: - "apps/*" - "packages/*"
pnpm requires pnpm-workspace.yaml at the workspace root. These patterns mean: any immediate child folder under
apps/ or packages/ that contains a package.json can participate as a workspace package.pnpm-workspace.yamlglob glob
apps/* packages/*future match future match
apps/web packages/validatorsFigure 1 - The workspace file declares locations; it does not create packages by itself
Step 7 - Create the structural directories New-Item -ItemType Directory -Path .\apps -Force New-Item -ItemType Directory -Path .\packages -Force Get-ChildItem -Force
Git and empty Git tracks files, not empty directories. If apps/ and packages/ are still empty at directories commit time, they will not appear in a clone. That is fine. Phase 03 and later will put real package files inside them. Do not create meaningless .gitkeep files just to make the tree look complete.
Step 8 - Install the workspace pnpm install
Because the workspace has no framework dependencies yet, the install should be small. Its important result is the workspace lockfile: pnpm-lock.yaml. Commit that lockfile. It records exact dependency resolution for reproducible installs.
Step 9 - Verify the root metadata
node --version
pnpm --version
pnpm run workspace:list
git statusAt this point workspace:list may show only the root project because no app package exists yet. That is expected. A workspace declaration is not the same as a populated workspace.
Checkpoint before Git hygiene files taskflow/ |-- .git/ |-- .node-version |-- apps/ |-- packages/ |-- package.json |-- pnpm-lock.yaml `-- pnpm-workspace.yaml
Verify JSON and YAML problems early A missing comma in package.json or incorrect indentation in YAML can make later framework generators appear broken. When a tool fails before it starts meaningful work, inspect these root configuration files first.
Smallest useful Do not reinstall Node or pnpm because package.json has invalid JSON. Fix the correction layer that produced the failure: configuration syntax.
Checkpoint • Get-Location points to taskflow. • git status works and reports this repository. • node --version and pnpm --version match the course baseline. • pnpm-workspace.yaml exists at the same level as package.json. • pnpm install succeeds and creates pnpm-lock.yaml. • No Next.js, NestJS, Prisma, Turbo, or shared package has been installed yet.
Create the TaskFlow Root Repository matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Create the TaskFlow Root Repository” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: service intent → repository contract → adapter → Prisma/Postgres → domain result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: TaskFlow repository root with apps/web, apps/api, shared packages, workspace metadata, root scripts, and clean Git hygiene.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
export interface TaskRepository {
findById(id: string): Promise<Task | null>;
listForWorkspace(input: TaskListQuery): Promise<TaskPage>;
save(task: Task): Promise<void>;
}Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Create the TaskFlow Root Repository” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Declare workspace globs and explain why apps and packages are separate categories.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Duplicating tsconfig settings in every package
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.