v0.7.0
Released: August 8, 2026
This release is about AI coding agents: a set of installable agent skills that teach your assistant how tsdevstack works, an init that sets them up for you, and a scaffold that tells any agent where to find what it needs.
Agent skills for your AI assistant
tsdevstack now ships twelve vendor-neutral agent skills: small instruction files that load into your AI assistant and trigger automatically when your work touches what they cover. They encode the parts of the framework an agent would otherwise guess at: the two-layer auth model and its decorator matrix, the endpoint pipeline from decorators to gateway routes, how secrets are scoped and read, database schema changes, messaging, object storage, running locally, service and worker lifecycle, the frontend BFF pattern, which deploy command already includes which steps, and deploy troubleshooting.
Install them into your agent of choice:
The skills follow the open Agent Skills format, so they work with Claude Code, Cursor, Codex, and the other agents the skills CLI supports. Each skill stays short and links to the matching docs page; your agent reads one source of truth instead of a copy that can drift.
init sets up the skills for you
At the end of scaffolding, init now offers to install the skills. When init runs non-interactively, which is how AI agents and CI run it, there is no prompt to answer, so a new flag carries the answer instead:
With --agent, the skills install for that agent without any prompting. A wrong agent id never breaks the scaffold: the project is complete by that point, the skills CLI prints the list of valid ids, and init finishes with a hint so you can install any time with the command above.
New projects come with an agent guide
Scaffolded projects include an AGENTS.md that tells any AI assistant how to work in a tsdevstack repo: use the MCP server for framework operations, follow the skills when installed, and fetch the docs for depth. It states the guardrails that prevent the classic mistakes, such as editing generated files, scaffolding services by hand, or reading secrets from process.env, and it points agents at tsdevstack.dev/llms.txt so they can discover every docs page on their own.
Database migrations, documented
A new page under Local Development covers the full migration workflow in one place: prisma migrate dev creates migrations locally, sync and cloud deploys only apply what you committed, and infra:plan-db-migrate / infra:run-db-migrate handle the manual cases. Framework behavior is unchanged; the page documents what already happens so you, and your agent, no longer have to infer it.
nest-common 0.7.0
@tsdevstack/nest-common releases alongside the CLI to keep the two in step. This one only refreshes the package's inline documentation: hovers and generated docs now name the guard AuthGuard, matching the shipped code. No code change, nothing to migrate.
Upgrading an existing project
A minor version does not arrive through your existing ^0.6 ranges; update them explicitly. The CLI is a root devDependency; nest-common lives in each NestJS service, so update it per service:
Nothing else changes in your project. To bring the agent tooling in:
And if you want the agent guide too, copy AGENTS.md from a freshly scaffolded project into your repo root; it is generic to any tsdevstack monorepo.
New projects get all of this from the templates automatically.