bootstrap

Orchestrates safe project bootstrapping for Vercel-linked Next.js repositories.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/rauell1/safaricharge --skill bootstrap-rauell1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/rauell1/safaricharge/tree/main/.agents/skills/bootstrap
Command: npx skills add https://github.com/rauell1/safaricharge --skill bootstrap-rauell1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from bootstrapping repositories that depend on Vercel, databases, auth, and managed integrations by enforcing the correct setup order and preventing unsafe early commands.

Core Features & Use Cases

  • Safe project linking: Verifies Vercel authentication and project linkage before any database or development commands run.
  • Environment setup: Locates env templates, creates local env files, and checks required keys against pulled values.
  • Managed resource provisioning: Guides Neon and other Vercel-linked setup flows, including AUTH_SECRET generation and env syncing.
  • First-run validation: Runs database and dev commands only after prerequisites are satisfied and reports precise failure points.
  • Use Case: Ideal for a Next.js app that must be connected to Vercel and its backend services in a repeatable, low-risk sequence.

Quick Start

Ask the assistant to bootstrap the repository in the correct Vercel-first order and report any missing linkage, environment, or database prerequisites.

Frequently Asked Questions about bootstrap

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

FAQPage Schema
How do I safely bootstrap a Next.js app linked to Vercel and a database?

To safely bootstrap a Next.js app, you must follow a strict Vercel-first setup order: verify CLI access, link the project, provision environment variables, and run database setup before starting development. This prevents unsafe early commands.

What is the correct order for setting up Vercel environment variables and database connections?

The correct setup order for Vercel environment variables is to first verify Vercel authentication and project linkage, then locate env templates, pull required keys, sync managed resources like Neon databases, and finally run database commands.

Why does my Vercel dev server fail when environment variables are missing?

Your Vercel dev server fails because the bootstrapping process requires complete environment variables. The setup checks required keys against pulled values and validates database prerequisites before allowing the first-run development command to execute.

Can I set up my Neon database before linking my repository to Vercel?

No, you should not set up your Neon database before linking to Vercel. Safe project bootstrapping requires verifying Vercel authentication and project linkage first to ensure environment variables and managed integrations are correctly provisioned.

How do I generate an AUTH_SECRET for my Vercel project environment?

Generating an AUTH_SECRET is handled during the managed resource provisioning phase. The setup process guides you through AUTH_SECRET generation and environment syncing after Vercel project linkage is verified and local env files are created.

What are the limitations of automated Vercel project bootstrapping?

Automated Vercel project bootstrapping requires ordered verification of CLI access, project linkage, environment completeness, and database commands. If any prerequisite fails, the process stops and reports the precise failure point rather than attempting partial setup.