Full-stack monorepo preset, packkit.json provenance, agent tool steering

[DanMat]

Three items from the field review, plus a bug the testing turned up.

Full-stack monorepo preset

fullstack (alias fs), or --monorepo-layout fullstack:

apps/web         React + Vite
apps/server      Hono API — also serves the web build in production
packages/shared  types + helpers both sides import

The reviewer's sharpest complaint was scaffolding pieces separately and merging them by hand. The parts already existed (node-service, react-app) — the composition didn't. Vite proxies /api to the server so requests are same-origin in dev exactly as in production (no CORS, no environment-specific base URL), and turbo dev builds shared before either app starts, so a changed shared type surfaces as a type error on both sides rather than at runtime.

The existing monorepo preset is untouched and stays the default layout.

This is why generating isn't verifying

I installed the generated workspace and ran the real toolchain instead of eyeballing the file list. It failed, twice:

• No @types/react → turbo typecheck failed with TS7016/TS7026 on every JSX element.
• A test script with no test files → vitest exits 1, so turbo test failed.

Both are exactly the "subtly wrong" plumbing a scaffolder is supposed to eliminate. Fixed, then re-verified end to end:

BUILD      3 successful, 3 total
TYPECHECK  4 successful, 4 total
TEST       4 successful, 4 total   (shared, server, web — all pass)

And the production claim in the README was checked rather than assumed — NODE_ENV=production node dist/index.js serves /api/health as JSON and / as the built web app, one process, one port.

packkit.json provenance

Records generator version, preset, and only settings that differ from the defaults, so it reads as the decisions someone made rather than a dump of every option. Packkit previously left no trace, so a project couldn't say what it started from — this is the prerequisite for any future packkit upgrade.

Deliberately no timestamps or machine details: generation stays a pure function of the config, so the same config produces the same bytes. There's a test for that.

Agent tool steering

MCP descriptions now push agents to packkit_schema first and frame packkit_preview as the structure-preview step. The reviewer asked for preview_project_structure "as a default pre-scaffold step" — that tool exists, as packkit_preview. Them not finding it was the finding.

Also

The MCP scaffold path now writes a lockfile before pushing, matching the CLI. Without it, a repo created through MCP failed its first CI run.

48 tests pass.

🤖 Generated with Claude Code