new-package

Generate a new package scaffold with standard files and tests in the monorepo.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/kjfsm/notion-headless-cms --skill new-package-kjfsm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-package
Source: https://github.com/kjfsm/notion-headless-cms/tree/main/.claude/skills/new-package
Command: npx skills add https://github.com/kjfsm/notion-headless-cms --skill new-package-kjfsm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This process automates scaffolding for a new package in the monorepo, providing a ready-to-use skeleton that follows the project's conventions for package.json, tsup, tsconfig, src/index.ts, and tests.

Core Features & Use Cases

  • Generates a ready-made package scaffold under packages/<name> with standard configuration files and test structure.
  • Enforces monorepo conventions and naming to ensure consistency across packages.
  • Disables automatic model invocation and requires explicit invocation via /new-package <name> to trigger creation.

Quick Start

Run the new-package skill with the target name to generate the scaffolding under packages/.

Frequently Asked Questions about new-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new TypeScript package in a monorepo?

Scaffolding a new TypeScript package in a monorepo involves generating a ready-to-use skeleton under packages/<name> with standard configuration files including package.json, tsup, tsconfig, src/index.ts, and __tests__.

What files are generated when creating a new monorepo package?

Creating a new monorepo package generates standard files including package.json, tsup, tsconfig, src/index.ts, and __tests__ directories to ensure the new package follows project conventions and maintains a consistent structure.

How do I enforce naming conventions for new packages in a monorepo?

Enforcing naming conventions for new packages in a monorepo is handled automatically by this skill, which integrates with the monorepo workflow to support consistent naming and structural placement under the packages/ directory.

Does creating a new package trigger automatic model invocation?

No, creating a new package does not trigger automatic model invocation. The skill explicitly disables automatic model usage to avoid side effects during generation and requires explicit invocation via the /new-package <name> command.

Can I use this scaffolding tool for packages outside a monorepo?

No, this scaffolding tool is designed specifically for monorepo environments. It enforces monorepo conventions and integrates directly with the monorepo workflow to ensure consistent structural placement under the packages/ directory.