product boundaries, evidence and capability manifests,
safety policy, maturity, ecosystem decisions, and release gates.
- `tests/` and `evals/`: deterministic and model-facing verification.
## Development
- Keep skill entrypoints concise and use progressive
typecheck`
- Format code: `bun run format`
- Check formatting: `bun run format:check`
- Run tests: `bun test`
- Install dependencies: `bun install`
### Action Testing
- Test action locally: `./test-local.sh`
- Test specific file
CLAUDE.md
## Commands
```bash
bun test # Run tests
bun run typecheck # TypeScript type checking
bun run format # Format with prettier
bun run format:check # Check formatting
```
## What This Is
A GitHub
guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Build / Test / Format
The project is built via `make`, not directly with `swift build`. Two Swift packages
unix)]`-only code in the main crate — all features must work on all platforms
- Tests in `crates/*/tests/` should be cross-platform; use helper functions for
OS-specific APIs like
Verify every message against CPython with
the `/python-playground` skill before pinning it in a test.
## Always use `#[derive(FromArgs)]` for function parameters
Any function beyond the trivial 0/1/2-positional shapes (covered
into dependency issues, stop and ask.
```bash
# Full check (ruff + mypy + unit tests)
uv run --no-sync dev.py check
# Unit tests only (--no-sync avoids uv panic in sandboxed environments
format (uses ruff via pre-commit)
pre-commit run --all-files
# Run CPU tests
python -m pytest tests/ -m "not gpu" -v --timeout=300
# Run GPU tests
python -m pytest
references `feature.md §4` for shared aspects.
- **`documents/ai/guides/bug-fix.md`** — Use when fixing a reported bug, failing test, traceback, or behaviour that contradicts a stated contract. Defines the four mandatory phases (Reproduce → Diagnose
compatibility
- External validators with rewards system
## Pre-requisites
- [Kurtosis](https://docs.kurtosis.com/install): For launching test networks
- [Bun](https://bun.sh/) v1.2+: TypeScript runtime and package manager
- [Docker](https://www.docker.com
each topic are in `docs/`; targets are in `targets/` (canary is the
fast smoke test). The rest of this file is the pipeline operator guide.
---
# vuln-pipeline
Execution-verified vulnerability
prop on FlashList. Do not use it, suggest it, or add it.
## Build & Test
```bash
yarn build # compile TypeScript to dist/
yarn test --forceExit
yarn type-check
yarn lint
```
**Important
skipped.
```
[TYPE][Function/FileName][Short Description]
```
- `TYPE` in capitals: for example `FEAT`, `FIX`, `DOCS`, `REFACTOR`, `TEST`, `CHORE`.
- `Function/FileName`: the function, class, module or file the change is about.
- `Short Description
OpenAI-compatible default (Path A)
- `starter_anthropic.py` = Anthropic SDK version (Path B)
- `test.py` = mock-based tests for the Ollama starter (OpenAI-compat response shape)
- `test_anthropic.py` = mock-based tests for the Anthropic
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.