Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
itallstartedwithaidea avatar

Edge Deployment

  • 53 installs
  • 31 repo stars
  • Updated April 12, 2026
  • itallstartedwithaidea/agent-skills

Deploy a detected frontend stack to Vercel or Cloudflare with previews, production promotes, env vars, and domains—without hand-rolling platform config.

About

Edge Deployment is an Agent Skills™ package that automates taking a frontend repository from “build succeeds locally” to “running on Vercel or Cloudflare” with minimal manual platform trivia. It targets solo and indie builders who ship SaaS dashboards, marketing sites, and hybrid SSR apps and do not want to memorize each framework’s default install, build, and output settings across two major edge hosts. The skill inspects the project, infers the framework from a broad catalog, selects an appropriate static or server-rendered strategy, wires environment variables per stage, and walks through preview and production promotion patterns tied to git workflow. It explicitly accounts for how Vercel’s serverless functions differ from Cloudflare Workers constraints so the agent does not paste the wrong runtime assumptions. Beyond the first deploy, it covers custom domains and ongoing environment management so repeat releases stay boring. Use it when the product code is ready and the blocker is reliable, repeatable edge hosting—not when you still need feature implementation or load testing in isolation. It pairs naturally with CI-oriented habits: PR previews for validation and merge-to-main

  • Auto-detects 40+ frontend frameworks and configures build commands and output directories accordingly
  • Supports Vercel and Cloudflare Pages/Workers with SSR versus SSG routing choices
  • Manages preview deployments on pull requests and production deployments on merge
  • Handles environment variables and custom domain setup across environments
  • Encodes platform differences between Vercel serverless functions and Cloudflare Workers edge runtime

Edge Deployment by the numbers

  • 53 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #710 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill edge-deployment

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs53
repo stars31
Security audit3 / 3 scanners passed
Last updatedApril 12, 2026
Repositoryitallstartedwithaidea/agent-skills

What it does

Deploy a detected frontend stack to Vercel or Cloudflare with previews, production promotes, env vars, and domains—without hand-rolling platform config.

Files

SKILL.mdMarkdownGitHub ↗

Edge Deployment

Part of Agent Skills™ by googleadsagent.ai™

Description

Edge Deployment automates the deployment of frontend applications to Vercel and Cloudflare with auto-detection of 40+ frameworks, intelligent build configuration, and environment-specific settings. The agent identifies the framework, configures the build pipeline, sets up environment variables, and deploys with zero manual configuration for standard projects.

Modern edge platforms eliminate the need for traditional server provisioning. This skill encodes the deployment patterns for both static (SSG) and server-rendered (SSR) applications across Vercel and Cloudflare Pages/Workers. The agent selects the optimal deployment strategy based on the framework's rendering capabilities, the project's data requirements, and the target platform's runtime constraints.

The skill handles the full deployment lifecycle: initial setup, preview deployments for pull requests, production deployments on merge, custom domain configuration, and environment variable management. It understands the differences between Vercel's serverless functions and Cloudflare Workers' edge runtime, routing to the appropriate platform based on project needs.

Use When

  • Deploying a new frontend project for the first time
  • Configuring CI/CD for preview and production deployments
  • Migrating between deployment platforms (Vercel to Cloudflare or vice versa)
  • Setting up custom domains and SSL certificates
  • Configuring environment variables for different deployment stages
  • Optimizing build settings for faster deploys

How It Works

graph TD
    A[Project Source] --> B[Detect Framework]
    B --> C{Framework Type}
    C -->|Next.js/Nuxt/SvelteKit| D[SSR Deployment]
    C -->|Astro/Vite/CRA| E[Static Deployment]
    D --> F{Target Platform}
    E --> F
    F -->|Vercel| G[Configure vercel.json]
    F -->|Cloudflare| H[Configure wrangler.jsonc]
    G --> I[Set Build Command + Output Dir]
    H --> I
    I --> J[Configure Env Variables]
    J --> K[Deploy Preview on PR]
    K --> L[Deploy Production on Merge]

Framework detection examines package.json dependencies, config files, and directory structure. The agent maps each framework to its optimal build command, output directory, and runtime configuration.

Implementation

Vercel Deployment

{
  "framework": "nextjs",
  "buildCommand": "next build",
  "outputDirectory": ".next",
  "regions": ["iad1", "sfo1", "lhr1"],
  "env": {
    "DATABASE_URL": "@database-url",
    "API_KEY": "@api-key"
  }
}
# Deploy to Vercel
npx vercel --prod

# Preview deployment
npx vercel

# Set environment variable
npx vercel env add DATABASE_URL production

Cloudflare Pages Deployment

// wrangler.jsonc
{
  "name": "my-app",
  "pages_build_output_dir": "./dist",
  "compatibility_date": "2026-04-01",
  "vars": {
    "ENVIRONMENT": "production"
  }
}
# Deploy to Cloudflare Pages
npx wrangler pages deploy ./dist --project-name=my-app

# Preview deployment
npx wrangler pages deploy ./dist --project-name=my-app --branch=feature-x

GitHub Actions CI/CD

name: Deploy
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: "20" }
      - run: npm ci
      - run: npm run build
      - if: github.event_name == 'push'
        run: npx wrangler pages deploy ./dist --project-name=my-app
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CF_API_TOKEN }}

Best Practices

  • Use preview deployments for every PR to catch issues before production
  • Store secrets in the platform's encrypted environment variable system, never in code
  • Pin framework and runtime versions to avoid build drift between environments
  • Configure caching headers at the edge for static assets (1 year for hashed files)
  • Use platform-specific adapters (e.g., @sveltejs/adapter-cloudflare) for SSR
  • Monitor build times and set alerts for regressions above your baseline

Platform Compatibility

PlatformSupportNotes
CursorFullShell tool for CLI deploys
VS CodeFullVercel/CF extensions available
WindsurfFullDeployment workflow support
Claude CodeFullCLI-based deployments
ClineFullTerminal integration
aiderPartialConfig file generation only

Related Skills

  • React Best Practices
  • Web Design Guidelines
  • CI/CD Pipelines
  • Cloudflare Workers

Keywords

edge-deployment vercel cloudflare-pages ci-cd framework-detection static-deployment ssr-deployment preview-deployment

---

© 2026 googleadsagent.ai™ | Agent Skills™ | MIT License

Related skills

FAQ

Is Edge Deployment safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

DevOps & CI/CDdevopsfrontend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.