Enforce npm package conventions for JavaScript ES module projects.
npx skills add https://github.com/sanand0/scripts --skill npm-packages
Please help me install this Agent Skill. Skill: npm-packages Source: https://github.com/sanand0/scripts/tree/main/agents/npm-packages Command: npx skills add https://github.com/sanand0/scripts --skill npm-packages
This Skill provides a comprehensive guide for structuring, coding, and publishing npm packages, ensuring consistency, maintainability, and ease of use across projects. It streamlines the package development lifecycle from creation to deployment.
package.json Conventions: Defines mandatory and recommended fields for package.json, including scripts for linting, building, and testing (prepublishOnly).README.md Structure: Outlines a standardized README.md format with essential sections like shields, installation, usage, and development, improving discoverability and user adoption.package.json and README.md for a new JavaScript utility, pre-filling all standard fields and build scripts according to best practices, saving hours of setup time.Create a package.json and README.md for a new npm package named 'my-utility', including build and test scripts.
High-intent search queries and answers about installing and using this skill.
A package.json for npm publishing requires mandatory fields: name, version, description, homepage, repository, license, type (set to 'module' for ESM), files, and exports. Include scripts for build, lint, test, and prepublishOnly to automate quality checks before publishing.
A professional README includes shields for badges, installation instructions, usage examples, development setup, and contribution guidelines. This structure improves discoverability, helps users understand your package quickly, and establishes trust through clear documentation.
Yes, enforce standards by defining scripts for linting and testing in package.json, using ESM with named exports, avoiding TypeScript in core files while providing type definitions, and standardizing build workflows. This ensures consistency across projects and simplifies maintenance.
Use ES modules (ESM) with named exports, provide type definitions alongside JavaScript code, standardize test frameworks like Vitest and Playwright, and follow consistent naming conventions. These practices improve compatibility, developer experience, and code quality for consumers.
Yes, configuring prepublishOnly, test, and lint scripts in package.json ensures code quality gates run automatically before publishing. This prevents defects from reaching consumers and establishes a reliable release process.
Define the files field in package.json to explicitly list distributable assets: built output, type definitions, and README. Use exports to map entry points for different module consumers. This reduces package size and clarifies which files are public API.
tomzxGenerate a ready-to-commit README.md from project metadata using a fixed Markdown template.
sgcarstrendsAutomate software release workflows with semantic-release and conventional commits.
harrytran998Run JavaScript and TypeScript applications with integrated package management, bundling, and testing.
shanieMoonlightLink workspace packages in monorepos using npm, yarn, pnpm, or bun.