Technical Documentation: vudovn/antigravity-kit
ℹ️ Provenance: Multi-Tier Ingestion · CodeWiki Reference
Overview (`README.md`)
AG KIT
Production profile
AG Kit installs a complete .agents/ workspace contract. Antigravity is the supported production runtime for this release. Other tools may read the Markdown components, but runtime behavior outside Antigravity is not part of the production compatibility guarantee.
| Capability | Production implementation |
|---|---|
| Rules and skill discovery | .agents/rules/, .agents/skills/, .agents/workflows/ |
| Specialist routing | 20 role definitions and intelligent-routing skills |
| Persistent context | .agents/memory/ and context-compression guidance |
| Orchestration | /coordinate, /orchestrate, Antigravity /agents and /tasks |
| MCP | Workspace config plus explicit, backup-aware sync helper |
| Tool safety | Native PreToolUse gate for high-confidence destructive commands |
| Packaging | Local Antigravity plugin bundle with a SHA-256 content inventory |
| Validation | Toolkit CI, Antigravity Doctor, regression tests, Dependency Review, CLI and web checks |
The native hook is deliberately narrow. It blocks root-filesystem deletion, drive formatting, and raw-disk overwrite patterns while allowing normal project cleanup such as deleting dist/ or node_modules/. It does not replace Antigravity permissions, workspace trust, sandboxing, or human approval.
Requirements
- Node.js 22 or newer for repository-level Antigravity tooling.
- Python 3.10 or newer for AG Kit validators and utility scripts.
- A trusted Google Antigravity workspace.
- Git for safe update, review, and rollback workflows.
The published CLI currently supports Node.js 18 or newer; the Antigravity integration checks run on Node.js 22.
Quick start
Install into a project
npx @vudovn/ag-kit initOr install the CLI globally:
npm install @vudovn/ag-kit
ag-kit initDo not add .agents/ to the project .gitignore when Antigravity needs to index rules, skills, or workflows. To keep it local without disabling discovery, add .agents/ to .git/info/exclude instead.
Verify the workspace
npm run check:agents
npm run check:antigravity
npm run test:antigravitycheck:antigravity is read-only. The default MCP example contains YOUR_API_KEY, so the normal doctor reports a warning until the example is configured. Use strict mode only after all placeholders have been resolved:
node .agents/hooks/antigravity-doctor.mjs --strictOpen in Antigravity
After opening the repository as a trusted workspace:
- Confirm slash commands such as
/plan,/coordinate, and/orchestrateare discovered. - Confirm relevant skills are selected from
.agents/skills/. - Run a normal command such as
npm testand confirm it is allowed. - Verify the safety hook with a mocked payload rather than executing a destructive command:
printf '%s' '{"tool_args":{"CommandLine":"rm -rf /"}}' \
| node .agents/hooks/validate-tool-call.mjsThe command must exit non-zero and print BLOCKED by AG Kit.
Safe updates and rollback
AG Kit updates are merge-aware. User-owned files and locally modified managed files are preserved by default.
ag-kit update --dry-run # Preview the exact plan
ag-kit update # Merge safely and create a backup
ag-kit update --strategy replace # Explicit full replacement, still backed up
ag-kit rollback # Restore the newest pre-update backupUpdate metadata is stored in .agents/.ag-kit/. Backups are stored in .ag-kit-backups/ outside the managed toolkit tree. Read MIGRATION.md before upgrading an existing installation to the Antigravity-native release.
Antigravity-native integration
Runtime contract
.agents/antigravity.json declares the six supported integration phases and the documented Antigravity CLI capabilities used by AG Kit. It avoids inventing a minimum semantic version when upstream documentation does not define one.
Native safety hook
Antigravity loads .agents/hooks.json, which registers:
{
"enabled": true,
"PreToolUse": [
{
"matcher": "run_command",
"command": "node .agents/hooks/validate-tool-call.mjs",
"timeout": 10
}
]
}To temporarily disable the AG Kit hook while diagnosing a compatibility issue, set "enabled": false, reopen the workspace, and report the payload shape privately if it may contain sensitive data. Do not delete Antigravity's own permission controls.
MCP configuration
Review the workspace MCP plan without writing to the home directory:
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --printAfter replacing placeholders, explicitly apply to one supported target:
node .agents/hooks/sync-mcp.mjs --apply --target suite
node .agents/hooks/sync-mcp.mjs --apply --target cliExisting servers with the same name are preserved unless --force is supplied. A timestamped backup is created before an existing target file is changed. Never commit real MCP credentials.
Build and inspect the plugin
npm run build:antigravity-pluginReview dist/antigravity-plugin/ before local installation. The bundle contains packaged skills, agents, rules, converted workflow commands, the native hook, an MCP example, and PLUGIN_CONTENTS.json with SHA-256 entries.
agy plugin install ./dist/antigravity-plugin
agy plugin listPlugin installation is optional; the repository-native .agents/ workspace remains the source of truth for project development.
Included components
| Component | Count | Purpose |
|---|---|---|
| Agents | 20 | Domain specialist and orchestration role definitions |
| Skills | 47 | Progressive domain knowledge and executable validation helpers |
| Workflows | 13 | Repeatable slash-command procedures |
| Rules | 6 | Workspace-wide routing, safety, design, and coding constraints |
| Memory topics | 4 required topics plus index | Durable project conventions, decisions, preferences, and feedback |
Every agent, skill, workflow, and rule has a SemVer contract. .agents/manifest.json, .agents/manifest.lock.json, and .agents/DEPENDENCY_GRAPH.md make the managed toolkit reproducible and detect drift.
npm run generate:agents
npm run check:agentsCommon workflows
| Command | Purpose |
|---|---|
/brainstorm |
Explore options and architecture before implementation |
/coordinate |
Run separable research or review tasks in parallel, then synthesize |
/create |
Create a feature or application with structured gates |
/debug |
Perform evidence-based root-cause analysis |
/deploy |
Execute production pre-flight checks and deployment workflow |
/enhance |
Safely modify an existing codebase |
/orchestrate |
Plan, obtain approval, delegate to specialists, and verify |
/plan |
Create a detailed implementation plan and checklist |
/preview |
Manage local preview servers |
/remember |
Save durable project information to memory |
/status |
Summarize active work and blockers |
/test |
Design and execute tests |
/verify |
Prove changes by running checks instead of relying on inspection |
Release and production gates
A release candidate is not production-approved until all automated checks and the hands-on Antigravity smoke test in PRODUCTION_CHECKLIST.md are complete.
Required GitHub checks:
- Toolkit validation
- CLI tests and package validation
- Web lint, typecheck, build, and audit
- Antigravity native contract
- Dependency Review
AG Kit never requires automatic merge, automatic deployment, or automatic MCP synchronization. Production changes should remain reviewable and reversible.
Documentation
- Antigravity implementation details
- Migration guide
- Production release checklist
- Security policy and runtime threat model
- Agent flow architecture
- Toolkit architecture
- Changelog
- Release setup
References and attribution
AG Kit is an original open-source implementation of Markdown-based agent engineering patterns. No proprietary source files are included. Runtime integration decisions are based on public Antigravity documentation and codelabs linked in .agents/hooks/README.md.
Support the project
License
Released under the MIT License © Vudovn.
Overview (`.agents/README.md`)
AG Kit toolkit operator guide
AG Kit is a modular .agents/ toolkit for Google Antigravity. It routes software-engineering work to specialist roles, progressively loads focused skills, preserves durable project context, and verifies changes with executable checks.
Runtime contract
Antigravity is the primary production runtime. The machine-readable contract is .agents/antigravity.json and covers six phases:
- rules, skills, and workflow discovery;
- MCP configuration and explicit synchronization;
- native lifecycle hooks and command safety;
- agent/subagent orchestration;
- optional plugin packaging;
- validation and production smoke testing.
See hooks/README.md for the implementation and security boundaries.
Quick start
From the project root:
npm run check:agents
npm run check:antigravity
npm run test:antigravityOpen the repository as a trusted Antigravity workspace. The runtime should discover:
rules/*.mdas workspace constraints;skills/*/SKILL.mdas progressively loaded domain context;workflows/*.mdas slash commands;agent/*.mdas specialist role definitions;memory/as durable project context.
Use /coordinate for separable parallel research/review work and /orchestrate for plan approval followed by specialist implementation. Antigravity /agents and /tasks remain the runtime source of truth.
Native safety hook
.agents/hooks.json registers a PreToolUse gate for run_command. The policy blocks only high-confidence root/disk destructive patterns. It does not replace Antigravity permissions, workspace trust, sandboxing, or user approval.
Test with mocked stdin only:
printf '%s' '{"tool_args":{"CommandLine":"rm -rf /"}}' \
| node .agents/hooks/validate-tool-call.mjsThe process must exit non-zero. To diagnose a compatibility issue, set "enabled": false temporarily and reopen the workspace.
MCP setup
mcp_config.json is a workspace example. Replace YOUR_API_KEY before enabling the server and keep real credentials outside version control.
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --printNo home-directory file is changed without --apply. Existing server names are preserved unless --force is explicit, and an existing target is backed up before writing.
Plugin bundle
npm run build:antigravity-pluginReview dist/antigravity-plugin/ and its PLUGIN_CONTENTS.json inventory before optional local installation. The repository .agents/ directory remains the source of truth.
Core concepts
- Agents define role, boundaries, tools, and skill dependencies.
- Skills contain selectively loaded domain knowledge and optional executable scripts.
- Rules define workspace-wide precedence, safety, and routing behavior.
- Workflows provide reusable slash-command procedures.
- Memory stores durable project conventions, preferences, decisions, and feedback.
- Hooks supplement runtime permissions with narrow policy checks.
- Runtime scripts turn guidance into repeatable evidence.
- Manifest and lock make managed components and runtime tooling reproducible.
Validation
Validate a target project:
python .agents/scripts/checklist.py .Run full project verification when a preview URL exists:
python .agents/scripts/verify_all.py . --url http://localhost:3000Verify AG Kit itself after editing agents, skills, rules, workflows, memory, runtime tooling, schemas, scripts, or links:
npm run generate:agents
npm run check:agents
npm run check:antigravity
npm run test:antigravityDocumentation
- Architecture and inventory
- Antigravity integration
- Dependency graph
- Runtime scripts
- Root migration guide
- Production checklist
- Security policy
- Change history
- Quick routing reference
Overview (`cli/README.md`)
AG Kit CLI
CLI for installing and safely updating AG Kit, a collection of agents, skills, workflows, rules, memory conventions, and validation tools for Google Antigravity.
Installation
npx @vudovn/ag-kit initOr install globally:
npm install @vudovn/ag-kit
ag-kit initCommands
| Command | Description |
|---|---|
ag-kit init |
Install .agents; safely merges when an installation already exists |
ag-kit update |
Update managed files while preserving local changes |
ag-kit rollback |
Restore the newest or a selected pre-update backup |
ag-kit status |
Show installation, manifest, toolkit version, backups, and CLI status |
Safe update model
AG Kit records SHA-256 baselines in .agents/.ag-kit/manifest.json. During an update it compares the previous upstream version, the current local file, and the new upstream file.
- Clean managed files are updated automatically.
- Files changed only locally are preserved.
- User-created files are preserved.
- Files changed both locally and upstream are reported as conflicts.
- Incoming conflict copies are written under
.agents/.ag-kit/conflicts/. - A full pre-update backup is stored under
.ag-kit-backups/by default.
ag-kit update --dry-run
ag-kit update --strategy merge
ag-kit update --strategy replace
ag-kit rollback
ag-kit rollback --backup 20260712-090000-000merge is the default strategy. replace is intentionally explicit and still creates a backup unless --no-backup is supplied.
Common options
ag-kit init --path ./myapp
ag-kit init --branch dev
ag-kit update --force
ag-kit update --quiet --force
ag-kit update --conflict-report ./ag-kit-update.json
ag-kit rollback --dry-runWhen --quiet is used against an existing installation, --force is required because the CLI cannot safely ask for confirmation.
Included toolkit
- 20 specialist agents
- 47 skills
- 13 workflows
- Shared rules, persistent memory conventions, MCP configuration, and validation scripts
Exit codes
| Code | Meaning |
|---|---|
0 |
Success or no changes required |
1 |
Download, validation, filesystem, or configuration failure |
2 |
Update completed, but one or more conflicts require manual review |
130 |
Interrupted by the user |
License
MIT
Overview (`web/README.md`)
AG Kit - Web Application
⚡ Quick Start (Local Development)
The web/ directory contains the official online documentation site and interactive dashboard portal built using Next.js 16 and React 19.
Install dependencies:
bashnpm installRun local development server:
bashnpm run devOpen browser:
Navigate to http://localhost:3000 to view the documentation portal locally.
🏗️ Architecture & Stack
- Framework: Next.js 16 (App Router)
- Library: React 19
- Styling: Tailwind CSS v4
- MDX: @next/mdx for seamless markdown integration
- Components: Built with @base-ui/react and Lucide React icons
📦 What gets installed by the CLI
When downstream developers run npx @vudovn/ag-kit init, they install a .agents/ folder at their project root:
| Directory | Count | Description |
|---|---|---|
agent/ |
20 | Specialist AI agent configurations (Frontend, Backend, Security, PM, QA, etc.) |
skills/ |
45 | Domain-specific context modules with conditional loading rules |
workflows/ |
13 | Pre-configured interactive slash commands |
📚 Online Documentation
☕ Support the Project
If AG Kit has made your AI programming sessions more productive, consider supporting the project:
Vietnamese Bank (MBBank QR):
📄 License
Released under the MIT License © Vudovn.
Overview (`.agents/hooks/README.md`)
AG Kit — Antigravity Native Integration
AG Kit now treats Google Antigravity as its primary runtime. The integration is intentionally built from Antigravity's workspace-native conventions instead of a cross-runtime abstraction.
What is active
| Phase | Native surface | AG Kit implementation |
|---|---|---|
| 1. Discovery | .agents/rules/, .agents/skills/, .agents/workflows/ |
Doctor validates discovery paths and required frontmatter |
| 2. MCP | .agents/mcp_config.json |
Workspace validation plus explicit, backup-aware sync helper |
| 3. Hooks | .agents/hooks.json |
PreToolUse gate for clearly destructive run_command calls |
| 4. Orchestration | workflows, specialist definitions, Antigravity subagents | Validates /coordinate, /orchestrate, core roles, and routing skills |
| 5. Plugin | Antigravity CLI plugin import | Deterministic local plugin bundle builder |
| 6. Validation | CI and smoke tests | Doctor, hook regression tests, MCP tests, and plugin build tests |
Quick verification
node .agents/hooks/antigravity-doctor.mjs
node --test .agents/hooks/tests/antigravity.test.mjsThe doctor checks the installed workspace without changing files. Use --json for machine-readable output and --strict to treat unresolved configuration placeholders as failures.
Native safety hook
Antigravity reads .agents/hooks.json. AG Kit registers one native hook:
{
"enabled": true,
"PreToolUse": [
{
"matcher": "run_command",
"command": "node .agents/hooks/validate-tool-call.mjs",
"timeout": 10
}
]
}The policy blocks only high-confidence destructive operations such as deleting a filesystem root, formatting a drive, or overwriting a raw disk. It deliberately allows normal cleanup such as deleting dist/ or node_modules/.
The hook is not a sandbox and does not replace Antigravity's permission settings. Invalid or unknown payload shapes fail open with a warning to prevent a runtime-wide lockout after upstream payload changes.
MCP setup
Antigravity CLI supports workspace MCP configuration at .agents/mcp_config.json. Antigravity IDE and the wider suite may also use a shared global configuration.
Inspect the merge plan:
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --printApply only after replacing placeholders such as YOUR_API_KEY:
node .agents/hooks/sync-mcp.mjs --apply --target suite
node .agents/hooks/sync-mcp.mjs --apply --target cliThe helper never overwrites an existing server with the same name unless --force is supplied. It creates a timestamped backup before writing.
Orchestration
AG Kit uses the existing Antigravity-native workflows:
/coordinatefor parallel read/research and synthesis;/orchestratefor plan approval followed by specialist implementation;.agents/agent/*.mdas role definitions;coordinator-mode,parallel-agents,intelligent-routing, andverify-changesas orchestration skills.
Antigravity's /agents and /tasks views remain the runtime source of truth for active work. AG Kit does not create a second scheduler.
Build a plugin bundle
node .agents/hooks/build-plugin.mjs
# or
npm run build:antigravity-pluginThe generated dist/antigravity-plugin/ contains:
- a
gemini-extension.jsoncompatible manifest used by Antigravity CLI's plugin importer; - packaged skills and specialist definitions;
- workflows converted into namespaced command TOML files;
- rules, native hooks, and an MCP example;
PLUGIN_CONTENTS.jsonwith deterministic SHA-256 inventory data.
Install the local build after reviewing it:
agy plugin install ./dist/antigravity-plugin
agy plugin listSecurity boundaries
- No MCP configuration is copied to the home directory without explicit
--apply. - Placeholder credentials block MCP application.
- The plugin builder does not include secrets from environment variables or home-directory configuration.
- The hook only reads one tool payload from stdin and performs no network calls.
- AG Kit does not weaken Antigravity permission prompts or workspace trust controls.
Release and operations
- Root README — installation and production quick start.
- Migration guide — upgrade and rollback from earlier AG Kit versions.
- Production checklist — automated and hands-on release gates.
- Security policy — threat model, incident handling, and hook recovery.
Primary Antigravity references
- Workspace rules and workflows: https://codelabs.developers.google.com/antigravity-ide
- Workspace skills: https://codelabs.developers.google.com/antigravity-skills
- Workspace MCP: https://codelabs.developers.google.com/antigravity-cli
- Native
PreToolUsehooks: https://codelabs.developers.google.com/secure-agentic-coding - Plugin installation: https://codelabs.developers.google.com/antigravity-cli-plugins and https://codelabs.developers.google.com/antigravity-conductor
Overview (`.agents/scripts/README.md`)
AG Kit Runtime Scripts
Entry points
`validate_kit.py`
Self-validates the .agents/ package. It checks JSON, strict SemVer frontmatter, workflow/agent/skill references, manifest and lock synchronization, generated dependency docs, memory contracts, local Markdown links, Python syntax, referenced script paths, and documented inventory counts.
python .agents/scripts/validate_kit.py
python .agents/scripts/validate_kit.py --json`generate_manifest.py`
Builds deterministic manifest.json and manifest.lock.json files from component frontmatter. Use --check in CI to fail on registry drift.
python .agents/scripts/generate_manifest.py
python .agents/scripts/generate_manifest.py --check`dependency_graph.py`
Builds DEPENDENCY_GRAPH.md from workflow and agent dependencies. Use --check to verify that the generated graph is current.
python .agents/scripts/dependency_graph.py
python .agents/scripts/dependency_graph.py --check`checklist.py`
Runs the fast project validation path. URL checks are automatically skipped when --url is not supplied.
python .agents/scripts/checklist.py .
python .agents/scripts/checklist.py . --url http://localhost:3000
python .agents/scripts/checklist.py . --report .agents/reports/checklist.json`verify_all.py`
Runs the broad release suite. --no-runtime excludes Lighthouse and Playwright; --no-e2e excludes Playwright only.
python .agents/scripts/verify_all.py . --no-runtime
python .agents/scripts/verify_all.py . --url http://localhost:3000 --report verification.json`session_manager.py`
Prints project type, package metadata, feature hints, and file counts.
python .agents/scripts/session_manager.py status .`auto_preview.py`
Starts, stops, or inspects a detected local preview server.
python .agents/scripts/auto_preview.py start 3000
python .agents/scripts/auto_preview.py status
python .agents/scripts/auto_preview.py stopRuntime prerequisites
Most scripts use only the Python standard library. Optional checks require the corresponding project tools:
- Lighthouse:
npm install lighthouse - Playwright:
pip install playwright && playwright install chromium - Node lint/test commands: project package manager and configured scripts
- Python lint/test commands: project-configured tools such as Ruff, MyPy, or pytest
Missing URL-based tools produce a failed runtime check rather than a false pass. Missing non-applicable build outputs are reported as skipped/pass with an explanatory message.
Exit-code contract
0: check passed or was not applicable1: findings met the configured failure threshold2: invalid command usage or missing input path
The master runners use subprocess exit codes as the source of truth and can emit a full JSON report with commands, durations, stdout, stderr, and status.
Regression tests
Toolkit scripts include regression tests for self-validation, component SemVer, manifest/lock integrity, dependency graph synchronization, memory contracts, security scanning, dependency and bundle analysis, and toolkit-root discovery.
python -m unittest discover -s .agents/scripts/tests -vWeb Src App Docs Antigravity Content.En (`web/src/app/docs/antigravity/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, FeatureGrid, Feature } from '@/components/mdx'
Antigravity Runtime Integration
Google Antigravity is AG Kit's production runtime. Beyond rules, skills, and workflows, the kit ships a native integration layer inside .agents/.
The runtime layer
Tool safety hook
hooks.json registers a native PreToolUse gate for run_command. It is deliberately narrow — it blocks high-confidence destructive patterns only:
- Unix root-filesystem deletion (
rm -rf /and equivalents) - Filesystem formatting and raw-disk overwrite (
mkfs, writing to/dev/sdX) - Windows drive formatting and forced root deletion
Normal project cleanup (deleting dist/, node_modules/) passes through.
MCP synchronization
.agents/mcp_config.json is the workspace source for MCP servers. The sync helper applies it explicitly — it refuses placeholder credentials, preserves conflicting entries by default, and backs up the target before writing:
Antigravity Doctor
The Doctor checks discovery, MCP, hooks, orchestration, plugin packaging, and release readiness — read-only:
Plugin bundle
For teams who prefer a packaged install, the plugin builder produces a local Antigravity plugin bundle with a deterministic SHA-256 content inventory:
Web Src App Docs Antigravity Content.Vi (`web/src/app/docs/antigravity/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, FeatureGrid, Feature } from '@/components/mdx'
Tích hợp Runtime Antigravity
Google Antigravity là runtime production của AG Kit. Ngoài rules, skills và workflows, kit đi kèm lớp tích hợp native bên trong .agents/.
Lớp runtime
Hook an toàn công cụ
hooks.json đăng ký cổng PreToolUse native cho run_command. Nó cố tình hẹp — chỉ chặn các mẫu phá hủy có độ tin cậy cao:
- Xóa root filesystem Unix (
rm -rf /và tương đương) - Format filesystem và ghi đè raw-disk (
mkfs, ghi vào/dev/sdX) - Format ổ đĩa Windows và xóa root cưỡng bức
Dọn dẹp dự án bình thường (xóa dist/, node_modules/) vẫn đi qua bình thường.
Đồng bộ MCP
.agents/mcp_config.json là nguồn cấu hình MCP của workspace. Trình đồng bộ áp dụng nó một cách tường minh — từ chối credential giữ chỗ, giữ nguyên mục xung đột theo mặc định, và sao lưu đích trước khi ghi:
Antigravity Doctor
Doctor kiểm tra discovery, MCP, hooks, orchestration, đóng gói plugin và mức sẵn sàng phát hành — chỉ đọc:
Gói plugin
Với đội muốn cài dạng đóng gói, trình build plugin tạo bundle plugin Antigravity cục bộ với inventory nội dung SHA-256 xác định:
Web Src App Docs Updates Content.En (`web/src/app/docs/updates/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, FeatureGrid, Feature } from '@/components/mdx'
Managed Updates & Rollback
AG Kit installs .agents/ as a managed tree: every kit file is tracked in a manifest with SHA-256 hashes, so updates know exactly what is yours and what is the kit's.
How the managed tree works
Files you add or modify are not kit-managed, so the default merge strategy preserves them. Only files whose hash matches the manifest are updated in place.
Updating safely
Rolling back
- Defaults to the newest backup; pick one with
--backup. - The current tree is backed up before restoring (disable with
--no-keep-current). - Preview with
--dry-run.
Web Src App Docs Updates Content.Vi (`web/src/app/docs/updates/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, FeatureGrid, Feature } from '@/components/mdx'
Cập nhật được quản lý & Rollback
AG Kit cài .agents/ dưới dạng cây được quản lý: mọi file của kit được theo dõi trong manifest với hash SHA-256, nên khi cập nhật hệ thống biết chính xác file nào của bạn, file nào của kit.
Cây được quản lý hoạt động thế nào
File bạn thêm hoặc sửa không thuộc quản lý của kit, nên chiến lược mặc định merge sẽ giữ nguyên chúng. Chỉ những file có hash khớp manifest mới được cập nhật.
Cập nhật an toàn
Rollback
- Mặc định dùng bản sao lưu mới nhất; chọn bản khác với
--backup. - Cây hiện tại được sao lưu trước khi khôi phục (tắt bằng
--no-keep-current). - Xem trước với
--dry-run.
Web Src App Docs Guide Examples Brainstorm Content.En (`web/src/app/docs/guide/examples/brainstorm/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Structured Brainstorming
Explore multiple approaches before writing code with the /brainstorm workflow.
Overview
The /brainstorm command activates a structured ideation mode.
Instead of jumping straight to code, the agent explores at least 3 different approaches,
analyzes pros and cons, and helps you make an informed decision.
The Process
```bash
/brainstorm authentication system for my SaaS app
```Example Session
Option A: React Hook Form + Zod
✅ Minimal re-renders, great DX
❌ Learning curve
📊 Effort: Low
Option B: Zustand
✅ Full control, persists across routes
❌ More boilerplate
📊 Effort: MediumPro Tips
Next Steps
- Try
/brainstormfor your next architecture decision - After deciding, use Add New Feature to implement
Web Src App Docs Guide Examples Brainstorm Content.Ja (`web/src/app/docs/guide/examples/brainstorm/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
構造化ブレインストーミング
/brainstorm ワークフローで、コードを書く前に複数のアプローチを検討しましょう。
概要
/brainstorm コマンドは構造化されたアイデア出しモードを起動します。
いきなりコードに飛びつくのではなく、エージェントが少なくとも 3 種類の異なるアプローチを検討し、
それぞれの長所と短所を分析して、納得のいく意思決定を後押しします。
プロセス
```bash
/brainstorm authentication system for my SaaS app
```セッション例
選択肢 A: React Hook Form + Zod
✅ 再レンダリングが最小限、開発体験が優秀
❌ 学習コストがある
📊 工数: 低
選択肢 B: Zustand
✅ 完全に制御可能、ルート間で状態を保持
❌ ボイラープレートが増える
📊 工数: 中実践のヒント
次のステップ
- 次のアーキテクチャ判断で
/brainstormを試してみましょう - 決めたら、新機能の追加で実装しましょう
Web Src App Docs Guide Examples Brainstorm Content.Vi (`web/src/app/docs/guide/examples/brainstorm/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Động não có cấu trúc
Khám phá nhiều hướng tiếp cận trước khi viết code với quy trình /brainstorm.
Tổng quan
Lệnh /brainstorm kích hoạt một chế độ phát ý tưởng có cấu trúc.
Thay vì lao thẳng vào code, tác tử khám phá ít nhất 3 hướng tiếp cận khác nhau,
phân tích ưu nhược điểm và giúp bạn ra quyết định sáng suốt.
Quy trình
```bash
/brainstorm authentication system for my SaaS app
```Phiên làm việc ví dụ
Phương án A: React Hook Form + Zod
✅ Ít re-render, DX tuyệt vời
❌ Có đường cong học tập
📊 Công sức: Thấp
Phương án B: Zustand
✅ Toàn quyền kiểm soát, giữ trạng thái qua các route
❌ Nhiều code khuôn mẫu hơn
📊 Công sức: Trung bìnhMẹo hay
Bước tiếp theo
- Thử
/brainstormcho quyết định kiến trúc tiếp theo của bạn - Sau khi quyết định, dùng Thêm tính năng mới để triển khai
Web Src App Docs Guide Examples Brainstorm Content.Zh (`web/src/app/docs/guide/examples/brainstorm/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
结构化头脑风暴
使用 /brainstorm 工作流,在动手写代码之前先探索多种方案。
概述
/brainstorm 命令会启动一种结构化的构思模式。
与其直接动手写代码,智能体会探索至少 3 种不同的方案,
分析各自的优缺点,帮助你做出明智的决策。
流程
```bash
/brainstorm authentication system for my SaaS app
```示例会话
方案 A:React Hook Form + Zod
✅ 重渲染极少,开发体验出色
❌ 有一定学习曲线
📊 工作量:低
方案 B:Zustand
✅ 完全可控,跨路由保持状态
❌ 样板代码更多
📊 工作量:中实用技巧
后续步骤
- 在你的下一个架构决策中试试
/brainstorm - 决定之后,用添加新功能来实现
Web Src App Docs Guide Examples Create Content.En (`web/src/app/docs/guide/examples/create/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, StatusList, StatusItem } from '@/components/mdx'
Create New Application
Build complete applications from scratch with the /create wizard.
Overview
The /create command is your application creation wizard.
It guides you through an interactive dialogue, understands your requirements,
plans the architecture, and orchestrates specialist agents to build your app.
The Process
```bash
/create e-commerce site with product listing and cart
```Example Session
Pro Tips
Next Steps
- Run
/createfollowed by your app idea - Use Add New Feature to extend
Web Src App Docs Guide Examples Create Content.Ja (`web/src/app/docs/guide/examples/create/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, StatusList, StatusItem } from '@/components/mdx'
新しいアプリの作成
/create ウィザードで、完全なアプリケーションをゼロから構築しましょう。
概要
/create コマンドはあなたのアプリケーション作成ウィザードです。
対話形式のやり取りを通じて案内し、要件を理解し、
アーキテクチャを計画して、各専門エージェントを編成しアプリを構築します。
プロセス
```bash
/create e-commerce site with product listing and cart
```セッション例
実践のヒント
次のステップ
/createの後にアプリのアイデアを続けて実行しましょう- 新機能の追加で拡張しましょう
Web Src App Docs Guide Examples Create Content.Vi (`web/src/app/docs/guide/examples/create/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, StatusList, StatusItem } from '@/components/mdx'
Tạo ứng dụng mới
Xây dựng ứng dụng hoàn chỉnh từ đầu với trình hướng dẫn /create.
Tổng quan
Lệnh /create là trình hướng dẫn tạo ứng dụng của bạn.
Nó dẫn dắt bạn qua một cuộc hội thoại tương tác, hiểu yêu cầu của bạn,
lập kế hoạch kiến trúc và điều phối các tác tử chuyên biệt để dựng ứng dụng.
Quy trình
```bash
/create e-commerce site with product listing and cart
```Phiên làm việc ví dụ
Mẹo hay
Bước tiếp theo
- Chạy
/createkèm theo ý tưởng ứng dụng của bạn - Dùng Thêm tính năng mới để mở rộng
Web Src App Docs Guide Examples Create Content.Zh (`web/src/app/docs/guide/examples/create/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, StatusList, StatusItem } from '@/components/mdx'
创建新应用
使用 /create 向导从零构建完整的应用。
概述
/create 命令是你的应用创建向导。
它会通过一段交互式对话引导你,理解你的需求,
规划架构,并编排各个专家智能体来构建你的应用。
流程
```bash
/create e-commerce site with product listing and cart
```示例会话
实用技巧
后续步骤
- 运行
/create并附上你的应用想法 - 用添加新功能来扩展
Web Src App Docs Guide Examples Debugging Content.En (`web/src/app/docs/guide/examples/debugging/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Systematic Debugging
Solve complex issues using the rigorous /debug workflow.
Overview
The /debug workflow enforces a 4-phase investigation protocol (Discovery, Hypothesis, Verification, Resolution). It prevents guess-driven development by requiring evidence before code changes.
The Process
```bash
/debug Login returns 403 even with correct credentials
```Example Session
1. `emailRef.current` is null on mount
2. Event handler not bound correctlyPro Tips
Next Steps
- Try
/debugon an existing bug - See Deployment to ship your fix
Web Src App Docs Guide Examples Debugging Content.Ja (`web/src/app/docs/guide/examples/debugging/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
体系的なデバッグ
厳密な /debug ワークフローで、複雑な問題を解決しましょう。
概要
/debug ワークフローは4 段階の調査プロトコル(発見、仮説、検証、解決)を徹底させます。コードを変更する前に証拠を求めることで、当て推量に頼った開発を防ぎます。
プロセス
```bash
/debug Login returns 403 even with correct credentials
```セッション例
1. `emailRef.current` が mount 時に null
2. イベントハンドラが正しくバインドされていない実践のヒント
次のステップ
- 既存のバグで
/debugを試してみましょう - 修正を出荷するにはデプロイを参照しましょう
Web Src App Docs Guide Examples Debugging Content.Vi (`web/src/app/docs/guide/examples/debugging/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Gỡ lỗi có hệ thống
Giải quyết các vấn đề phức tạp với quy trình /debug chặt chẽ.
Tổng quan
Quy trình /debug áp dụng một giao thức điều tra 4 giai đoạn (Khám phá, Giả thuyết, Kiểm chứng, Khắc phục). Nó ngăn lối phát triển dựa trên phỏng đoán bằng cách yêu cầu có bằng chứng trước khi thay đổi code.
Quy trình
```bash
/debug Login returns 403 even with correct credentials
```Phiên làm việc ví dụ
1. `emailRef.current` là null khi mount
2. Trình xử lý sự kiện chưa được gắn đúngMẹo hay
Bước tiếp theo
- Thử
/debugvới một lỗi có sẵn - Xem Triển khai để phát hành bản sửa của bạn
Web Src App Docs Guide Examples Debugging Content.Zh (`web/src/app/docs/guide/examples/debugging/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
系统化调试
使用严谨的 /debug 工作流解决复杂问题。
概述
/debug 工作流强制执行一套四阶段调查协议(发现、假设、验证、解决)。它要求在改动代码之前先拿出证据,从而避免靠猜测驱动的开发。
流程
```bash
/debug Login returns 403 even with correct credentials
```示例会话
1. `emailRef.current` 在 mount 时为 null
2. 事件处理器绑定不正确实用技巧
后续步骤
- 在一个现有的 bug 上试试
/debug - 查看部署以发布你的修复
Web Src App Docs Guide Examples Deployment Content.En (`web/src/app/docs/guide/examples/deployment/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Production Deployment
Ship with confidence using the safety-first /deploy workflow.
Overview
The /deploy command is an Audit & Release Conductor.
It forces your code to pass a rigorous health check before deployment.
The Process
```bash
/deploy
```<h4 className="text-sm font-semibold mb-1">🛡️ Security</h4>
Scans for vulnerabilities & secrets
<h4 className="text-sm font-semibold mb-1">📋 Quality</h4>
Enforces Linting & Type SafetyExample Session
🔄 Security Scan... PASSED
🔄 Lint Check... PASSED
🔄 Type Validation... PASSED
✅ All checks passed!
Deploying to Vercel...🌐 URL: https://my-app.vercel.app
💚 Health Check: OKPro Tips
Next Steps
- Try
/deploy checkto run pre-flight checks - Learn about Multi-Agent Orchestration
Web Src App Docs Guide Examples Deployment Content.Ja (`web/src/app/docs/guide/examples/deployment/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
本番環境へのデプロイ
安全第一の /deploy ワークフローで、自信を持ってリリースしましょう。
概要
/deploy コマンドは監査とリリースの指揮官です。
デプロイ前に、コードへ厳格なヘルスチェックを強制的に通過させます。
プロセス
```bash
/deploy
```<h4 className="text-sm font-semibold mb-1">🛡️ セキュリティ</h4>
脆弱性とシークレットをスキャン
<h4 className="text-sm font-semibold mb-1">📋 品質</h4>
Linting と型安全性を強制セッション例
🔄 セキュリティスキャン…… PASSED
🔄 Lint チェック…… PASSED
🔄 型の検証…… PASSED
✅ すべてのチェックを通過しました!
Vercel へデプロイ中……🌐 URL: https://my-app.vercel.app
💚 ヘルスチェック: OK実践のヒント
次のステップ
/deploy checkを試して出発前チェックを実行しましょう- マルチエージェントのオーケストレーションについて学びましょう
Web Src App Docs Guide Examples Deployment Content.Vi (`web/src/app/docs/guide/examples/deployment/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Triển khai production
Phát hành tự tin với quy trình /deploy đặt an toàn lên hàng đầu.
Tổng quan
Lệnh /deploy là một Nhạc trưởng Kiểm toán & Phát hành.
Nó buộc code của bạn phải vượt qua một kiểm tra sức khỏe nghiêm ngặt trước khi triển khai.
Quy trình
```bash
/deploy
```<h4 className="text-sm font-semibold mb-1">🛡️ Bảo mật</h4>
Quét lỗ hổng & secret
<h4 className="text-sm font-semibold mb-1">📋 Chất lượng</h4>
Áp dụng Linting & An toàn kiểuPhiên làm việc ví dụ
🔄 Quét bảo mật... PASSED
🔄 Kiểm tra Lint... PASSED
🔄 Xác thực kiểu... PASSED
✅ Tất cả kiểm tra đã qua!
Đang triển khai lên Vercel...🌐 URL: https://my-app.vercel.app
💚 Kiểm tra sức khỏe: OKMẹo hay
Bước tiếp theo
- Thử
/deploy checkđể chạy các kiểm tra trước khi bay - Tìm hiểu về Điều phối đa tác tử
Web Src App Docs Guide Examples Deployment Content.Zh (`web/src/app/docs/guide/examples/deployment/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
生产环境部署
使用安全优先的 /deploy 工作流,从容发布。
概述
/deploy 命令是一位审计与发布指挥官。
它会强制你的代码在部署前通过一轮严格的健康检查。
流程
```bash
/deploy
```<h4 className="text-sm font-semibold mb-1">🛡️ 安全</h4>
扫描漏洞与密钥
<h4 className="text-sm font-semibold mb-1">📋 质量</h4>
强制 Linting 与类型安全示例会话
🔄 安全扫描…… PASSED
🔄 Lint 检查…… PASSED
🔄 类型校验…… PASSED
✅ 所有检查均已通过!
正在部署到 Vercel……🌐 URL: https://my-app.vercel.app
💚 健康检查: OK实用技巧
后续步骤
- 试试
/deploy check来运行起飞前检查 - 了解多智能体编排
Web Src App Docs Guide Examples New Feature Content.En (`web/src/app/docs/guide/examples/new-feature/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
Add a New Feature
Learn how to safely add complex features to an existing codebase using the /enhance workflow.
Overview
The /enhance workflow is your day-to-day tool for iterative development.
Unlike /create which builds from scratch, /enhance focuses on surgically adding functionality without breaking existing code.
The Process
```bash
/enhance Add an analytics dashboard for user activity
Requirements:
- Track daily active users and page views
- Visual charts using Recharts
- API endpoint to aggregate data
```<FeatureGrid cols={4}>
<Feature title="Database" />
<Feature title="Backend" />
<Feature title="Frontend" />
<Feature title="Testing" />
</FeatureGrid>Example Session
Found: Tailwind CSS with no dark mode config
Plan: Update tailwind.config, add ThemeProvider, create toggle componentPro Tips
Next Steps
- Try
/enhancein your project - See Test Generation for coverage
Web Src App Docs Guide Examples New Feature Content.Ja (`web/src/app/docs/guide/examples/new-feature/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
新機能の追加
/enhance ワークフローで、既存のコードベースに複雑な機能を安全に追加する方法を学びましょう。
概要
/enhance ワークフローは、日々の反復開発に使うツールです。
ゼロから構築する /create とは違い、/enhance は既存コードを壊さずに、外科手術のように機能を追加することに集中します。
プロセス
```bash
/enhance Add an analytics dashboard for user activity
Requirements:
- Track daily active users and page views
- Visual charts using Recharts
- API endpoint to aggregate data
```<FeatureGrid cols={4}>
<Feature title="Database" />
<Feature title="Backend" />
<Feature title="Frontend" />
<Feature title="Testing" />
</FeatureGrid>セッション例
発見:Tailwind CSS に dark mode の設定がありません
計画:tailwind.config を更新し、ThemeProvider を追加し、toggle コンポーネントを作成実践のヒント
次のステップ
- あなたのプロジェクトで
/enhanceを試してみましょう - カバレッジについてはテスト生成を参照しましょう
Web Src App Docs Guide Examples New Feature Content.Vi (`web/src/app/docs/guide/examples/new-feature/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
Thêm tính năng mới
Tìm hiểu cách thêm các tính năng phức tạp vào codebase có sẵn một cách an toàn với quy trình /enhance.
Tổng quan
Quy trình /enhance là công cụ hằng ngày cho việc phát triển lặp.
Khác với /create (dựng từ đầu), /enhance tập trung thêm chức năng một cách phẫu thuật mà không phá vỡ code hiện có.
Quy trình
```bash
/enhance Add an analytics dashboard for user activity
Requirements:
- Track daily active users and page views
- Visual charts using Recharts
- API endpoint to aggregate data
```<FeatureGrid cols={4}>
<Feature title="Database" />
<Feature title="Backend" />
<Feature title="Frontend" />
<Feature title="Testing" />
</FeatureGrid>Phiên làm việc ví dụ
Phát hiện: Tailwind CSS chưa cấu hình dark mode
Kế hoạch: Cập nhật tailwind.config, thêm ThemeProvider, tạo component toggleMẹo hay
Bước tiếp theo
- Thử
/enhancetrong dự án của bạn - Xem Sinh kiểm thử để biết về độ phủ
Web Src App Docs Guide Examples New Feature Content.Zh (`web/src/app/docs/guide/examples/new-feature/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
添加新功能
学习如何使用 /enhance 工作流,安全地为现有代码库添加复杂功能。
概述
/enhance 工作流是你日常迭代开发的工具。
与从零构建的 /create 不同,/enhance 专注于像做手术一样精准地添加功能,而不破坏现有代码。
流程
```bash
/enhance Add an analytics dashboard for user activity
Requirements:
- Track daily active users and page views
- Visual charts using Recharts
- API endpoint to aggregate data
```<FeatureGrid cols={4}>
<Feature title="Database" />
<Feature title="Backend" />
<Feature title="Frontend" />
<Feature title="Testing" />
</FeatureGrid>示例会话
发现:Tailwind CSS 尚未配置 dark mode
计划:更新 tailwind.config,添加 ThemeProvider,创建 toggle 组件实用技巧
后续步骤
- 在你的项目中试试
/enhance - 查看测试生成以了解覆盖率
Web Src App Docs Guide Examples Orchestration Content.En (`web/src/app/docs/guide/examples/orchestration/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
Multi-Agent Orchestration
Build entire SaaS platforms by coordinating specialist agents with the /orchestrate workflow.
Overview
Most AI interactions are 1-on-1. The orchestrator agent changes this by acting as a Project Manager.
It breaks down a large request (e.g., "Build a SaaS MVP") into tasks and assigns them to the best specialist for the job.
The Process
```bash
/orchestrate Build a "Course Platform" MVP with:
- User Authentication (NextAuth)
- Stripe Payments
- Video Hosting (Mux)
- Dashboard for Instructors
```...
### 2.1 Database Schema
- Users (id, email, role)
- Courses (id, title, price)
...Example Session
Pro Tips
Next Steps
- Learn about Systematic Debugging to maintain your complex app
- See Deployment to ship your MVP
Web Src App Docs Guide Examples Orchestration Content.Ja (`web/src/app/docs/guide/examples/orchestration/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
マルチエージェントのオーケストレーション
/orchestrate ワークフローで専門エージェントを連携させ、SaaS プラットフォーム全体を構築しましょう。
概要
ほとんどの AI とのやり取りは 1 対 1 です。orchestrator エージェントはプロジェクトマネージャーとして振る舞うことで、これを変えます。
大きなリクエスト(例:「SaaS の MVP を作る」)をタスクに分解し、その仕事に最適な専門家へ割り当てます。
プロセス
```bash
/orchestrate Build a "Course Platform" MVP with:
- User Authentication (NextAuth)
- Stripe Payments
- Video Hosting (Mux)
- Dashboard for Instructors
```...
### 2.1 Database Schema
- Users (id, email, role)
- Courses (id, title, price)
...セッション例
実践のヒント
次のステップ
Web Src App Docs Guide Examples Orchestration Content.Vi (`web/src/app/docs/guide/examples/orchestration/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
Điều phối đa tác tử
Xây dựng cả nền tảng SaaS bằng cách điều phối các tác tử chuyên biệt với quy trình /orchestrate.
Tổng quan
Hầu hết tương tác với AI đều là 1-đối-1. Tác tử orchestrator thay đổi điều này bằng cách đóng vai trò Quản lý dự án.
Nó phân rã một yêu cầu lớn (ví dụ "Xây dựng SaaS MVP") thành các tác vụ và giao cho chuyên gia phù hợp nhất với từng việc.
Quy trình
```bash
/orchestrate Build a "Course Platform" MVP with:
- User Authentication (NextAuth)
- Stripe Payments
- Video Hosting (Mux)
- Dashboard for Instructors
```...
### 2.1 Database Schema
- Users (id, email, role)
- Courses (id, title, price)
...Phiên làm việc ví dụ
Mẹo hay
Bước tiếp theo
- Tìm hiểu Gỡ lỗi có hệ thống để duy trì ứng dụng phức tạp
- Xem Triển khai để phát hành MVP của bạn
Web Src App Docs Guide Examples Orchestration Content.Zh (`web/src/app/docs/guide/examples/orchestration/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature, StatusList, StatusItem } from '@/components/mdx'
多智能体编排
使用 /orchestrate 工作流,通过协调多个专家智能体来构建整个 SaaS 平台。
概述
大多数 AI 交互都是一对一的。orchestrator 智能体改变了这一点,它扮演项目经理的角色。
它会把一个庞大的需求(例如"构建一个 SaaS MVP")拆解成多个任务,并分派给最擅长该任务的专家。
流程
```bash
/orchestrate Build a "Course Platform" MVP with:
- User Authentication (NextAuth)
- Stripe Payments
- Video Hosting (Mux)
- Dashboard for Instructors
```...
### 2.1 Database Schema
- Users (id, email, role)
- Courses (id, title, price)
...示例会话
实用技巧
后续步骤
Web Src App Docs Guide Examples Plan Content.En (`web/src/app/docs/guide/examples/plan/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Project Planning
Create detailed implementation plans before writing code with the /plan workflow.
Overview
The /plan command activates planning-only mode.
It uses the project-planner agent to create a detailed plan file without writing any code.
The Process
```bash
/plan e-commerce site with cart and checkout
```Example Session
1. What metrics? (users, revenue?)
2. Real-time or daily?
3. Charting library?
Pro Tips
Next Steps
- Run
/planfor your next major feature - After planning, use Create Application to implement
Web Src App Docs Guide Examples Plan Content.Ja (`web/src/app/docs/guide/examples/plan/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
プロジェクトの計画
/plan ワークフローで、コードを書く前に詳細な実装計画を作成しましょう。
概要
/plan コマンドは計画専用モードを起動します。project-planner エージェントを使い、コードを一切書かずに詳細な計画ファイルを作成します。
プロセス
```bash
/plan e-commerce site with cart and checkout
```セッション例
1. どの指標が必要ですか?(ユーザー、収益?)
2. リアルタイムですか、それとも日次ですか?
3. チャートライブラリは?
実践のヒント
次のステップ
- 次の大きな機能で
/planを実行しましょう - 計画の後は、アプリの作成で実装しましょう
Web Src App Docs Guide Examples Plan Content.Vi (`web/src/app/docs/guide/examples/plan/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
Lập kế hoạch dự án
Tạo các kế hoạch triển khai chi tiết trước khi viết code với quy trình /plan.
Tổng quan
Lệnh /plan kích hoạt chế độ chỉ lập kế hoạch.
Nó dùng tác tử project-planner để tạo một file kế hoạch chi tiết mà không viết bất kỳ dòng code nào.
Quy trình
```bash
/plan e-commerce site with cart and checkout
```Phiên làm việc ví dụ
1. Các chỉ số nào? (người dùng, doanh thu?)
2. Thời gian thực hay theo ngày?
3. Thư viện biểu đồ?
Mẹo hay
Bước tiếp theo
- Chạy
/plancho tính năng lớn tiếp theo của bạn - Sau khi lập kế hoạch, dùng Tạo ứng dụng để triển khai
Web Src App Docs Guide Examples Plan Content.Zh (`web/src/app/docs/guide/examples/plan/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
项目规划
使用 /plan 工作流,在写代码之前先制定详细的实现计划。
概述
/plan 命令会启动仅规划模式。
它使用 project-planner 智能体创建一份详细的计划文件,而不写任何代码。
流程
```bash
/plan e-commerce site with cart and checkout
```示例会话
1. 需要哪些指标?(用户、收入?)
2. 实时还是按天?
3. 用哪个图表库?
实用技巧
后续步骤
- 为你下一个重要功能运行
/plan - 规划之后,用创建应用来实现
Web Src App Docs Guide Examples Preview Content.En (`web/src/app/docs/guide/examples/preview/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Preview Management
Manage your local development server with the /preview workflow.
Overview
The /preview command manages your local development server.
Start, stop, restart, or check the status with simple commands.
The Process
Example Session
Port: 3000
Type: Next.jsPro Tips
Next Steps
- Run
/preview startto launch your dev server - See Deployment to go live
Web Src App Docs Guide Examples Preview Content.Ja (`web/src/app/docs/guide/examples/preview/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
プレビューの管理
/preview ワークフローで、ローカル開発サーバーを管理しましょう。
概要
/preview コマンドはローカル開発サーバーを管理します。
シンプルなコマンドで、起動、停止、再起動、状態の確認ができます。
プロセス
セッション例
ポート: 3000
タイプ: Next.js実践のヒント
次のステップ
/preview startを実行して開発サーバーを起動しましょう- 公開するにはデプロイを参照しましょう
Web Src App Docs Guide Examples Preview Content.Vi (`web/src/app/docs/guide/examples/preview/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Quản lý preview
Quản lý máy chủ phát triển cục bộ của bạn với quy trình /preview.
Tổng quan
Lệnh /preview quản lý máy chủ phát triển cục bộ của bạn.
Khởi động, dừng, khởi động lại hoặc kiểm tra trạng thái bằng các lệnh đơn giản.
Quy trình
Phiên làm việc ví dụ
Cổng: 3000
Loại: Next.jsMẹo hay
Bước tiếp theo
- Chạy
/preview startđể khởi động máy chủ phát triển của bạn - Xem Triển khai để đưa lên môi trường thật
Web Src App Docs Guide Examples Preview Content.Zh (`web/src/app/docs/guide/examples/preview/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
预览管理
使用 /preview 工作流管理你的本地开发服务器。
概述
/preview 命令负责管理你的本地开发服务器。
用简单的命令即可启动、停止、重启或查看状态。
流程
示例会话
端口: 3000
类型: Next.js实用技巧
后续步骤
- 运行
/preview start来启动你的开发服务器 - 查看部署以上线
Web Src App Docs Guide Examples Status Content.En (`web/src/app/docs/guide/examples/status/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Project Status
Get a complete overview of your project with the /status workflow.
Overview
The /status command gives you a complete dashboard view of your project.
See project info, tech stack, completed features, agent activity, and preview status.
The Process
```bash
/status
```Example Session
📁 Project: my-ecommerce
🏷️ Type: nextjs-ecommerce
📄 Files: 73 created, 12 modified
=== Agent Status ===
✅ database-architect → Completed
✅ backend-specialist → Completed
🔄 frontend-specialist → 60%
=== Preview ===
🌐 URL: http://localhost:3000
💚 Health: OKPro Tips
Next Steps
- Run
/statusto check project state - See Deployment when ready to ship
Web Src App Docs Guide Examples Status Content.Ja (`web/src/app/docs/guide/examples/status/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
プロジェクトの状態
/status ワークフローで、プロジェクトの全体像を把握しましょう。
概要
/status コマンドは、プロジェクトの完全なダッシュボードビューを提供します。
プロジェクト情報、技術スタック、完了した機能、エージェントの活動、プレビューの状態を確認できます。
プロセス
```bash
/status
```セッション例
📁 プロジェクト: my-ecommerce
🏷️ タイプ: nextjs-ecommerce
📄 ファイル: 73 件作成、12 件変更
=== Agent Status ===
✅ database-architect → 完了
✅ backend-specialist → 完了
🔄 frontend-specialist → 60%
=== Preview ===
🌐 URL: http://localhost:3000
💚 健康状態: OK実践のヒント
次のステップ
/statusを実行してプロジェクトの状態を確認しましょう- 出荷の準備ができたらデプロイを参照しましょう
Web Src App Docs Guide Examples Status Content.Vi (`web/src/app/docs/guide/examples/status/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Trạng thái dự án
Có cái nhìn tổng quan đầy đủ về dự án của bạn với quy trình /status.
Tổng quan
Lệnh /status cho bạn một góc nhìn dashboard đầy đủ về dự án.
Xem thông tin dự án, tech stack, các tính năng đã xong, hoạt động của tác tử và trạng thái preview.
Quy trình
```bash
/status
```Phiên làm việc ví dụ
📁 Dự án: my-ecommerce
🏷️ Loại: nextjs-ecommerce
📄 Tệp tin: 73 đã tạo, 12 đã sửa
=== Agent Status ===
✅ database-architect → Hoàn tất
✅ backend-specialist → Hoàn tất
🔄 frontend-specialist → 60%
=== Preview ===
🌐 URL: http://localhost:3000
💚 Sức khỏe: OKMẹo hay
Bước tiếp theo
- Chạy
/statusđể kiểm tra trạng thái dự án - Xem Triển khai khi sẵn sàng phát hành
Web Src App Docs Guide Examples Status Content.Zh (`web/src/app/docs/guide/examples/status/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
项目状态
使用 /status 工作流,全面掌握你项目的整体情况。
概述
/status 命令为你提供项目的完整仪表盘视图。
查看项目信息、技术栈、已完成的功能、智能体活动以及预览状态。
流程
```bash
/status
```示例会话
📁 项目: my-ecommerce
🏷️ 类型: nextjs-ecommerce
📄 文件: 已创建 73 个,已修改 12 个
=== Agent Status ===
✅ database-architect → 已完成
✅ backend-specialist → 已完成
🔄 frontend-specialist → 60%
=== Preview ===
🌐 URL: http://localhost:3000
💚 健康状况: OK实用技巧
后续步骤
- 运行
/status来查看项目状态 - 准备好发布时,查看部署
Web Src App Docs Guide Examples Test Content.En (`web/src/app/docs/guide/examples/test/content.en.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Test Generation & Execution
Generate and run tests with the /test workflow.
Overview
The /test command handles test generation and execution.
Analyze code, create test suites, run tests, or check coverage.
The Process
Example Session
Found 4 functions: login, register, verifyToken, resetPasswordCreated: `tests/auth.test.ts`
Test cases: 12
Coverage: 95%Pro Tips
Next Steps
- Run
/testto execute your test suite - See Deployment which runs tests automatically
Web Src App Docs Guide Examples Test Content.Ja (`web/src/app/docs/guide/examples/test/content.ja.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
テストの生成と実行
/test ワークフローで、テストを生成して実行しましょう。
概要
/test コマンドはテストの生成と実行を担います。
コードを分析し、テストスイートを作成し、テストを実行したり、カバレッジを確認したりします。
プロセス
セッション例
4 つの関数を発見:login、register、verifyToken、resetPassword作成: `tests/auth.test.ts`
テストケース: 12
カバレッジ: 95%実践のヒント
次のステップ
/testを実行してテストスイートを動かしましょう- テストを自動で実行するデプロイを参照しましょう
Web Src App Docs Guide Examples Test Content.Vi (`web/src/app/docs/guide/examples/test/content.vi.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
Sinh và chạy kiểm thử
Sinh và chạy test với quy trình /test.
Tổng quan
Lệnh /test lo việc sinh và chạy kiểm thử.
Phân tích code, tạo bộ test, chạy test hoặc kiểm tra độ phủ.
Quy trình
Phiên làm việc ví dụ
Tìm thấy 4 hàm: login, register, verifyToken, resetPasswordĐã tạo: `tests/auth.test.ts`
Số ca kiểm thử: 12
Độ phủ: 95%Mẹo hay
Bước tiếp theo
- Chạy
/testđể thực thi bộ kiểm thử của bạn - Xem Triển khai vốn tự động chạy test
Web Src App Docs Guide Examples Test Content.Zh (`web/src/app/docs/guide/examples/test/content.zh.mdx`)
import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
测试生成与执行
使用 /test 工作流生成并运行测试。
概述
/test 命令负责测试的生成与执行。
分析代码、创建测试套件、运行测试或检查覆盖率。
流程
示例会话
找到 4 个函数:login、register、verifyToken、resetPassword已创建: `tests/auth.test.ts`
测试用例: 12
覆盖率: 95%实用技巧
后续步骤
- 运行
/test来执行你的测试套件 - 查看部署,它会自动运行测试
--- METRICS ---
- Files Extracted: 50
- Estimated Token Budget: ~32462 tokens
- Canonical Reference: https://codewiki.google/github.com/vudovn/antigravity-kit