start-project

Starts the current MOM instance using the repository-local PowerShell operations script.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/SSS08099/mom-system --skill start-project-sss08099
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-project
Source: https://github.com/SSS08099/mom-system/tree/main/.agents/skills/start-project
Command: npx skills add https://github.com/SSS08099/mom-system --skill start-project-sss08099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a local MOM development instance involves coordinating environment files, builds, frontend, infrastructure, and process management, and doing it manually risks using the wrong checkout, ports, or containers. This Skill enforces a safe, repository-scoped startup procedure. ## Core Features & Use Cases - Repository-scoped startup: Resolves the current repository root with git and runs only that checkout's start-project.ps1 script. - Environment validation: Blocks startup when the root .env.local file is missing or invalid, preventing cross-checkout configuration leaks. - Status reporting: Runs status-project.ps1 to report the instance ID, managed PIDs, and configured ports after startup. - Use Case: A developer with multiple MOM checkouts wants to start the instance for the branch they are currently working on without touching legacy global Docker containers or killing unrelated Java or Node processes. ## Quick Start Start the current MOM instance for this repository and report its instance ID, managed PIDs, and configured ports.

Frequently Asked Questions about start-project

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

FAQPage Schema
How do I start the MOM instance for my current repository?

Resolve the repository root with git rev-parse --show-toplevel, confirm the root .env.local exists, then run scripts/start-project.ps1 via PowerShell with -NoProfile and -ExecutionPolicy Bypass. Afterwards run status-project.ps1 to see the instance ID, PIDs, and ports.

What optional switches does the MOM start script support?

The start-project.ps1 script supports -SkipBuild, -SkipFrontend, and -SkipInfrastructure switches. These let you bypass the build step, the frontend startup, or the infrastructure setup when you only need part of the stack.

Why does startup fail when .env.local is missing?

A missing or invalid root .env.local is a blocking error by design. The skill never borrows an environment file from another checkout, because doing so could point the instance at the wrong ports, database, or containers.

Can I stop Java or Node processes by port to restart the instance?

No. The script only manages processes whose PID metadata, start time, normalized project root, and JAR or Vite path match the current instance. Killing processes by port is explicitly forbidden to avoid terminating unrelated applications.

Does the start script touch legacy global Docker containers?

No. The skill never runs docker start against legacy global containers. Compose mode uses only the project name, loopback ports, network, and volumes defined in the current instance configuration.