init
Initialize AIWG configuration for an existing project by creating .aiwg/aiwg.config with provider and script entries
What this skill does
# Init You initialise AIWG configuration for an existing project by creating `.aiwg/aiwg.config` with provider registry entries and custom script definitions. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "aiwg init" → run with defaults or interactively - "add aiwg config" → create `.aiwg/aiwg.config` - "set up providers" → interactive provider selection - "register my scripts" → interactive script registration ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Default init | "aiwg init" | Run `aiwg init` with defaults | | Interactive | "init aiwg interactively" | Run `aiwg init --interactive` | | Provider flag | "init aiwg for copilot" | Run `aiwg init --provider copilot` | | Config check | "do I have an aiwg config?" | Read `.aiwg/aiwg.config` | ## Behavior When triggered: 1. **Distinguish from `new`**: - `init` adds AIWG configuration to an **existing** project — it does not create a new project directory or the full `.aiwg/` subdirectory tree. - If the project has no `.aiwg/` directory at all, suggest `aiwg new .` instead. 2. **Extract arguments**: - Is `--interactive` requested? If so, ask which providers to configure and which scripts to register. - Is a specific `--provider` given? Pre-fill that entry in the registry. - Is `--interactive` absent? Write a minimal config with the detected provider. 3. **Run the appropriate command**: ```bash # Default: write minimal config, auto-detect provider aiwg init # Interactive: guided wizard for providers and scripts aiwg init --interactive # Pre-configure a specific provider aiwg init --provider copilot ``` 4. **What the command creates** — `.aiwg/aiwg.config` with: - `providers` block: list of configured provider names and their deploy paths - `scripts` block: named shell commands for use with `aiwg run` - Metadata: version, created timestamp 5. **Report the result** — confirm path written and show the generated config summary. ## Examples ### Example 1: Default init **User**: "aiwg init" **Extraction**: No flags, auto-detect provider (claude-code) **Action**: ```bash aiwg init ``` **Response**: "Created `.aiwg/aiwg.config` with provider `claude-code` pre-configured. No scripts registered yet. Use `aiwg init --interactive` to add providers or scripts, or edit the file directly." ### Example 2: Interactive init **User**: "Set up AIWG config interactively" **Extraction**: Interactive flag required **Action**: ```bash aiwg init --interactive ``` **Response**: Wizard prompts for providers to enable and scripts to register, then writes `.aiwg/aiwg.config`. Confirms: "Configured 2 providers (claude-code, copilot) and 3 scripts (test, lint, deploy). Config written to `.aiwg/aiwg.config`." ### Example 3: Single provider **User**: "Init aiwg config for GitHub Copilot" **Extraction**: Provider `copilot` specified **Action**: ```bash aiwg init --provider copilot ``` **Response**: "Created `.aiwg/aiwg.config` with provider `copilot` configured (deploy path: `.github/`). Run `aiwg use sdlc --provider copilot` to deploy frameworks." ### Example 4: Config already exists **User**: "aiwg init" **Extraction**: `.aiwg/aiwg.config` already present **Action**: Read existing config, report what is configured, and offer `--interactive` to update rather than overwriting. **Response**: "`.aiwg/aiwg.config` already exists (providers: claude-code; scripts: test, deploy). Run `aiwg init --interactive` to update the configuration." ## Clarification Prompts If the user's intent is ambiguous: - "Is this an existing project, or would you like to create a new one? (For a new project, `aiwg new <name>` sets up the full structure.)" - "Would you like to configure providers and scripts interactively, or should I write defaults?" ## References - @$AIWG_ROOT/src/cli/handlers/init.ts — `init` command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/skills/run/SKILL.md — Running registered scripts
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.