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

@yaguaretech/dev-kit

v1.0.3

Published

CloudCastle standard dev tooling — Claude Code skills, AI rules, git hooks, and PR templates

Readme

generic-project / @yaguaretech/dev-kit

Standardized dev tooling for all Yaguaretech projects — Claude Code skills, AI rules, git hooks, and PR templates.


Option A — Add to an existing project (recommended)

npm install --save-dev @yaguaretech/dev-kit
npx ccdk init
git init        # skip if already a git repo
npm install     # installs husky and activates the commit hook

That's it. You'll get:

  • 9 Claude Code skills in .claude/skills/
  • AI rules and coding conventions in ai-rules/
  • PR template in .github/pull_request_template.md
  • Commit message validation hook via Husky

Open the project in Claude Code and type /boot-app to get started.

Updating to the latest skills/rules

npm update @yaguaretech/dev-kit
npx ccdk update

Option B — Bootstrap a brand new project

bash scripts/setup.sh

The setup script will ask you:

  1. Project name
  2. Package manager — npm / pnpm / yarn
  3. Stack:
    • Next.js only
    • Next.js + Prisma
    • Next.js + Supabase
    • Next.js + Prisma + Supabase
    • Next.js + Prisma + AWS SDK
    • Next.js + Supabase + AWS SDK
  4. Auth — None / NextAuth.js / Supabase Auth / Clerk
  5. AWS SDK (if not already included in the stack)
  6. Testing — None / Jest / Vitest
  7. Git init

It then creates a new project directory with the selected stack, pre-configured Claude Code skills, and a .env.example.


What's included in every generated project

Claude Code Skills (.claude/skills/)

| Skill | What it does | |-------|-------------| | /boot-app | Start the dev server, check env, run prisma generate if needed | | /commit | Conventional commit workflow with confirmation | | /initial-task <ID> | Set up workspace for a Jira/ClickUp ticket | | /install-clickup-mcp | Install ClickUp MCP server | | /install-figma-mcp | Install Figma MCP server | | /list-endpoints | Scan and table all API routes | | /qa-analysis | TypeScript + lint + tests + build check | | /test-coverage | Test suite with coverage report | | /test-endpoint METHOD /path | Fire a curl at a local endpoint |

AI Rules (ai-rules/claude/)

  • README.md — full skills reference Claude reads for context

Config templates

| Stack addition | Files generated | |---------------|----------------| | Prisma | prisma/schema.prisma, lib/db.ts (singleton client) | | Supabase | lib/supabase/client.ts, lib/supabase/server.ts | | AWS SDK | lib/aws/config.ts (S3 + SES pre-wired) |


Repository structure

generic-project/
├── .claude/
│   ├── settings.json          # pre-allowed commands
│   └── skills/                # one .md file per skill
├── ai-rules/
│   └── claude/
│       └── README.md          # skills reference for Claude
├── scripts/
│   └── setup.sh               # interactive project generator
├── templates/
│   ├── base/                  # tsconfig, .gitignore
│   ├── stacks/                # per-stack package.json + extras
│   └── configs/               # supabase, prisma, aws helpers
├── CLAUDE.md                  # Claude Code project context
└── README.md

Adding a new stack

  1. Create templates/stacks/<name>/package.json with the right dependencies.
  2. Add any config helpers under templates/configs/<name>/.
  3. Add a case to scripts/setup.sh's STACK_OPTIONS array and the copy_template switch block.

Adding a new skill

  1. Create .claude/skills/<skill-name>.md describing the steps.
  2. Add a row to ai-rules/claude/README.md.