setup

Decompose project ideas into modular-dev package graphs with contracts and workspace files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a broad project idea into a structured modular-dev workspace so large builds can be planned, isolated, and developed without overwhelming a single context.

Core Features & Use Cases

  • Project Decomposition: Splits an idea into independent package nodes, contracts, shared modules, and zones.
  • Workspace Initialization: Creates the expected directory skeleton, graph metadata, overview files, and CLAUDE.md guidance.
  • Workflow Setup: Prepares a project for contract-first development, isolated package work, and wave-based execution.
  • Use Case: Start a new product or refactor an existing codebase into smaller units that can be built safely in parallel.

Quick Start

Use the setup skill to decompose my project idea and create the modular-dev directory structure.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I decompose a project idea into a modular workspace structure?

Decomposing a project idea into a modular workspace involves splitting it into independent package nodes, contracts, and zones. This process generates a directory skeleton, graph.json metadata, and CLAUDE.md guidance to enable contract-first development and isolated package work.

What is the best way to set up a modular-dev package graph for a new project?

Setting up a modular-dev package graph requires decomposing your idea into isolated nodes and shared modules. This creates a workspace foundation with locked contracts and overview files, allowing large builds to be planned and developed in parallel without overwhelming a single context.

Can I use this modular project setup approach to restructure an existing codebase?

Yes, this modular project setup approach applies to restructuring existing codebases. It breaks down monolithic code into smaller, independent units by generating a package graph, directory skeleton, and locked contracts, ensuring safe parallel development and wave-based execution.

How does contract-first development workspace initialization work?

Contract-first development workspace initialization works by generating a structured directory skeleton alongside graph.json and locked contracts. This defines strict boundaries between package nodes upfront, enabling isolated module work and preventing dependency conflicts during large builds.

Do I need any dependencies to initialize a modular-dev directory skeleton?

No dependencies are required to initialize a modular-dev directory skeleton. The setup process independently generates the workspace files, graph metadata, and CLAUDE.md guidance from your project idea, preparing the foundation for contract-first development without external tools.

Why does my project decomposition need zones and overview files?

Project decomposition needs zones and overview files to organize independent package nodes and shared modules logically. This structure prevents context overload by isolating development work into manageable units, enabling safe parallel execution and clear contract boundaries across the workspace.