// Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.
| name | rt-claw-docs-sync |
| description | Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization. |
| license | MIT |
Keep documentation accurate and bilingual where the repository already has English and Chinese pairs.
| Path | Purpose |
|---|---|
README.md | English project overview |
README_zh.md | Chinese project overview |
docs/en/ | English developer and user documentation |
docs/zh/ | Chinese counterpart documentation |
CLAUDE.md | Command-level agent reference |
AGENTS.md | Shared agent instruction source |
.agents/ | Agent-agnostic development skills |
Common scopes:
readme: README.md and README_zh.md.arch: architecture docs and diagrams.usage: build, run, flash, and shell usage guides.api: API references and header documentation.agent: AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instructions, and
.agents/.Makefile, meson_options.txt, and
current scripts.claw/services/* -> architecture, usage, and service docs may need updates.claw/services/tools/* -> Tool Use and usage docs may need updates.include/* -> API references may need updates.osal/* -> architecture and porting docs may need updates.platform/* -> getting-started, usage, and platform docs may need updates.Makefile, meson_options.txt, or scripts/* -> build and usage docs may
need updates..agents/*, AGENTS.md, or tool-specific instruction files -> agent
guidance needs updates.Use when adding CI coverage for a new rt-claw module, feature chain, endpoint backend, service integration, or regression.
Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.
Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations.
Use when analyzing rt-claw build logs, QEMU output, serial monitor logs, CI failures, network/API failures, or boot/runtime crashes.
Use when adding a new rt-claw service, driver, tool, platform helper, platform port, or RTOS backend.
Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks.