Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    web deploy doctor

    1

    Fix build failures and runtime errors for Vercel, Netlify, and Cloudflare deployments.

    Free

    Security scanned
    web deploy doctor

    web deploy doctor

    Example session with this skill installed

    My Vite app works locally but gives a 404 when I refresh the page on Netlify. Here is my project structure.

    • Read your context and instructions
    • Compiled the web deploy doctor

    I have analyzed your project structure. The issue is a missing Single Page Application (SPA) fallback configuration. Netlify's servers try to find a physical file at the route path instead of letting your client-side router handle it.

    Netlify SPA Routing Fix

    SymptomDetected IssueRequired File
    404 on refreshMissing SPA Rewritepublic/_redirects
    Build ToolVitevite.config.js
    FrameworkReact/Vue/SvelteClient-side Routing

    To fix this, create a file named _redirects in your public folder with the following content:

    /*    /index.html   200
    

    Alternatively, if you prefer using a configuration file, add this to your netlify.toml in the root directory:

    [[redirects]]
      from = "/*"
      to = "/index.html"
      status = 200
    

    Next steps

    1. Create the public/_redirects file with the rewrite rule provided above.
    2. Commit and push the change to trigger a new Netlify build.
    3. Verify by navigating to a sub-route (e.g., /dashboard) and refreshing the browser.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Your build passes locally but fails the second it hits Vercel, Netlify, or Cloudflare. This skill identifies why your web app breaks during deployment, from case-sensitive import errors to missing environment variables and SPA routing 404s.

    What it does

    • Syncs lockfiles by detecting mismatches between package.json and lockfiles that trigger npm ci failures.
    • Validates import casing to find files that resolve on Windows/macOS but fail on Linux-based build servers.
    • Checks host configurations for Vite, Next.js, and Astro, ensuring the Output Directory and Root Directory match host expectations.
    • Identifies environment leaks by scanning client-side code for hardcoded localhost URLs or exposed secrets.
    • Fixes SPA routing by recommending the specific rewrite rules needed for React or Vue routers to work on refresh.

    How it works

    1. Initial diagnosis by analyzing the host, framework, and the first error line from your build log.
    2. Project inspection using a specialized script to scan for case mismatches, missing dependencies, and incorrect build paths.
    3. Log matching against a catalog of 30+ known deployment errors like ERESOLVE or vite: not found.
    4. Step-by-step resolution starting from installation issues through to runtime CORS or API URL fixes.

    Frameworks & tools

    Supports Vite, Create React App, Next.js, Astro, and monorepos. Optimized for deployment to Vercel, Netlify, Cloudflare Workers/Pages, and GitHub Pages.

    Why this beats prompting it yourself

    Generic AI advice often misses the specific quirks of host-specific build environments. This skill uses a structured check against real-world failure patterns like Linux case-sensitivity and SPA fallback requirements that generic prompts overlook.

    Use cases

    • Debugging a "blank page" error after a successful Vercel deploy.
    • Fixing "404 on refresh" for a React Router app on Netlify.
    • Resolving npm ci sync errors during the CI/CD pipeline.
    • Pre-flight checking a project to ensure environment variables are correctly mapped.

    Known limitations

    Cannot access host dashboards or private environment variables directly. Focuses primarily on static exports and basic SSR; complex database or backend-heavy deployments may require manual verification.

    Read-only file access. Cannot see host dashboards, private secrets, or run full builds. Limited support for complex SSR or database-specific deployment issues.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    • Free with an Agensi account

    Requires

    Wrangler
    Node.js
    Git

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files
    Environment Variables

    Allowed Hosts

    (
    .
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill specializes in the 'it works on my machine' problem by identifying build-server specific issues like Linux case-sensitivity, lockfile mismatches, and host-specific rewrite rules that standard IDE debuggers often miss.

    The skill is optimized for modern frontend frameworks including Next.js, Vite, Astro, and Create React App, specifically when deployed to Vercel, Netlify, Cloudflare Pages, or GitHub Pages.

    No, the skill operates by analyzing your build logs and project structure; it does not require or request direct access to your hosting dashboard or private environment variables for security reasons.

    While highly effective for static sites and SSR frameworks, it has limited visibility into complex database connections or backend-heavy infrastructure failures that occur outside the build pipeline.

    You get full access to the diagnostic workflow, the specialized inspection scripts, and the curated catalog of over 30+ known deployment error resolutions.

    Simply paste your build log or describe the deployment error to the agent; the skill will then guide you through a targeted scan of your project files to pinpoint the discrepancy.

    New in LLM Ops