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/templates

v0.2.0

Published

Built-in asset templates (YAML) for RepoChan image pipeline — prompt skeletons, sizes, grids, constraints.

Readme

@repochan/templates

Built-in asset templates for the RepoChan image pipeline: small YAML files with prompt_template, canvas size, optional grid, and post-process constraints.

This is a pure data package. It does not contain code, skills, or agent instructions.

Why a separate package?

| Concern | Owner | |---|---| | How to pick / fill templates | Skills (@repochan/skill) — teach the agent | | Load / list / get templates | CLI (repochan template list\|get) | | Template file contents | This package | | Protocol state (templateId string) | Core |

Skills must not ship runtime data the CLI parses. Agents consume templates only through the CLI.

Layout

YAML files live at the package root (one file per template). Example ids: official/foundation-sheet, official/poster-memphis.

Grid templates may declare grid.cell_keys in row-major order when every cell has a stable semantic meaning. For example, official/web-state-grid-3x3 defines nine web-state asset keys; starter validation matches them against manifest publications[], and starter asset-apply projects a delivered sheet into named files atomically.

Resolution order (CLI)

  1. Built-ins from this package (@repochan/templates)
  2. Project overlay: <projectRoot>/.repochan/templates/ (same id wins)

Usage

repochan template list
repochan template list --tag poster
repochan template get official/foundation-sheet

Scale roadmap

| Stage | Strategy | |---|---| | Now (~12 official) | Ship with CLI via this data package; semver-locked | | Dozens + community | Keep official set here; add remote registry / git pull later | | Hundreds+ | CLI becomes a pure client; remote hub is the source of truth |

Page/Astro project scaffolds are a different kind of template and are not stored here.