built MCP server
bun setup # Full setup (install + write .cursor/mcp.json + .mcp.json)
```
There is no test suite or linter configured.
## Architecture
### MCP Server (`src/talk_to_figma_mcp/server.ts`)
The main server implementing the MCP protocol
install dependencies
npm run build # compile with tsup
npm run dev # watch mode
npm test # run vitest
npm run typecheck # type checking
npm run lint # eslint
npm run format # prettier
Install dependencies
poetry run uvicorn airweave.main:app --host 0.0.0.0 --port 8001 --reload # Dev server
# Tests
poetry run pytest tests/unit # Unit tests only
poetry run pytest tests/integration # Integration tests
poetry
trace changed or reused helper contracts, including error and sentinel returns, through callers, consumers, tests, and operational configuration.
- Verify standard quality commands include every changed path and exercise exact entry
notebook.google.com) via both a Model Context Protocol server and a comprehensive command-line interface.
Tested with personal/free tier accounts. May work with Google Workspace accounts but has not been tested
required to merge — reproduce them locally first:
```bash
uv run ruff format src/ tests/ && uv run ruff check src/ tests/ --fix
uv run mypy src/ouroboros
uv run pytest
```
(`Ruff Lint
code quality. The architecture emphasizes robust error handling, user-friendly interfaces, and extensive testing coverage with advanced tool integration including CCR proxy, Cometix status line, and CCusage analytics. Version
Tests Module
**Last Updated**: Mon Oct 27 19:39:26 CST 2025
[Root](../CLAUDE.md) > **tests**
## Module Responsibilities
Test suite module providing comprehensive test coverage for the ZCF project, including unit
plumbing, `jian-core` event types + taffy layout, `jian-scene` canonical render scene — `LayoutScene` + hit-test + path geometry, consumed by OP and any jian app); `vendor/casement` is the winit fork; `vendor/agent
ships its own wasm under `wasm/`.
- Build: `tsup` (`bun run build` inside the package). Tests: `vitest`.
## op-web-sdk-react (`op-web-sdk-react/`)
React 19 adapter
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.