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

@hiromima/design-loom

v0.1.0

Published

Harness-neutral, agent-drivable design-generation pipeline. Drive from any agent (Claude Code, Codex, CI) with pure bash.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

hiromimahiromima

Keywords

designpipelineagentbashcodexclaudestate-machine

Readme

design-loom

Harness-neutral, agent-drivable design-generation pipeline. A small bash state machine that runs a design pipeline (clarify → generate → structure → score → bundle) and can be driven from any agent — Claude Code, Codex, or a CI job — because the orchestration is pure bash + python3 + jq with no tool/MCP dependency.

npx @hiromima/design-loom run myproj 5dim.json

Why

Most "AI design pipeline" tooling is welded to one harness (a specific tool/skill API). design-loom separates orchestration (a portable state machine) from phase execution (swappable). The state machine emits a JSON contract per step; your agent decides how to run each phase. Same pipeline, any harness.

Install

npm i -g @hiromima/design-loom    # or: npx @hiromima/design-loom <cmd>

Requires bash, python3, jq. The quality gate (score) additionally uses the gemini CLI for vision scoring and a screenshot backend (browser-use or headless Chrome) — both optional; without them, score degrades to a neutral default.

Quickstart

# 1. Describe the job (5 dimensions)
cat > 5dim.json <<'JSON'
{"output":"HTML","fidelity":"hi-fi","option_count":1,"constraints":[],"ds_uik_brands":[]}
JSON

# 2. Initialize
design-loom run myproj 5dim.json

# 3. Drive the loop: get next phase -> run it -> mark complete
while true; do
  R=$(design-loom next myproj)
  S=$(echo "$R" | python3 -c 'import json,sys;print(json.load(sys.stdin).get("status",""))')
  [ "$S" = "all_completed" ] && break
  PH=$(echo "$R" | python3 -c 'import json,sys;print(json.load(sys.stdin).get("phase",""))')
  # Run the phase per phases/<name>/PHASE.md, write outputs.json, then:
  design-loom complete myproj "$PH" completed outputs.json
done

# 4. Inspect
design-loom status myproj

Commands

| Command | Purpose | | --- | --- | | design-loom run <project> <5dim.json> | Initialize plan + state | | design-loom next <project> | Get the next phase as JSON ({phase, skill, args, expected_output, hint}) | | design-loom complete <project> <phase> <status> [outputs.json] | Mark a phase done (completed/failed/skipped/pending) | | design-loom status <project> | Progress table | | design-loom score <html> | Visual quality gate — normalized JSON ({score, axes, slop_flags, violations}) |

Bring your own phases

The bundled phases/{clarify,generate,structure,bundle}/PHASE.md are minimal reference phases. The only coupling point is the JSON contract — see phases/PHASE_CONTRACT.md. Swap in your own phases freely.

Quality gate

design-loom score <html> renders the HTML, scores it on 5 axes (visual hierarchy, consistency, spacing, typography, color harmony, 0–10), and flags AI-slop tropes and font/size violations. The vision API key is read from the environment only (GEMINI_API_KEY) — never hardcode it.

License

MIT — see LICENSE.