stuffbucket Pages
Family that automates GitHub Pages deployment for Vite projects. The skills correspond to sequential pipeline steps — run them in this order on first deploy:
pages-prepare-vitepages-build-vitepages-commit-vitepages-push-vitepages-publish-vite
After the first run, individual steps can be re-run as needed (e.g. re-build + push without re-preparing).
Routing table
| Step | Skill | What it does |
|---|---|---|
| 1. Prepare | pages-prepare-vite |
Patch vite.config.ts base path, generate .github/workflows/deploy.yml, optionally set Pages source to "GitHub Actions" via API. Handles GHE detection and curl-redirect URL discovery. |
| 2. Build | pages-build-vite |
Local vite build, auto-detects npm/pnpm/yarn, verifies base path and dist/index.html. Same build CI will run. |
| 3. Commit | pages-commit-vite |
Stage and commit deploy.yml + patched vite.config.ts. Refuses to commit without the workflow file. Never commits dist/. |
| 4. Push | pages-push-vite |
Push current branch; triggers the workflow. Guards remote and committed workflow. |
| 5. Publish | pages-publish-vite |
Poll the workflow run, fetch Pages info, follow redirects to discover the actual served URL (handles GHE codespace-style randomized subdomains). |
Cross-family edges
figma-make-to-vite— common predecessor: convert a Figma Make export into a Vite app, then deploy it through this pipeline.design-frontend,design-polish,design-check— typical predecessors that produce ship-worthy UI.react-best-practices— bundle / perf concerns surfaced duringpages-build-vite.git-workflow-skill— the commit and push steps; use here when the user prefers a richer git workflow.tauri— explicitly NOT in this pipeline; Tauri ships installers, not static sites.
Decision flow
- First-time deploy (no
deploy.yml, no base path) → start atpages-prepare-vite, run the full chain. - Re-deploy after content change →
pages-build-vite→pages-commit-vite→pages-push-vite→pages-publish-vite. - Switching from branch-based Pages to Actions source →
pages-prepare-vite. - Workflow ran but the URL doesn't work (GHE) →
pages-publish-vitefor redirect-following. - Local build error before push →
pages-build-vitein isolation.
When NOT to use this skill
- Non-Vite frameworks (Next.js export, Astro, SvelteKit static-adapter) — the patcher is Vite-specific.
- Hosting on Cloudflare Pages / Netlify / Vercel — these are GitHub Pages workflows.
- Tauri or other desktop bundles — see the
taurifamily. - A project that already has a working
deploy.ymland just needs a one-off deploy —pages-push-viteis enough.