aiwg Prompt模板

Simple Building Blocks

AIWG's workflow source is readable and editable. The main building blocks are:

- Agents — specialist role instructions, such as Security Auditor or Test Architect, with defined responsibilities and supported tool access. - Skills — reusable procedures an agent can find from a goal and follow during a task. - Commands — explicit ways to request a workflow through the provider or CLI. - Rules — constraints for the assistant to follow, with tool-based checks where configured. - Behaviors — lifecycle actions and hooks on providers that support them. - Templates — structures for requirements, briefs, review reports, runbooks, and other outputs.

Many assets use Markdown with YAML metadata; hooks and utilities may also include executable scripts or structured configuration. The provider determines how each asset is loaded or invoked. A role definition is not a separate model, and a written rule is not proof that its constraint was enforced.

Install & Deploy

The prompt-led installer at the top of this README is the canonical beginner path. For manual setup:

npm i -g aiwg
cd /path/to/your/project
aiwg use all --provider claude   # replace claude with your provider selector

Deployment refreshes the shared context and reports verification and any required reload. Follow that result, then ask the agent to check the intended project and its AIWG connection. The manual installation reference covers the terminal path in detail.

For a deliberately narrower deployment, choose the relevant framework or addon instead of all. These are alternatives, not a sequence of required setup steps:

aiwg use sdlc --provider claude          # Software development
aiwg use forensics --provider claude     # Investigation workflows
aiwg use marketing --provider claude     # Campaign and content work
aiwg use media-curator --provider claude # Media collections
aiwg use research --provider claude      # Research artifacts
aiwg use civic-action --provider claude  # Civic review and preparation
aiwg use rlm --provider claude           # Context decomposition

For maintenance or an existing workspace that needs context migration, preview the relevant regeneration branch rather than treating every branch as installation:

Preview how to refresh this workspace’s provider context. If it needs existing-project extraction or migration, explain the proposed changes, preserve project-specific instructions, and verify the result.

The regeneration guide also covers canonical refresh and legacy compatibility. Use the branch that matches the workspace state. To scaffold a new project rather than connect the current one, see the new-project guide.

Multi-Platform Deployment

aiwg use all --provider antigravity    # Google Antigravity CLI (alias: agy)
aiwg use all --provider claude         # Claude Code
aiwg use all --provider codex          # OpenAI Codex
aiwg use all --provider copilot        # GitHub Copilot
aiwg use all --provider cursor         # Cursor
aiwg use all --provider factory        # Factory AI
aiwg use all --provider opencode       # OpenCode
aiwg use all --provider warp           # Warp Terminal
aiwg use all --provider devin          # Devin Desktop
aiwg use all --provider openclaw       # OpenClaw
aiwg use all --provider hermes         # Hermes
aiwg use all --provider openhuman      # OpenHuman
aiwg use all --provider pi             # Pi Coding Agent
aiwg use all --provider omp            # Oh My Pi

all means the complete deployable end-user surface. It intentionally omits contributor-only development bundles and packages that cannot be deployed directly.

Quick Start

Prerequisites: Node.js >=20.0.0 and an AI platform (Claude Code, GitHub Copilot, Cursor, Warp Terminal, or others). New installs should prefer Node 24. See Prerequisites Guide for details.

Release verification: Inspect the provenance and signature material for the release you install. The verification guide describes the available artifacts and commands.

Optional native features

The base global install intentionally excludes native packages whose lifecycle scripts require explicit trust. Core deployment, discovery, and provider tooling work without them. Enable only the capability you need:

Enable the native features needed for interactive terminals, semantic search, or graph-backed artifacts in this workspace. Explain which dependencies are required, install only the selected features, and verify they load.

The feature installer writes a private manifest and lockfile under the AIWG user data directory and approves scripts only for that feature. Do not set a broad user-level npm allow-scripts policy. If an older install left native package files present but unbuilt, aiwg doctor reports the broken capability and the same scoped rebuild command.

The Six Core Components

Project scope (recommended) vs user scope (global)

aiwg use supports project deployments, additive user mirrors, and a user-global bootstrap:

- Project scope — default. Run aiwg use all --provider <provider> from a project root and the artifacts land in that provider's project paths. This keeps project-specific instructions associated with the intended repository. Some providers also use user-level surfaces; check the reported deployment scope. This is the recommended default for new users. - User scope (additive mirror) — aiwg use all --provider <provider> --scope user keeps the project deployment and mirrors it to ~/.claude/agents/, ~/.claude/skills/, etc. - Global bootstrap — aiwg use all --provider claude --global installs framework and kernel assets in native user-level paths while leaving only lightweight context and provider bootstrap files in the current project. Ask the assistant to connect additional projects without deploying their own skill copies.

Shared user-level instructions can be useful for personal conventions, while project-local instructions keep a team's requirements and decisions with its repository. Review both scopes when a provider uses them together. The installer and provider inventory describe where files will go, so you can distinguish instructions that follow you across projects from instructions intended for this workspace.

See the Agentic Install Runbook for the zero-to-running setup path, and the CLI reference (under aiwg use → "Scope models") for the per-provider details and the global-install rough-edge inventory.

Claude Code Marketplace (Alternative)

Add the AIWG marketplace to Claude Code and install the SDLC, Agent Loop, and Compound Memory plugins.

The marketplace contains independently packaged framework and addon plugins, so you can install only the capabilities a Claude Code workspace needs. Source-distributed opt-in addons such as Civic Action deploy with aiwg use civic-action and do not imply a marketplace wrapper.

Installation Troubleshooting