Menu
Rebuild and redeploy AIWG from local customization source — makes recent edits live
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jmagly/aiwg --skill customize-rebuildThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
WCAG accessibility analysis for color palettes including contrast ratios, compliance checking, and remediation suggestions. Use when user needs to verify colors meet accessibility standards.
Generate, analyze, compare, export, and suggest color palettes using color theory. Use when user asks about colors, palettes, color schemes, or needs help choosing colors for a project.
Research current color trends from Pantone, architecture, film, and design. Use when user asks about trending colors, popular palettes, or wants research-backed color inspiration.
Based on SOC occupation classification
Showing SKILL.md
| namespace | aiwg |
| name | customize-rebuild |
| platforms | ["all"] |
| description | Rebuild and redeploy AIWG from local customization source — makes recent edits live |
You rebuild and redeploy AIWG from the user's local clone so their recent edits go live. This is the daily-driver skill for anyone in customization mode — fast, frictionless, and no jargon.
| Pattern | Example | Action |
|---|---|---|
| Apply changes | "apply my changes" | aiwg use all (fast path) |
| Full rebuild | "rebuild everything" | npm run build + aiwg use all |
| Redeploy workflow | "redeploy the current customizations" | Verify dev mode and build need, then use aiwg use all as the deployment step |
When triggered:
Verify customization mode is active:
aiwg version # should show [dev] and the repo path
If not in dev mode, tell the user and offer to run customize-setup.
Determine whether a TypeScript build is needed:
.ts files changed since last build: git -C <edgePath> diff --name-only HEAD -- src/ '*.ts'agentic/code/ changed (agents, skills, rules, prompts) — skip npm run build and use aiwg use all as the deployment stepsrc/, apps/web/, or package.json changed — run npm run build firstFor simplicity: if uncertain, ask "Did you change any TypeScript source files, or just agents/rules/skills?" and act accordingly. Default to the fast path (aiwg use all only) since most user customizations are in agentic/code/.
Fast path (most common — editing agents, rules, skills):
aiwg use all
Full rebuild path (when TS source changed):
npm --prefix <edgePath> run build
aiwg use all
Report result concisely:
Done — deployed X agents, Y skills, Z rules from ~/my-aiwg.
Changes are live in your next session.
Do NOT surface "npm run build" details to the user unless they asked about TypeScript changes. Just report "Done" with the deployment counts.
User: "apply my changes"
Action: Check dev mode → aiwg use all (fast path, no TS changes detected)
Response: "Done — deployed 180 agents, 360 skills, 16 rules from ~/my-aiwg."
User: "I added a rule, make it live"
Action: aiwg use all (rule files are in agentic/code/, no build needed)
Response: "Done — your new rule is live. 181 rules deployed."
User: "I changed some TypeScript source, rebuild everything"
Action: npm run build → aiwg use all
Response: "Built and deployed from ~/my-aiwg. All changes are live."
If not in customization mode:
"It looks like AIWG isn't running from a local clone right now. Want me to set up customization mode first?"
loadConfig() for edgePath