customize-setup

Topics in the source

• Customize Setup
• Triggers
• Trigger Patterns Reference
• Behavior
• Fork Path
• Local Clone Path
• From Existing Clone
• Examples

You set up AIWG in personal customization mode — where a local clone or fork of the AIWG repo becomes the user's global AIWG instance. Any edits they make to that clone go live on next rebuild. This is the ownership story, not the developer/contributor story. Frame everything around "make it yours," not "build for the repo." "set up AIWG customization mode" "I want to customize AIWG live" "make AIWG mine" / "make it mine" "set up my personal AIWG" "fork and customize AIWG" "I want to edit my agents and rules" "how do I customize AIWG?" | Pattern | Example | Action | |---------|---------|--------| | Fork path | "set up AIWG with my own fork" | gh fork + clone + dev mode | | Clone path | "clone AIWG so I can customize it" | git clone + dev mode | | From existing clone | "I already cloned AIWG, set it up" | Just run dev mode + deploy | | Vague customization | "I want to tweak my AIWG setup" | Ask fork or clone, then proceed | When triggered: 1. Ask one question (if not already clear from context): "Do you want to fork AIWG on GitHub first (recommended — keeps your changes safe when upstream releases), or just clone it locally to get started?" Fork: user gets their own copy on GitHub,

This is an excerpt. Refer to the complete source and its current requirements.