dev-init

To set up a Next.js and TypeScript development environment, you need to verify the Node.js toolchain, install npm dependencies, and check for essential package lock files. This process ensures your workspace is configured correctly before coding.

Environment verification checks for the presence of necessary development tools like Node.js, npm, npx, and Git. It confirms these foundational tools are installed and accessible before proceeding with dependency installation.

To scaffold project files during initialization, the system creates initial feature tracking and Product Requirements Document files if they do not already exist in your directory, ensuring essential documentation is in place.

Yes, you can check integration status for GitHub, Supabase, and Brave Search during project setup. The initialization process reports whether the necessary tokens and configurations for these services are currently active.

The best way to automate dependency installation is to run an initialization skill that verifies your environment and installs project dependencies using npm automatically, ensuring all required packages are present.

Yes, the initialization works without existing package lock files by checking for their presence and proceeding with dependency installation. It scaffolds missing essential files like feature tracking documents while setting up the workspace.