## File: README.md

<h1 align="center">AG KIT</h1>







---

## 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

```bash
npx @vudovn/ag-kit init
```

Or install the CLI globally:

```bash
npm install @vudovn/ag-kit
ag-kit init
```

Do 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

```bash
npm run check:agents
npm run check:antigravity
npm run test:antigravity
```

`check: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:

```bash
node .agents/hooks/antigravity-doctor.mjs --strict
```

### Open in Antigravity

After opening the repository as a trusted workspace:

1. Confirm slash commands such as `/plan`, `/coordinate`, and `/orchestrate` are discovered.
2. Confirm relevant skills are selected from `.agents/skills/`.
3. Run a normal command such as `npm test` and confirm it is allowed.
4. Verify the safety hook with a mocked payload rather than executing a destructive command:

```bash
printf '%s' '{"tool_args":{"CommandLine":"rm -rf /"}}' \
  | node .agents/hooks/validate-tool-call.mjs
```

The 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.

```bash
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 backup
```

Update metadata is stored in `.agents/.ag-kit/`. Backups are stored in `.ag-kit-backups/` outside the managed toolkit tree. Read [MIGRATION.md](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:

```json
{
  "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:

```bash
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --print
```

After replacing placeholders, explicitly apply to one supported target:

```bash
node .agents/hooks/sync-mcp.mjs --apply --target suite
node .agents/hooks/sync-mcp.mjs --apply --target cli
```

Existing 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

```bash
npm run build:antigravity-plugin
```

Review `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.

```bash
agy plugin install ./dist/antigravity-plugin
agy plugin list
```

Plugin 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.

```bash
npm run generate:agents
npm run check:agents
```

## Common 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](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](.agents/hooks/README.md)
- [Migration guide](MIGRATION.md)
- [Production release checklist](PRODUCTION_CHECKLIST.md)
- [Security policy and runtime threat model](SECURITY.md)
- [Agent flow architecture](AGENT_FLOW.md)
- [Toolkit architecture](.agents/ARCHITECTURE.md)
- [Changelog](CHANGELOG.md)
- [Release setup](.github/RELEASE_SETUP.md)

## 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](.agents/hooks/README.md).

## Support the project









## License

Released under the [MIT License](LICENSE) © [Vudovn](https://github.com/vudovn).

---

## File: .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

```bash
node .agents/hooks/antigravity-doctor.mjs
node --test .agents/hooks/tests/antigravity.test.mjs
```

The 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:

```json
{
  "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:

```bash
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --print
```

Apply only after replacing placeholders such as `YOUR_API_KEY`:

```bash
node .agents/hooks/sync-mcp.mjs --apply --target suite
node .agents/hooks/sync-mcp.mjs --apply --target cli
```

The 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:

- `/coordinate` for parallel read/research and synthesis;
- `/orchestrate` for plan approval followed by specialist implementation;
- `.agents/agent/*.md` as role definitions;
- `coordinator-mode`, `parallel-agents`, `intelligent-routing`, and `verify-changes` as 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

```bash
node .agents/hooks/build-plugin.mjs
# or
npm run build:antigravity-plugin
```

The generated `dist/antigravity-plugin/` contains:

- a `gemini-extension.json` compatible 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.json` with deterministic SHA-256 inventory data.

Install the local build after reviewing it:

```bash
agy plugin install ./dist/antigravity-plugin
agy plugin list
```

## Security 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](../../README.md) — installation and production quick start.
- [Migration guide](../../MIGRATION.md) — upgrade and rollback from earlier AG Kit versions.
- [Production checklist](../../PRODUCTION_CHECKLIST.md) — automated and hands-on release gates.
- [Security policy](../../SECURITY.md) — 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 `PreToolUse` hooks: <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>

---

## File: .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.

```bash
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.

```bash
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.

```bash
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.

```bash
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.

```bash
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.

```bash
python .agents/scripts/session_manager.py status .
```

### `auto_preview.py`

Starts, stops, or inspects a detected local preview server.

```bash
python .agents/scripts/auto_preview.py start 3000
python .agents/scripts/auto_preview.py status
python .agents/scripts/auto_preview.py stop
```

## Runtime 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 applicable
- `1`: findings met the configured failure threshold
- `2`: 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.

```bash
python -m unittest discover -s .agents/scripts/tests -v
```

---

## File: .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:

1. rules, skills, and workflow discovery;
2. MCP configuration and explicit synchronization;
3. native lifecycle hooks and command safety;
4. agent/subagent orchestration;
5. optional plugin packaging;
6. validation and production smoke testing.

See [hooks/README.md](hooks/README.md) for the implementation and security boundaries.

## Quick start

From the project root:

```bash
npm run check:agents
npm run check:antigravity
npm run test:antigravity
```

Open the repository as a trusted Antigravity workspace. The runtime should discover:

- `rules/*.md` as workspace constraints;
- `skills/*/SKILL.md` as progressively loaded domain context;
- `workflows/*.md` as slash commands;
- `agent/*.md` as 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:

```bash
printf '%s' '{"tool_args":{"CommandLine":"rm -rf /"}}' \
  | node .agents/hooks/validate-tool-call.mjs
```

The 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.

```bash
node .agents/hooks/sync-mcp.mjs --check
node .agents/hooks/sync-mcp.mjs --print
```

No 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

```bash
npm run build:antigravity-plugin
```

Review `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:

```bash
python .agents/scripts/checklist.py .
```

Run full project verification when a preview URL exists:

```bash
python .agents/scripts/verify_all.py . --url http://localhost:3000
```

Verify AG Kit itself after editing agents, skills, rules, workflows, memory, runtime tooling, schemas, scripts, or links:

```bash
npm run generate:agents
npm run check:agents
npm run check:antigravity
npm run test:antigravity
```

## Documentation

- [Architecture and inventory](ARCHITECTURE.md)
- [Antigravity integration](hooks/README.md)
- [Dependency graph](DEPENDENCY_GRAPH.md)
- [Runtime scripts](scripts/README.md)
- [Root migration guide](../MIGRATION.md)
- [Production checklist](../PRODUCTION_CHECKLIST.md)
- [Security policy](../SECURITY.md)
- [Change history](../CHANGELOG.md)
- [Quick routing reference](rules/quick-reference.md)

---

## File: cli/README.md

# AG Kit CLI

CLI for installing and safely updating [AG Kit](https://github.com/vudovn/ag-kit), a collection of agents, skills, workflows, rules, memory conventions, and validation tools for Google Antigravity.

## Installation

```bash
npx @vudovn/ag-kit init
```

Or install globally:

```bash
npm install @vudovn/ag-kit
ag-kit init
```

## Commands

| 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.

```bash
ag-kit update --dry-run
ag-kit update --strategy merge
ag-kit update --strategy replace
ag-kit rollback
ag-kit rollback --backup 20260712-090000-000
```

`merge` is the default strategy. `replace` is intentionally explicit and still creates a backup unless `--no-backup` is supplied.

## Common options

```bash
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-run
```

When `--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

---

## File: 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.

<FeatureGrid>
  <Feature title="Project" description="Info & Stack" />
  <Feature title="Agents" description="Status Board" />
  <Feature title="Files" description="Statistics" />
  <Feature title="Preview" description="Health Check" />
</FeatureGrid>

## The Process

<StepList>
  <Step number={1} title="Run Command">
    Simply run the command to see your project dashboard.

    ```bash
    /status
    ```
  </Step>
</StepList>

## Example Session

<Terminal>
  <TerminalLine type="user">/status</TerminalLine>

  <TerminalBlock>
    === Project Status ===
    
      📁 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: OK
    
  </TerminalBlock>
</Terminal>

## Pro Tips


  <Tip title="Before Deploy">
    Check status to ensure all agents completed.
  </Tip>
  <Tip title="Track Progress">
    Monitor multi-agent orchestration in real-time.
  </Tip>


## Next Steps

- Run `/status` to check project state
- See [Deployment](/docs/guide/examples/deployment) when ready to ship

---

## File: 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` コマンドは、プロジェクトの**完全なダッシュボードビュー**を提供します。
プロジェクト情報、技術スタック、完了した機能、エージェントの活動、プレビューの状態を確認できます。

<FeatureGrid>
  <Feature title="プロジェクト" description="情報とスタック" />
  <Feature title="エージェント" description="ステータスボード" />
  <Feature title="ファイル" description="統計" />
  <Feature title="プレビュー" description="ヘルスチェック" />
</FeatureGrid>

## プロセス

<StepList>
  <Step number={1} title="コマンドを実行する">
    コマンドを実行するだけで、プロジェクトのダッシュボードが表示されます。

    ```bash
    /status
    ```
  </Step>
</StepList>

## セッション例

<Terminal>
  <TerminalLine type="user">/status</TerminalLine>

  <TerminalBlock>
    === Project Status ===
    
      📁 プロジェクト: my-ecommerce
      🏷️ タイプ: nextjs-ecommerce
      📄 ファイル: 73 件作成、12 件変更
    

    === Agent Status ===
    
      ✅ database-architect → 完了
      ✅ backend-specialist → 完了
      🔄 frontend-specialist → 60%
    

    === Preview ===
    
      🌐 URL: http://localhost:3000
      💚 健康状態: OK
    
  </TerminalBlock>
</Terminal>

## 実践のヒント


  <Tip title="デプロイ前に">
    状態を確認し、すべてのエージェントが完了したことを確かめましょう。
  </Tip>
  <Tip title="進捗を追う">
    マルチエージェントのオーケストレーションをリアルタイムで監視しましょう。
  </Tip>


## 次のステップ

- `/status` を実行してプロジェクトの状態を確認しましょう
- 出荷の準備ができたら[デプロイ](/docs/guide/examples/deployment)を参照しましょう

---

## File: 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.

<FeatureGrid>
  <Feature title="Dự án" description="Thông tin & Stack" />
  <Feature title="Tác tử" description="Bảng trạng thái" />
  <Feature title="Tệp tin" description="Thống kê" />
  <Feature title="Preview" description="Kiểm tra sức khỏe" />
</FeatureGrid>

## Quy trình

<StepList>
  <Step number={1} title="Chạy lệnh">
    Chỉ cần chạy lệnh để xem dashboard dự án của bạn.

    ```bash
    /status
    ```
  </Step>
</StepList>

## Phiên làm việc ví dụ

<Terminal>
  <TerminalLine type="user">/status</TerminalLine>

  <TerminalBlock>
    === Project Status ===
    
      📁 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: OK
    
  </TerminalBlock>
</Terminal>

## Mẹo hay


  <Tip title="Trước khi triển khai">
    Kiểm tra trạng thái để chắc chắn mọi tác tử đã hoàn tất.
  </Tip>
  <Tip title="Theo dõi tiến độ">
    Giám sát điều phối đa tác tử theo thời gian thực.
  </Tip>


## Bước tiếp theo

- Chạy `/status` để kiểm tra trạng thái dự án
- Xem [Triển khai](/docs/guide/examples/deployment) khi sẵn sàng phát hành

---

## File: 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` 命令为你提供项目的**完整仪表盘视图**。
查看项目信息、技术栈、已完成的功能、智能体活动以及预览状态。

<FeatureGrid>
  <Feature title="项目" description="信息与技术栈" />
  <Feature title="智能体" description="状态面板" />
  <Feature title="文件" description="统计数据" />
  <Feature title="预览" description="健康检查" />
</FeatureGrid>

## 流程

<StepList>
  <Step number={1} title="运行命令">
    只需运行命令即可查看你的项目仪表盘。

    ```bash
    /status
    ```
  </Step>
</StepList>

## 示例会话

<Terminal>
  <TerminalLine type="user">/status</TerminalLine>

  <TerminalBlock>
    === Project Status ===
    
      📁 项目: my-ecommerce
      🏷️ 类型: nextjs-ecommerce
      📄 文件: 已创建 73 个，已修改 12 个
    

    === Agent Status ===
    
      ✅ database-architect → 已完成
      ✅ backend-specialist → 已完成
      🔄 frontend-specialist → 60%
    

    === Preview ===
    
      🌐 URL: http://localhost:3000
      💚 健康状况: OK
    
  </TerminalBlock>
</Terminal>

## 实用技巧


  <Tip title="部署前">
    查看状态，确保所有智能体都已完成。
  </Tip>
  <Tip title="跟踪进度">
    实时监控多智能体编排。
  </Tip>


## 后续步骤

- 运行 `/status` 来查看项目状态
- 准备好发布时，查看[部署](/docs/guide/examples/deployment)

---

## File: 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.

<FeatureGrid>
  <Feature title="start" description="Launch server" />
  <Feature title="stop" description="Kill server" />
  <Feature title="restart" description="Reload" />
  <Feature title="check" description="Health" />
</FeatureGrid>

## The Process

<StepList>
  <Step number={1} title="Start Server">
    ```bash
    /preview start
    ```
  </Step>
  <Step number={2} title="Check Status">
    ```bash
    /preview
    ```
  </Step>
  <Step number={3} title="Stop Server">
    ```bash
    /preview stop
    ```
  </Step>
</StepList>

## Example Session

<Terminal>
  <TerminalLine type="user">/preview start</TerminalLine>

  <TerminalBlock>
    <TerminalLine type="agent">**🚀 Starting preview...**</TerminalLine>
    
      Port: 3000
      Type: Next.js
    
  </TerminalBlock>

  <TerminalBlock highlight>
    <TerminalLine type="agent">**✅ Preview ready!**</TerminalLine>
    URL: http://localhost:3000
  </TerminalBlock>
</Terminal>

## Pro Tips


  <Tip title="Auto-detection">
    Automatically detects Next.js, Vite, etc.
  </Tip>
  <Tip title="Port Conflict">
    Suggests alternatives if port 3000 is busy.
  </Tip>


## Next Steps

- Run `/preview start` to launch your dev server
- See [Deployment](/docs/guide/examples/deployment) to go live