app-start

Validate ports, Docker containers, and Node processes before starting the Arsenale development environment.

11|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dnviti/arsenale --skill app-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-start
Source: https://github.com/dnviti/arsenale/tree/main/.claude/skills/app-start
Command: npx skills add https://github.com/dnviti/arsenale --skill app-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start the Arsenale development environment safely by performing pre-flight checks, coordinating containers, and ensuring a clean startup sequence to avoid port conflicts and runtime errors.

Core Features & Use Cases

  • Port, container, and process verification prior to startup.
  • Coordinated setup of Docker-based services (PostgreSQL, guacd) and Prisma lifecycle, followed by launching the API and frontend servers.
  • Automatic restart workflow when conflicts are detected, with guidance on remediation.

Quick Start

Run the app-start skill to initialize and bring up the Arsenale development environment safely.

Frequently Asked Questions about app-start

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

FAQPage Schema
How do I safely start a local dev environment with Docker and Node without port conflicts?

Safely start a local dev environment by running pre-flight checks that validate port availability, Docker containers, and Node processes before startup. This coordinates Docker services and Node servers to prevent runtime conflicts.

What's the best way to coordinate PostgreSQL and guacd Docker containers with Prisma during startup?

Coordinate PostgreSQL and guacd Docker containers with Prisma setup by executing predev lifecycle steps that initialize containers and database schemas before launching concurrent API and frontend servers.

Why does my dev server fail to start when ports 3000 and 3001 are already in use?

Your dev server fails to start because pre-flight port checks detect existing processes on ports 3000 and 3001. The startup workflow applies an automatic restart on conflict and provides remediation guidance to clear the blockage.

How do I handle Docker container and Node process conflicts before launching my development environment?

Handle Docker container and Node process conflicts by running a verification step that checks active containers and processes, automatically restarting when conflicts are detected, and providing a single retry with remediation guidance.

Does this startup workflow provide error handling and remediation guidance for local development?

Yes, the startup workflow provides error handling by monitoring for startup errors during predev and dev steps. It delivers remediation guidance and applies a single retry to ensure end-to-end environment startup success.