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

@bedframe/skills

v0.1.0

Published

Agent Skills for Bedframe — Browser Extension Development Framework

Readme

@bedframe/skills

@bedframe/skills is the Bedframe skill library for agent-assisted extension development.

It provides the portable markdown contracts that help coding agents understand how a Bedframe project is structured, how Bedframe workflows operate, and how to work safely with cross-browser extension codebases.

These skills are designed to work with:

  • a project-level AGENTS.md
  • nearest-folder AGENTS.md files
  • Bedframe-generated project structure
  • @bedframe/cli
  • @bedframe/core
  • the default .github/workflows/mvp.yml release flow

What developers get

Bedframe projects can install selected skills into:

<bedframe-project>/.agents/skills/*

That gives an agent a project-local set of workflow guides for common Bedframe tasks such as:

  • understanding the Bedframe B.E.D. model
  • editing bedframe.config.ts
  • adding browser targets
  • adding pages
  • building, zipping, versioning, and publishing
  • following the Bedframe M.V.P. release contract

The intended outcome is not prompt-heavy hand-holding. The goal is to let a developer use their agent of choice with a clear Bedframe-native contract already present in the repo.

How it fits into a project

The Bedframe agent contract is split across a few layers:

  • root AGENTS.md
    • introduces Bedframe, B.E.D., M.V.P., project architecture, and high-level guardrails
  • nearest-folder AGENTS.md
    • localizes rules for folders such as src/_config, src/manifests, src/pages, and src/scripts
  • .agents/skills/*
    • gives workflow-specific instructions for tasks like config, build, version, and publish

Together these files help an agent navigate both:

  • Bedframe architecture and conventions
  • the specific local project shape generated during scaffold

Package contents

  • AGENTS.md
    • source template for the generated root project AGENTS.md
  • bedframe/references/nested-agents/*
    • nearest-folder AGENTS.md templates for generated projects
  • bedframe/*
    • Bedframe skill content published at package root under the bedframe skill
  • bedframe/references/template/SKILL.md
    • base skill template for future Bedframe skill additions

Current skill

  • bedframe

The umbrella bedframe skill is the intended project install. It routes to focused reference docs instead of requiring a separate skill folder for each CLI command.

Skill design

Each skill keeps the main SKILL.md short and puts longer task detail in references/REFERENCE.md.

That lets an agent:

  1. discover the skill from its metadata
  2. load the short working instructions in SKILL.md
  3. load the reference file only when more detail is needed

This follows the same general pattern used by portable markdown-first skill systems: keep the top-level contract concise, then load deeper reference material only when the task actually needs it.

Example installed shape

After scaffold or manual install, a project can look like:

AGENTS.md
.agents/
  skills/
    bedframe/
      SKILL.md
      references/
        REFERENCE.md

Use AGENTS.md in this package as the source template for that generated file.

Generated projects can also include nearest-folder contracts such as:

src/_config/AGENTS.md
src/manifests/AGENTS.md
src/pages/AGENTS.md
src/scripts/AGENTS.md
src/__tests__/AGENTS.md

Typical use

Use @bedframe/skills when you want a Bedframe project to carry its own agent-facing conventions instead of depending on a specific app or harness to explain them at runtime.

That is useful for:

  • Claude, Codex, Cursor, Gemini, and similar coding agents
  • Teams that want portable repo-local instructions
  • Bedframe projects that need consistent config, manifest, page, script, and release behavior

Release workflow

Bedframe skills assume the standard Bedframe release path:

  • make
  • version
  • publish

In a standard project, .github/workflows/mvp.yml is the main CI/CD contract and direct bedframe publish --browsers ... is the manual equivalent of the publish phase.