use
Deploy AIWG frameworks and addons to the current workspace across supported providers
What this skill does
# AIWG Use You deploy AIWG frameworks and addons to the current workspace. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "set up sdlc" → deploy sdlc-complete framework - "add the marketing framework" → deploy media-marketing-kit - "activate rlm" → deploy rlm addon - "scaffold the writing framework" → deploy voice-framework addon - "get the ring methodology" → deploy ring-methodology addon ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Framework deploy | "use sdlc" | Run `aiwg use sdlc-complete` | | Addon deploy | "use the ralph addon" | Run `aiwg use ralph` | | Provider-scoped deploy | "deploy sdlc to copilot" | Run `aiwg use sdlc-complete --provider copilot` | | Dev mode deploy | "deploy from local source" | Run `aiwg use sdlc-complete --dev` | | All frameworks | "deploy everything" | Run `aiwg use all` | ## Behavior When triggered: 1. **Extract intent**: - Which framework or addon is requested? (resolve shorthand: "sdlc" → `sdlc-complete`, "marketing" → `media-marketing-kit`, "forensics" → `forensics-complete`, "research" → `research-complete`, "curator" → `media-curator`) - Is a specific provider mentioned? Default is the detected active provider. - Is `--dev` (local source) requested? 2. **Resolve the target**: **Frameworks:** | Shorthand | ID | |-----------|-----| | sdlc | sdlc-complete | | marketing | media-marketing-kit | | forensics | forensics-complete | | research | research-complete | | curator | media-curator | **Addons:** | Shorthand | ID | |-----------|-----| | ralph | ralph | | rlm | rlm | | ring | ring-methodology | | voice | voice-framework | | writing | writing-quality | | testing | testing-quality | | utils | aiwg-utils | 3. **Run the appropriate command**: ```bash # Deploy a framework (default provider) aiwg use sdlc-complete # Deploy an addon aiwg use ralph # Deploy to a specific provider aiwg use sdlc-complete --provider copilot # Deploy from local development source aiwg use sdlc-complete --dev # Deploy all frameworks and addons aiwg use all ``` 4. **Report the result** inline — confirm what was deployed, where, and any warnings about missing dependencies. ## Examples ### Example 1: Deploy the SDLC framework **User**: "use sdlc" **Extraction**: Framework `sdlc-complete`, default provider **Action**: ```bash aiwg use sdlc-complete ``` **Response**: "Deployed sdlc-complete to claude-code. Agents written to `.claude/agents/`, commands to `.claude/commands/`, rules to `.claude/rules/`. Registered in `.aiwg/frameworks/registry.json`." ### Example 2: Deploy to a specific provider **User**: "deploy the sdlc framework to GitHub Copilot" **Extraction**: Framework `sdlc-complete`, provider `copilot` **Action**: ```bash aiwg use sdlc-complete --provider copilot ``` **Response**: "Deployed sdlc-complete to copilot. Agents written as `.github/agents/*.agent.md`, commands to `.github/prompts/`, rules to `.github/instructions/`." ### Example 3: Deploy an addon **User**: "activate the ring methodology addon" **Extraction**: Addon `ring-methodology`, default provider **Action**: ```bash aiwg use ring-methodology ``` **Response**: "Deployed ring-methodology addon to claude-code. 7 rules installed to `.claude/rules/`." ### Example 4: Deploy all frameworks **User**: "deploy everything" **Extraction**: All frameworks and addons **Action**: ```bash aiwg use all ``` **Response**: "Deployed all frameworks to claude-code: sdlc-complete, media-marketing-kit, forensics-complete, research-complete, media-curator, and 7 addons." ## Clarification Prompts If the user's intent is ambiguous: - "Which framework would you like to deploy? Available: sdlc-complete, media-marketing-kit, forensics-complete, research-complete, media-curator" - "Should I deploy to the current provider (claude-code) or a different one?" ## References - @$AIWG_ROOT/src/cli/handlers/use.ts — Use command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @CLAUDE.md — Multi-platform provider table
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.