npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@code-fixer-23/create-pi-package

v1.2.3

Published

Scaffold PI packages with prompts, skills, and extensions.

Readme

@code-fixer-23/create-pi-package

Scaffold PI packages with the familiar create-* flow.

create-pi-package asks which PI resource folders you want, creates the matching starter files, adds a scripts/create-* helper for each selected resource, and optionally sets up extension testing.

Feature highlights

  • Uses a familiar create-* scaffolding flow for PI packages
  • Lets you choose one or many resource folders in a single run
  • Generates starter files for extensions, prompts, skills, and themes
  • Adds matching scripts/create-* helpers for every selected resource
  • Supports creating files in a new folder, an existing folder, or directly in .
  • Sets up extension testing with either jest or vitest
  • Generates a strict tsconfig.json when extension tooling is needed
  • Creates a ready-to-edit package.json for extension packages
  • Auto-detects the invoking package manager for dependency installation
  • Can also create AGENTS.md and CLAUDE.md

Usage

npm create pi-package
npm create pi-package my-pi-package
npm create pi-package .
npm create pi-package my-pi-package --project-folders extensions prompts --runner vitest
  • Omit the folder argument to scaffold in the current working directory
  • Pass . to explicitly scaffold in the current working directory
  • Pass a folder name like my-pi-package to create or target that folder

What it generates

Depending on your selections, the package can create:

  • extensions/index.ts
  • prompts/example.md
  • skills/example/SKILL.md
  • themes/theme.json
  • matching scaffold scripts in scripts/
  • AGENTS.md and CLAUDE.md when --instructions is used

If extensions is selected, it also generates:

  • a strict tsconfig.json
  • either vitest.config.ts or jest.config.cjs
  • a package.json with test scripts and dev dependencies
  • dependency installation by default
  • install commands based on the invoking package manager (pnpm, npm, yarn, or bun)

Example generated tree

For example, if you choose extensions, prompts, and skills, you will get a structure like this:

my-pi-package/
├── extensions/
│   └── index.ts
├── prompts/
│   └── example.md
├── skills/
│   └── example/
│       └── SKILL.md
├── scripts/
│   ├── create-extension.ts
│   ├── create-prompt.ts
│   └── create-skill.ts
├── package.json
├── tsconfig.json
└── vitest.config.ts

If you choose jest instead of vitest, jest.config.cjs is generated instead of vitest.config.ts.

Prompt flow

Step 1 — Choose what to include

Question:

What do you want to include in this PI package?

Choices are presented in this order:

  • extensions
  • prompts
  • skills
  • themes

You can select one or many. For every selected folder, create-pi-package creates:

  • a starter file in that folder
  • a matching scripts/create-* helper

Bypass key: --project-folders <folders...>

Example:

npm create pi-package my-pi-package --project-folders extensions prompts skills

Step 2 — Choose a test runner

This question is only asked if you selected extensions.

Question:

Which test runner do you want to use?

Choices are presented in this order:

  • jest
  • vitest

Your choice controls which config file is generated:

  • jestjest.config.cjs
  • vitestvitest.config.ts

A strict tsconfig.json is also generated for extension packages.

Bypass key: --runner <jest|vitest>

Example:

npm create pi-package my-pi-package --project-folders extensions --runner vitest

Non-interactive examples

Bypass the folder selection step:

npm create pi-package my-pi-package --project-folders prompts themes

Bypass the test runner step for an extension package:

npm create pi-package my-pi-package --project-folders extensions --runner jest

Bypass both interactive steps at once:

npm create pi-package my-pi-package --project-folders extensions prompts skills themes --runner vitest

Scaffold directly into the current directory:

npm create pi-package . --project-folders prompts themes

Add agent instruction files without prompts:

npm create pi-package my-pi-package --project-folders prompts --instructions

Skip dependency installation for extension scaffolds:

npm create pi-package my-pi-package --project-folders extensions --runner vitest --no-install

CLI options

  • --project-folders <project-folders...> folders to generate
  • --runner <runner> test runner to use when extensions is selected
  • --instructions also create AGENTS.md and CLAUDE.md
  • --no-install skip dependency installation