Custom Build Process Skill

Custom Build Process

Purpose

This is a project-specific custom skill called by the Builder workflow after implementation is complete. It handles building project artifacts specific to this project (claudecode_webui).

Generic workflow skills invoke this skill if it exists; if absent, the build step is skipped.

When Called

The Builder invokes this skill from its working directory (the worktree) after code changes are complete but before testing.

Build Steps

Frontend Build (if frontend code changed)

Check if frontend code was modified:

git diff --name-only HEAD~1 | grep -q "^frontend/" && echo "Frontend changed"

If frontend code changed, build it. First, install dependencies if needed — only needed once per worktree, skip if frontend/node_modules already exists. Plain npm install fails in builder containers (npm error Cannot read properties of null (reading 'edgesOut')); --legacy-peer-deps resolves it — verified 2026-09-29. This install runs only inside the builder's own worktree — never in the production checkout, since it's scoped to frontend/node_modules under cwd, a gitignored, worktree-local directory.

if [ ! -d frontend/node_modules ]; then
    (cd frontend && npm install --legacy-peer-deps)
fi

Then build:

# Clean stale build artifacts so old hashed chunks don't linger across worktree checkouts
rm -rf frontend/dist

# Build fresh
cd frontend && npm run build

Verification

After build:

Verify frontend/dist/ directory was created/updated
Check build output for errors
Report any build failures

Usage by Generic Skills

The Builder workflow calls this skill like:

Invoke custom-build-process skill (no arguments - uses cwd)

The skill runs project-specific build commands in the Builder's working directory. If this skill does not exist, the generic workflow skips the build step.

Agent Skills: Custom Build Process

Install this agent skill to your local

Skill Files