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

@repochan/starters

v0.1.0

Published

Built-in landing-page starters (full Astro/Tailwind project scaffolds) for RepoChan.

Readme

@repochan/starters

Complete, real project websites that can be localized for another repository. Each child directory is an independent Astro/Tailwind site copied by repochan starter pull; the package has no runtime exports or build logic.

Source Starter and Transfer Kit

A Source Starter preserves its original project name, character, URLs, copy, source code, and production assets. It is a finished website, not an anonymous wireframe. Its previews and running source are the authoritative expression of the design.

The Transfer Kit is the small, concentrated handoff surface inside that full site:

<starter-id>/
├── repochan/
│   ├── starter.json              # sole manifest: previews, locales, slots, orders, postprocess
│   ├── site.json                 # project metadata and theme tokens
│   ├── assets.json               # source/customized asset state
│   ├── i18n/{locale}.json        # complete content structures
│   └── previews/{desktop,mobile}.png
├── public/                       # full source assets plus optional low-information slot references
├── src/                          # complete implemented site
└── package.json

The Transfer Kit is not a second package or manifest. It lets the Page Designer replace deterministic configuration, complete locale values, and declared asset slots without reconstructing the design or copying fields by hand.

Core owns the manifest and config schemas. The CLI owns discovery, projection, order materialization, deterministic post-processing, local-source pull, and validation.

Asset contract

Each slot is either:

  • scalar: one output;
  • bundle: named publications[] plus one exclusive extract-grid postprocess.

repochan/assets.json mirrors the discriminant. source means the original finished Starter asset is present and buildable. customized means the pulled instance has replaced it for the target project. Source validation accepts the preserved original; starter validate --localized requires every required slot to be customized.

For a complex baked composition, the original full asset remains in the Starter. A slot may additionally reference a low-information migration guide, such as a pose line drawing produced by official/hero-pose-lineart-extract. The guide preserves composition and safe zones while reducing character or background identity; it never replaces the original artwork.

All supported locale files must have the same complete recursive shape as the default locale, including keys, value types, and array lengths. Presentation colors live only in repochan/site.json; source files consume derived CSS variables.

Commands

repochan starter list
repochan starter get minimal --json
repochan starter pull --starter minimal
repochan starter pull --from /path/to/creator-starter
repochan starter configure [--content-file content.json --overwrite]
repochan starter create-order hero-composite --intent "..." --foundation ord-foundation-001
repochan starter asset-apply hero-composite --order ord-hero-001 --overwrite
repochan starter validate minimal
repochan starter validate --output-dir .repochan/web-starter --localized
repochan starter validate --all

Contributing a Starter

Starter Designer works in a creator-owned directory or repository. Official inclusion happens through a pull request containing the complete Source Starter, desktop/mobile previews, and validation/build evidence. The official package is not a direct output directory for the skill.

Available starters

| ID | Original project site | Default | |---|---|---| | caddy | Caddy architectural automatic-HTTPS landing page | no | | marktext | MarkText midnight Art Deco editorial landing page | no | | minimal | RepoChan single-screen editorial Hero | yes | | redis | Redis kinetic real-time signal-relay landing page | no |