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

@avant-garde/design-loop

v0.1.0

Published

Design-code deep agent: render → see → refine Shopify theme implementation, with the Design Work Contract for orchestrator delegation

Readme

@avant-garde/design-loop

The design-code deep agent for Marketing OS: the render → see → refine engine for on-brand, conversion-driven Shopify theme implementation, plus the Design Work Contract that lets a general-purpose planner (Claude Code in the GH runner) delegate implementation to it.

Plan & rationale: docs/plans/brand-conversion-design-agent/.

What's here

  • The contract (./contract) — TaskSpec / ProgressEvent / WorkReport / RevisionSpec zod schemas. Parent-agnostic; the same shapes back the MCP server and the CLI.
  • The deep agent (runDesignAgent) — decomposes a TaskSpec into per-page/section sub-tasks, runs the bounded refine loop for each, and merges the results into one WorkReport.
  • The refine loop (runRefineLoop) — propose → implement → render → capture → conform → refine, capped at N iterations (default 4), escalate-with-best on the cap, rejected on a guardrail/asset-boundary refusal.
  • Deterministic gates — dark-pattern blocklist (output-processor), WCAG accessibility floor, token fidelity. Rule-based, never routed through a model.
  • Delegation surfaceDelegationService (in-process registry, async + progress), an MCP server (pnpm mcp), and a CLI (design-code-agent run).

Architecture: logic vs. I/O

All logic (contract, loop, deep agent, gates, conformance merge, delegation) is fully typed and tested with injectable providers — no browser, no model, no Shopify needed. The I/O adapters (Playwright capture, shopify theme dev, a VLM critic endpoint, pixelmatch diff, the MCP transport) are thin, lazy-loaded glue in src/adapters/ (marked @ts-nocheck) and declared as optional dependencies, so the package builds and tests run with zero heavy deps installed.

TaskSpec ─▶ DelegationService ─▶ runDesignAgent ─▶ runRefineLoop ─▶ WorkReport
                                       │                 │
                                       └─ decompose      ├─ Implementer  (stub | LLM)
                                                         ├─ CaptureProvider (stub | Playwright)
                                                         ├─ CriticProvider  (stub | VLM)  ┐
                                                         └─ gates (deterministic) ────────┴─▶ ConformanceResult

ConformanceResult matches the Design MCP validate_design_conformance return shape, so the local merge can be swapped for the hosted MCP call (set DESIGN_MCP_ENDPOINT) without changing callers.

Run

pnpm --filter @avant-garde/design-loop build
pnpm --filter @avant-garde/design-loop test

# CLI (stub providers — no external deps):
node dist/delegation/cli.js run --task task.json --report report.json --stub

# MCP server (needs @modelcontextprotocol/sdk; what the GH-runner planner connects to):
pnpm --filter @avant-garde/design-loop mcp

A live run (DESIGN_LOOP_REAL=1 + a configured critic endpoint + shopify theme dev) uses the real adapters; otherwise the stub providers run deterministically.