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

@houserules/plugin-typescript

v0.1.2

Published

houserules plugin: a path-scoped TypeScript rule covering the type-system decisions that have a right answer.

Downloads

553

Readme

@houserules/plugin-typescript

npm

An agent writing TypeScript reaches for any the moment data arrives from outside the program, and picks between interface and type by whichever it saw last. Neither choice fails a build, so neither gets caught in review until the codebase has both conventions and no reason for either.

This plugin ships the small set of type-system decisions that have a right answer, as a rule the agent loads only when it has a TypeScript file open.

Install

pnpm add -D @houserules/plugin-typescript
pnpm exec houserules init

Requires @houserules/cli. init is what writes the module into .claude/. This module is off by default, so select it when init asks.

Modules

  • typescript installs .claude/rules/typescript.md, a path-scoped rule covering three decisions. interface for object shapes, because they extend. type for unions and computed types. unknown plus a type guard instead of any for untyped external data.

    Scoped to **/*.ts, **/*.mts, **/*.cts, and **/*.tsx through its paths: frontmatter, plus **/*.svelte and **/*.svelte.ts so svelte.md can defer to it. Claude Code loads it only when a matching file is in the working set, so it costs nothing on the always-loaded surface. Keep that frontmatter. A rule file without paths: is loaded on every turn.

    The rule assumes strict: true.

What it leaves alone

Doc comments and verification commands are out of scope on purpose.

Doc comments belong to code-comments.md in @houserules/plugin-prose, which covers TSDoc form in more depth than a per-language rule should restate. Running pnpm check and pnpm test belongs to the CLAUDE.md managed region, which says it once per turn rather than once per language rule that happens to load.

A rule that repeats something houserules already says costs resident budget every time it loads to say it again. This one says only what is specific to TypeScript's type system.

Part of houserules

houserules is a portable set of Claude Code infrastructure that keeps the agent's context lean. This is one of twelve first-party plugins. The package list has the rest.

License

MIT. See LICENSE.