typescript-backend-project-setup_skill

Overview

This skill sets up an NX monorepo tailored for TypeScript backend projects with strict typing, enforced linting, 100% test coverage, and AI-friendly project conventions. It prefers NX generators and commands, only patching files when necessary, and also copies templates for AI guardrails, docs, and git hooks. The workflow guides you from initial questions through verification and optional architecture documentation.

How this skill works

It prompts for workspace name, domain description, claude-skillz template path, target directory, and initial apps/packages. It runs NX workspace generators, installs recommended plugins (vitest, eslint, @nx/node), generates libraries and apps, and syncs TypeScript project references. Finally it copies template files that NX cannot create (AI integration, docs, custom ESLint rules, and husky hooks) and applies strict patches to nx.json, tsconfig.base.json, eslint.config.mjs, package.json, and vitest configs.

When to use it

• You want a TypeScript backend monorepo scaffolded for AI-assisted development
• Starting in an empty or near-empty project folder
• You require strict type safety and automated lint/test gates
• You need preconfigured CI-friendly tooling (vitest, eslint, husky)
• You want built-in AI guardrails and documentation templates

Best practices

• Provide the full path to your local claude-skillz template before starting
• Prefer NX generators and nx sync; patch files only when generators can’t create required content
• Use pnpm and the NX commands shown (create-nx-workspace, nx g, nx add) for repeatability
• Run nx report and initial verify steps to confirm versions and scripts work
• Keep custom templates updated with NX docs to avoid breaking changes

Example use cases

• Create a new workspace with publishable packages (packages/query, packages/builder) and a Node API app
• Initialize a team repo that enforces 100% coverage and strict TypeScript rules for AI code generation
• Scaffold a domain-focused monorepo that forbids generic utils/shared folders and enforces naming conventions
• Add Claude integration, documentation skeleton, and pre-commit hooks to an existing empty folder