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

farmwork

v1.5.1

Published

Farmwork - A workflow framework for Claude Code by Wynter Jones

Readme

A workflow framework for Claude Code by Wynter Jones

Quick Start

npm install -g farmwork
cd your-project
farmwork init
farmwork doctor
farmwork status

Or run directly with npx:

npx farmwork init

The Farmwork Method

Core Concepts

  1. Skills - Auto-activating workflows that respond to natural phrases
  2. Slash Commands - Explicit triggers for actions like /push
  3. Agents - 15 specialized AI subagents for specific tasks
  4. Supplies - Built-in tools and MCP integrations to extend your farm
  5. Issue Tracking - Using beads (bd) for full visibility
  6. Living Audits - Documents that track ongoing concerns
  7. Plan & Implement - You describe the outcome, the rest is handled
  8. Idea Garden - Pre-plan creative stage with natural aging

Skills (Auto-Activating Workflows)

Skills auto-activate when you use these natural phrases:

| Phrase | Skill | What Happens | |--------|-------|--------------| | open the farm | farm-audit | Audit systems, update FARMHOUSE.md | | count the herd | farm-inspect | Full code inspection (no push) | | go to market | market | i18n + WCAG accessibility audit | | go to production | production | Update BROWNFIELD, strategy check | | I have an idea for... | garden | Plant idea in GARDEN.md | | water the garden | garden | Generate 10 new ideas | | compost this... | garden | Move idea to COMPOST.md | | let's research... | research | Create/update _RESEARCH/ doc |

Slash Commands (Explicit Actions)

| Command | Description | |---------|-------------| | /push | Lint, test, build, commit, push (11 steps) | | /office | Interactive strategy setup |

Skill Activation Hook

Farmwork adds a UserPromptSubmit hook that reminds Claude to check for applicable skills. This improves activation reliability over phrase commands in CLAUDE.md.

Agents

15 specialized agents included:

| Agent | Purpose | |-------|---------| | the-farmer | Audit and update FARMHOUSE.md metrics | | code-reviewer | Quality & security code review | | security-auditor | OWASP vulnerability scanning | | performance-auditor | Memory leaks, re-renders, anti-patterns | | code-smell-auditor | DRY violations, complexity, naming | | accessibility-auditor | WCAG 2.1 compliance, alt text, contrast | | unused-code-cleaner | Detect and remove dead code | | code-cleaner | Remove comments and console.logs | | i18n-locale-translator | Translate UI text to locales | | storybook-maintainer | Create/update Storybook stories | | idea-gardener | Manage Idea Garden and Compost | | researcher | Systematic research before planning | | strategy-agent | Core loop strategy (what/stopping/why) | | onboarding-agent | Tours, tooltips, modals, empty states | | user-guide-agent | Feature documentation for help docs |

Supplies

Supplies are optional tools and MCP integrations that extend your farm's capabilities. Add them during farmwork init or anytime with farmwork supply.

Built-in Supplies

| Supply | Purpose | |--------|---------| | just | Command runner for project tasks | | beads | Local, markdown-based issue tracking | | knip | Dead code detection (unused files, deps, exports) |

MCP Supplies

| Supply | Purpose | Requires | |--------|---------|----------| | storybook | Connect Claude to your component library | Storybook installed | | context7 | Up-to-date library documentation | None | | sentry | Error tracking and monitoring | SENTRY_AUTH_TOKEN | | images | AI image generation (Gemini/OpenAI) | API keys |

Recommended Workflow

  1. Start Session: Run open the farm to audit current state
  2. Capture Ideas: Use I have an idea for... to plant ideas in GARDEN
  3. Research: Use let's research... to gather information before planning
  4. Plan Work: Use make a plan for... for new features
  5. Implement: Use let's implement... to execute with tracking
  6. Quality Check: Run count the herd for full audit + dry run
  7. Ship: Run close the farm or /push to push changes

You can go to market when you have a production-ready app with international users.

Directory Structure

your-project/
├── CLAUDE.md           # Lean instructions (references skills)
├── .claude/            # Claude Code configuration
│   ├── skills/         # Auto-activating workflows (NEW!)
│   │   ├── farm-audit/     # "open the farm"
│   │   ├── farm-inspect/   # "count the herd"
│   │   ├── garden/         # idea management
│   │   ├── research/       # "let's research..."
│   │   ├── production/     # "go to production"
│   │   └── market/         # "go to market"
│   ├── agents/         # 15 specialized subagents
│   │   ├── the-farmer.md
│   │   ├── code-reviewer.md
│   │   ├── security-auditor.md
│   │   └── ... (12 more)
│   └── commands/       # Explicit slash commands
│       ├── push.md
│       └── office.md
├── _AUDIT/             # Living audit documents
│   ├── FARMHOUSE.md    # Framework command center
│   ├── GARDEN.md       # Idea nursery
│   ├── COMPOST.md      # Rejected ideas
│   ├── KNIP.md         # Dead code report (if enabled)
│   └── ... (security, performance, etc.)
├── _OFFICE/            # Product strategy
│   ├── GREENFIELD.md   # Vision
│   ├── BROWNFIELD.md   # Reality
│   └── ... (onboarding, user guide)
├── _PLANS/             # Implementation plans
├── _RESEARCH/          # Research documents
├── .beads/             # Issue tracking
└── justfile            # Navigation commands

Commands

farmwork init

Start setting up the new digital farm:

farmwork init                    # Interactive setup wizard

Options:

  • -f, --force - Overwrite existing files

Optional Features: During init, you'll be asked about optional features:

  • i18n - Internationalization support
  • Storybook - Component documentation (React/Vue projects)
  • Knip - Dead code detection (runs during farm-inspect)
  • Supplies - MCP integrations (Storybook, Context7, Sentry, Images)

Creates:

  • CLAUDE.md - Lean instructions (references skills)
  • .claude/ - Claude Code configuration directory
    • skills/ - 6 auto-activating workflows (farm-audit, farm-inspect, garden, research, production, market)
    • agents/ - 15 specialized subagents
    • commands/ - 2 slash commands (/push, /office)
    • settings.local.json - Skill activation hook
  • _AUDIT/ - Living audit documents
    • FARMHOUSE.md, GARDEN.md, COMPOST.md, and more
  • _OFFICE/ - Product strategy documents
    • GREENFIELD.md, BROWNFIELD.md, ONBOARDING.md, USER_GUIDE.md
  • _PLANS/ - Implementation plans directory
  • _RESEARCH/ - Research documents directory
  • justfile - Navigation and task commands

farmwork status

Display Farmwork status and metrics.

farmwork status

Shows:

  • Component counts (agents, commands, audits, plans)
  • Office documents status
  • Issue tracking status (if beads is configured)
  • FARMHOUSE score and open items
  • Configuration file status
  • Project metrics (tests, stories)

farmwork doctor

Check your Farmwork setup and diagnose issues.

farmwork doctor

Checks:

  • Core files (CLAUDE.md, .claude/, settings)
  • Agents and commands configuration
  • Audit system (_AUDIT/, FARMHOUSE.md, _PLANS/)
  • Research system (_RESEARCH/)
  • Office system (_OFFICE/, CORE_LOOP.md, ONBOARDING.md, USER_GUIDE.md)
  • Navigation (justfile, just command)
  • Issue tracking (beads)
  • Security (.gitignore settings)

farmwork supply

Add supplies to your farm - tools and MCP integrations.

farmwork supply              # Interactive supply selection
farmwork supply images       # Install specific supply

Available Supplies:

  • storybook - Storybook MCP server + skill
  • context7 - Context7 MCP for library documentation
  • sentry - Sentry error tracking MCP
  • images - AI image generation (Gemini/OpenAI)

What It Does:

  1. Installs the MCP server via claude mcp add
  2. Creates a corresponding skill in .claude/skills/
  3. Configures any required API keys

Requirements

  • Node.js 18+
  • just (recommended for navigation)
  • beads (for issue tracking)
  • knip (optional, for dead code detection)

License

MIT

Links