add-node

Create a new node in a modular-dev project and update graph.json.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Arrosam/Modular-Dev --skill add-node-arrosam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-node
Source: https://github.com/Arrosam/Modular-Dev/tree/main/skills/add-node
Command: npx skills add https://github.com/Arrosam/Modular-Dev --skill add-node-arrosam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of a new node in an existing modular-dev project by turning a manual setup process into a guided workflow.

Core Features & Use Cases

  • Node setup: Creates the package directory and placeholder files needed for a new component.
  • Graph registration: Updates graph.json so the new node is tracked correctly in the project structure.
  • Contract onboarding: Adds new contracts and placeholder tests when the node needs fresh interfaces.
  • Zone re-partitioning: Recomputes zone placement so the new node fits the current dependency map.
  • Use case: Use this when you need to introduce a new service, feature module, or package into a modular-dev repository without breaking the project’s organization.

Quick Start

Use the add-node skill to help me add a new node for my feature, update the project graph, create any required contracts, and re-partition the affected zones.

Frequently Asked Questions about add-node

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

FAQPage Schema
How do I add a new module to a modular-dev project without breaking existing contracts?

To add a new module, you create the package directory and update overview metadata so the node connects to existing contracts. This guided workflow ensures the new component integrates smoothly without disrupting project organization.

What is the best way to register a new package in graph.json?

Registering a new package in graph.json involves updating the project structure file to track the new node correctly. This ensures the modular-dev architecture recognizes the new component and maintains an accurate dependency map.

How does zone partitioning work when introducing a new feature module?

Zone partitioning recomputes dependency placement when a new feature module is introduced. This ensures the new node fits the current dependency map and maintains the architectural boundaries of the modular-dev project.

Do I need to manually create placeholder tests when onboarding new contracts?

No, new contracts and placeholder tests are generated automatically during the node setup process. This contract onboarding step creates the required interfaces so the new package integrates with the existing modular-dev structure.

Can I use this guided workflow to set up a new service in an existing modular repository?

Yes, this workflow is designed for introducing a new service, feature module, or package into a modular-dev repository. It transforms the manual setup process into a guided workflow that preserves project organization.

What files need to be updated when adding a node to a modular-dev architecture?

Adding a node requires updating the package directory, overview metadata, graph.json, optional contract definitions, and zone partitioning. This comprehensive update ensures the scoped commit path and project structure remain intact.