package-authoring

To scaffold a TypeScript package in a pnpm monorepo, this Skill generates a complete skeleton at packages/{name}/ including src/, package.json, tsconfig.json, and test files. It enforces naming conventions like @recallnet/skunk-{name} and configures tsup and ESLint automatically.

A reusable workspace package requires a standardized folder structure with src/ for code, package.json for exports, tsconfig.json for TypeScript paths, and tsup for builds. This Skill enforces these conventions across the monorepo to ensure consistency and future TradeCore promotion.

Yes, you can enforce ESLint and tsup build configuration across monorepo packages. This Skill provides step-by-step guidance for setting up TypeScript config, tsup builds, and ESLint rules to maintain standard exports and lint standards.

Yes, this scaffolding tool supports pnpm workspace integration out of the box. You scaffold a new package under packages/{name} from the repo root and run pnpm install to integrate it into the monorepo workflow and begin development immediately.

The naming convention for Skunkworks workspace packages is @recallnet/skunk-{name}. This Skill enforces this naming pattern alongside standard exports, lint rules, and build configuration to maintain consistency across the monorepo.

You should use a standardized package skeleton for monorepo development when building reusable libraries that span multiple executors. This approach enforces folder structure, naming conventions, and tooling, accelerating package work and defining clear promotion guidelines toward TradeCore.