add-dependency

Adds npm packages to a Yarn 4 project via yarn add and verifies package.json.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill add-dependency-plazacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-dependency
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/add-dependency
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill add-dependency-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure correct usage of Yarn 4 when adding new dependencies, preventing drift in tooling and keeping docs up to date.

Core Features & Use Cases

  • Automatically add a new dependency to the project using yarn add, ensuring the correct package manager is used.
  • Verify the dependency appears in package.json and optionally install TypeScript types when needed.
  • Update project documentation or setup notes when a core stack change occurs.

Quick Start

Install a package by running the command with the package name argument.

Frequently Asked Questions about add-dependency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new npm package to a Yarn 4 project?

To add an npm package to a Yarn 4 project, use the yarn add command with the package name. This ensures the correct package manager is used and updates package.json with the new dependency automatically.

Can I install TypeScript type declarations when adding a dependency with Yarn 4?

Yes, you can install TypeScript type declarations when adding a dependency. The process identifies and installs the necessary type packages alongside the core library to maintain proper type safety.

What is the best way to manage dev dependencies in a Yarn 4 workflow?

The best way to manage dev dependencies in a Yarn 4 workflow is using the yarn add command configured for development packages. This correctly categorizes testing or build tools separately from production libraries in package.json.

Does adding a core library with Yarn 4 require documentation updates?

Adding a core library with Yarn 4 suggests documentation updates when needed. If the new package represents a core stack change, the workflow prompts you to update project documentation or setup notes to prevent tooling drift.

Why should I verify package.json after running yarn add?

You should verify package.json after running yarn add to confirm the package was successfully registered. This validation step ensures the dependency appears correctly before you start importing it into your application code.