find-npm-packages
Identify, validate, and add npm package references to a Front-End Checklist rule.
What this skill does
Given a rule file or rule slug, this skill will:
- Understand what the rule is checking for
- Research which npm packages are commonly used to implement, automate, or enforce the rule
- Validate each candidate against quality thresholds (popularity + maintenance)
- Select the best 2–3 packages
- Add them to the rule's
npmPackagesfrontmatter field
Quality thresholds (mandatory — do not skip)
Before selecting any package, check it against these criteria using the npm registry:
| Criterion | Minimum |
|---|---|
| Weekly downloads | >10,000/week |
| Last publish | Within 18 months |
| npm registry | Must be listed (registry.npmjs.org/{name}) |
Packages that fail any threshold must be excluded, regardless of how relevant they are.
Research steps
Step 1 — Understand the rule
Read the rule file: packages/content/rules/en/{category}/{slug}.mdx
Focus on:
- What problem does this rule solve?
- What technique, spec, or behavior does it enforce?
- What tools or linters are mentioned in the
tools:field?