Install any skill in seconds. Free to start, no credit card required.
Get Started Free →butterbase-ai/deploy-frontend
Use when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages
Passed 17 of 20 test cases with the skill, and 4 of 20 without it.
and 15 more in the full report
15 fixed4 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are initiating an Edge SSR deployment for a Next.js application on Cloudflare Workers using `manage_edge_ssr`. What framework key should be specified during creation?
| Checked | Without skill | With skill |
|---|---|---|
| Passes nextjs-edge as the framework parameter. | Missed | Passed |
The instructions your model reads when the skill loads.
7-step workflow for deploying static frontends to Butterbase. Covers building, CORS, zipping, uploading, and verification.
| Framework | Build command | Output dir | Env prefix | Framework flag |
|---|---|---|---|---|
| React (Vite) | npm run build | dist/ | VITE_ | react-vite |
| Next.js (static) | next build | out/ | NEXT_PUBLIC_ | nextjs-static |
| Plain HTML | (none) | project root | N/A | static |
Note: Next.js requires
output: 'export'innext.config.jsto produce a static export.
Use manage_frontend with action: "set_env" to configure the API URL and app ID before building. These variables are injected at build time by the framework.
{
"app_id": "app_abc123",
"action": "set_env",
"vars": {
"VITE_API_URL": "https://api.butterbase.ai/v1/app_abc123",
"VITE_APP_ID": "app_abc123"
}
}
VITE_NEXT_PUBLIC_REACT_APP_set_env upserts; you can call it again to add or change variables.
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.