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

create-allthing

v0.5.0

Published

CLI to scaffold full-stack projects with Docker and AI-agent-ready structure

Readme

create-allthing

CLI to scaffold full-stack projects with a standardized structure, Docker included, and AI-agent ready.

npx create-allthing

Features

  • Interactive prompt-guided scaffolding
  • Main menu: Create project or Skills Stack management
  • Multi-stage Docker builds optimized per technology
  • Healthchecks configured in Dockerfile and docker-compose
  • Network isolation: frontend-net / backend-net
  • Environment variables properly injected at build time
  • Nginx with SPA routing (try_files) ready for client-side routing
  • Predictable structure designed for AI agents (Claude Code, Cursor, Codex)
  • Configurable Claude Code skill stacks with global persistence
  • Jenkinsfile generation with multi-environment pipeline (dev → staging → prod)
  • Git repo initialized with initial commit
  • Apply skills to existing projects via create-allthing skills

Available Stacks

| Layer | Options | |---|---| | Frontend | React (Vite) · Angular | | Backend | Python + FastAPI · .NET WebAPI | | Database | PostgreSQL · MongoDB · None | | CI/CD | Jenkinsfile (optional) |


Usage

npx create-allthing

The CLI shows a main menu:

  1. Create project — the full scaffolding wizard
  2. Skills Stack — manage your AI skill stack (persisted globally)

Create Project Flow

  1. Project name — used as folder name and workspace
  2. Frontend — React (Vite) or Angular
  3. Backend — Python + FastAPI or .NET WebAPI
  4. Database — PostgreSQL, MongoDB, or None
  5. Jenkinsfile — generate CI/CD pipeline (yes/no)
  6. Confirmation — summary before creating anything

Once confirmed, the CLI:

  • Creates the folder structure
  • Runs npm create vite / ng new / uv init / dotnet new webapi as needed
  • Generates docker-compose.yml, .env.example, .gitignore, README.md, .code-workspace
  • Generates Jenkinsfile (if selected) with dev → staging → prod pipeline
  • Installs Claude Code skills from your saved stack
  • Runs git init with initial commit

Skills Stack Management

Select Skills Stack from the main menu to:

  • Find and add skill — uses npx skills with find-skills to browse available skills
  • Remove skill — select skills to remove from your stack
  • Restore defaults — reset to the 10 default skills
  • Save and return — persist to ~/.create-allthing/skills-stack.json

Apply Skills to Existing Project

create-allthing skills          # interactive — detects duplicates, asks what to do
create-allthing skills -l       # list your current skill stack
create-allthing skills --stack-info  # show skills installed in current project

Generated Structure

my-project/
├── frontend/            # React (Vite) or Angular
│   ├── src/
│   ├── Dockerfile
│   ├── nginx.conf
│   └── .dockerignore
├── backend/             # FastAPI or .NET WebAPI
│   ├── src/
│   ├── Dockerfile
│   └── .dockerignore
├── infra/
│   ├── scripts/
│   └── db/
│       ├── migrations/
│       └── seeds/
├── mcp/
├── docs/
│   ├── specs/
│   └── agents.md
├── .claude/
│   ├── skills/
│   └── skills-lock.json
├── docker-compose.yml
├── Jenkinsfile          # if selected
├── .env.example
├── .env
├── .gitignore
├── my-project.code-workspace
└── README.md

Quick Start (generated project)

cp .env.example .env
# edit .env with your values
docker compose up --build

| Service | URL | |---|---| | Frontend | http://localhost:3000 | | Backend | http://localhost:8080 |


Adding New Stack Options

The CLI uses a registry pattern — to add a new backend, frontend, or database:

  1. Create the template folder in templates/backend/<id>/ (or frontend/<id>/)
  2. Add the entry to the corresponding registry in src/registry/
  3. Create a runner in src/runners/<id>.js if it needs specific setup logic

Prompts, scaffold, and generators read from the registry automatically.

Example: adding Express as a backend

// src/registry/backends.js
export const backends = [
  // ... existing ...
  {
    id: 'express',
    label: 'Node.js + Express',
    dirs: ['src/routes', 'src/services', 'src/models', 'src/middleware', 'tests'],
    healthcheck: {
      compose: "['CMD', 'curl', '-sf', 'http://localhost:8080/health']",
    },
    readmeTest: 'cd backend && npm test',
  }
]
templates/backend/express/
├── Dockerfile
├── src/
│   └── index.js
└── .dockerignore

Requirements

  • Node.js >= 18
  • npm (for React/Vite and Angular frontends)
  • uv (for FastAPI — auto-installed if missing)
  • .NET SDK 8 (for .NET WebAPI)
  • Docker (to run the generated project)
  • Git (for the initial commit)

All runners degrade gracefully: if a tool is unavailable, they create the folder structure manually and show the installation command.


Local Development

git clone https://github.com/Alberto02003/create-allthing
cd create-allthing
npm install
node bin/create-allthing.js

To test without publishing:

npm link
create-allthing

License

MIT