@magic-resume-kit/* from npm.
Kenmet is a pnpm + Turborepo monorepo. The root package.json pins the package manager to pnpm@10.28.1 so CI and local installs stay aligned.
What workspaces are available?
What are the package dependency boundaries?
These are enforced by code review rather than tooling. Keep them honest:apps/webmay depend on anypackages/*workspace.packages/resume-templatesdepends onpackages/resume-schema. The reverse must not happen — schema is the leaf.packages/mcpdepends onpackages/resume-schemaandpackages/resume-templates. Not onapps/*.- New shared shapes belong in
packages/resume-schema, not duplicated intoapps/web.
How do I run commands with Turborepo?
The rootpackage.json runs everything through Turbo:
How does the workspace:* protocol work?
Local cross-workspace deps use the workspace:* protocol in package.json. This means you must run pnpm install from the repo root, not from inside a workspace, or pnpm can’t resolve the link.
When you publish @magic-resume-kit/mcp, pnpm rewrites workspace:* to the real version at pack time — no manual bumping needed.
Applications pin exact npm versions for @magic-resume-kit/*; only local packages such as GenUI use workspace:*. Public package releases are handled by GitHub Actions in magic-resume-kit.