Menu
Build static web output where the Mapache preview canvas can serve it.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | mapache-preview-build |
| description | Build static web output where the Mapache preview canvas can serve it. |
Use this skill when building a static website or static frontend bundle in a Mapache preview-capable session.
For Vite, prefer:
npm run build -- --outDir build --base ./
or set both base and build.outDir in vite.config.js:
export default defineConfig({
base: "./",
build: {outDir: "build"},
});
For other frameworks, use the equivalent settings for:
QA a Mapache preview with the runner-owned browser QA command, status checks, console logs, screenshots, and structured reports.
Host an app or API behind the Mapache preview gateway.
Work from or create GitHub issues with repository context, labels, clarification, and implementation flow.
Run or compose Mapache browser QA tests from checked-in e2e/qa case manifests using Chrome DevTools. Use when the user explicitly asks for QA testing, smoke testing, browser testing, end-to-end testing, or a named QA case, and when issue-workflow changes frontend behavior and requires QA before PR completion.
Use when the user provides a GitHub issue number and wants Codex to complete the whole implementation workflow: update local main from remote, read the issue and comments, create an issue-named branch, implement and test the change, compose and run QA for frontend changes, commit, push, open a pull request, return to main, and comment or label the issue when blocked or waiting on user action.
Route agents through the Mapache developer wiki before non-trivial implementation work.