Decision**:
- ✅ If baseline is clear → **STOP! No handler needed.**
- ❌ If baseline is confusing → Document specific issues, proceed to handler
4. **Document Justification**:
- What specific diagram problem does the handler solve
size for, and snapping its ladder would collapse the prose/code gap its own comment documents. The console is the web half of the same rule: `rem`, never
sandbox/AGENTS.md`.
- `packaging`: macOS, Linux, and Windows packaging and deployment assets.
- `docs`: the published documentation site (docs.asymptotelabs.ai).
Do not recreate or depend on removed `asymptote` mirror trees. Keep new work
anything it describes (service responsibilities, ports, protocols, data stores, flows, deployment topology), update the document in the same change.
## Common Development Commands
### Setup & Environment
```bash
# Switch between environments (prod, staging
consumers pinned by commit SHA.
**How we write** — [`writing-with-ai.md`](.claude/rules/writing-with-ai.md): internal vs external-facing documents, why a model cannot make its own output stop reading as model output
Always use context7 when I need code generation, setup or configuration steps, or library/API documentation. This means you should automatically use the Context7 MCP tools to resolve library
pipx run` - while every variant
keeps identical tool names and one set of documentation. Change `plugin.json`'s name
and you rename its tools with it.
The skills-only entry
user-facing terms instead.
- Do not describe the underlying protocol implementation in docs. Only document the SDK surface (methods, types, options). ACP protocol details belong exclusively in ACP-specific pages
specific shells such as session selection, session headers, and control-plane actions in `frontend/packages/inspector/`.
- Document all shared React components in `docs/react-components.mdx`, and keep that page aligned with the exported surface
just test`, `just format` complete successfully.
### Comments
- Comments MUST only be used to:
1. Document a function
2. Explain the WHY of a piece of code
3. Explain a particularly
pytest tests/test_foo.py`, restart + check Z).
Communication only — doesn't replace automated tests.
## Post-Commit Documentation Sync (MANDATORY — DO NOT SKIP)
> After EVERY `git commit`, run the checklist below BEFORE responding
helpers
├── .opencode/commands/ # OpenCode /minutes-* slash-command wrappers
└── tests/integration/ # Integration tests (including real whisper tests)
```
## Documentation Structure
Documentation is organized under `docs/` by purpose. See [docs/README.md](docs/README.md) for the index.
- `docs/architecture
from every `README*.md` and `docs/getting-started.md` **and** add the name to each of those documents' ` = …` enumeration (the `<平台> = …` line in the zh translations). That enumeration must list every `PLATFORMS` entry
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.