sdcorejs-env-setup

Set up Angular Portal, NestJS, or NextJS projects by resolving environment and runtime errors.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-env-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdcorejs-env-setup
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-env-setup
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-env-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes trial-and-error during first-time project setup by diagnosing missing environment configuration and common runtime blockers (like missing .env, port conflicts, Node version mismatches, or database connection failures).

Core Features & Use Cases

  • Stack detection: Automatically detects Angular Portal vs NestJS vs NextJS by checking expected config entry files.
  • Prerequisite verification: Confirms Node/PM tooling versions, lockfile-aligned package manager choice, and git identity before installing.
  • Per-stack bootstrap: Provides targeted steps for .env/.env.local creation, Postgres readiness/migrations, Angular environment setup, and Next.js conventions.
  • Smoke testing and verification: Instructs how to validate the running app with real commands and endpoint checks, not guesses.
  • Safety guardrails: Prevents risky actions like editing .env.example directly, committing real credentials, forcing installs that mask conflicts, or bypassing hooks without understanding implications.

Quick Start

Ask the AI to run sdcorejs-env-setup for your fresh clone when you say “thiết lập môi trường” or paste the error message you see (for example, EADDRINUSE or “connection refused”).

Frequently Asked Questions about sdcorejs-env-setup

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

FAQPage Schema
How do I set up a local environment for a new NestJS or Next.js clone?

To set up your local environment, the Skill detects your stack from config files and performs lockfile-aligned dependency installation, .env creation, and Postgres migration steps. It then verifies the dev server and health endpoints to ensure your clone runs correctly.

Why does my Next.js dev server fail with EADDRINUSE after a fresh clone?

Environment setup errors like EADDRINUSE are resolved by detecting port conflicts and verifying Postgres readiness. The Skill diagnoses missing .env files and Node version mismatches to clear initial runtime blockers after a fresh checkout.

How does environment setup handle Angular vs NestJS project detection?

Environment setup detects whether your project is Angular Portal, NestJS, or Next.js by checking expected config entry files. It then applies stack-specific steps, including Angular environment configurations and Next.js conventions.

Do I need a specific Node version for environment setup of Angular or NestJS?

You need compatible Node and package manager versions verified against your project lockfile before installation. The Skill confirms your git identity and tooling versions to prevent mismatches during environment setup.

What should I avoid when configuring .env files for a new Next.js clone?

When configuring .env files, you should avoid editing .env.example directly or committing real credentials. The Skill provides safety guardrails to prevent forcing installs that mask conflicts or bypassing hooks without understanding implications.

How do I verify my NestJS or Next.js environment setup is working?

To verify your environment setup, the Skill performs smoke testing using real commands and health endpoint checks. It instructs you how to validate the running app, ensuring your dev server operates correctly without guessing.