customize-rebuild
Rebuild and redeploy AIWG from local customization source — makes recent edits live
What this skill does
# Customize Rebuild 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. ## Triggers - "apply my changes" - "make this live" / "make it live" - "rebuild" / "redeploy" - "recompile" - "push my edits live" - "update my AIWG" - "deploy my customizations" ## Trigger Patterns Reference | 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 | ## Behavior When triggered: 1. **Verify customization mode is active**: ```bash aiwg version # should show [dev] and the repo path ``` If not in dev mode, tell the user and offer to run `customize-setup`. 2. **Determine whether a TypeScript build is needed**: - Check if any `.ts` files changed since last build: `git -C <edgePath> diff --name-only HEAD -- src/ '*.ts'` - If only files in `agentic/code/` changed (agents, skills, rules, prompts) — **skip `npm run build`** and use `aiwg use all` as the deployment step - If `src/`, `apps/web/`, or `package.json` changed — run `npm run build` first For 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/`. 3. **Fast path** (most common — editing agents, rules, skills): ```bash aiwg use all ``` 4. **Full rebuild path** (when TS source changed): ```bash npm --prefix <edgePath> run build aiwg use all ``` 5. **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. ## Examples ### Example 1: Daily-use apply **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." ### Example 2: After adding a rule file **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." ### Example 3: After editing TypeScript **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." ## Clarification Prompts 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?" ## References - @$AIWG_ROOT/bin/aiwg.mjs — dev mode delegation logic - @$AIWG_ROOT/src/channel/manager.mjs — `loadConfig()` for edgePath - @$AIWG_ROOT/docs/customization/README.md — Customization guide
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.