General Guidelines for working with Nx
- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many
Steady3 mentions in 2 weeks
No other project uses it yet
39k17d agoReviewMountCreate a free account to mount
single-source symlink mechanism, and the preflight/value-test checklist). Read it before touching any integration, test, fixture, or frontend under `showcase
Steady3 mentions in 2 weeks
No other project uses it yet
39k17d agoReviewMountCreate a free account to mount
multiple packages. Lerna uses Nx as the task runner and monorepo manager for building, testing, and managing the various Lerna commands and core functionality.
## Package Manager
This project uses
No other project uses it yet
36k3y agoReviewMountCreate a free account to mount
published crate
`qdrant-edge` is assembled from these sources by `publish/amalgamate.py`.
## Build, lint, test
- Format: `cargo +nightly fmt --all` (needs nightly).
- Lint: `cargo clippy --workspace --all-targets -- -D warnings`. When
No other project uses it yet
35k2mo agoReviewMountCreate a free account to mount
build # or: make build
# Watch mode for development
yarn watch # or: make watch
# Run tests
yarn test # Unit tests (Jest) for all packages, then type-checks src + tests
yarn test
Steady3 mentions in 2 weeks
No other project uses it yet
35k5mo agoReviewMountCreate a free account to mount
Checked production build in ./build
yarn generate # Regenerate level + locale manifests (also pre-hooked)
```
### Testing & Linting
```bash
yarn test # Run Jasmine test suite
yarn test:coverage # Run tests with
No other project uses it yet
34k17d agoReviewMountCreate a free account to mount
YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
## 4. Goal-Driven Execution
No other project uses it yet
34k35d agoReviewMountCreate a free account to mount
Rust port of the install core) is **in the backlog**: do not plan, change, test parity with or mention it unless Daniel resumes it.
## Essential Commands
```bash
# Development
npm install
34k14d agoReviewMountCreate a free account to mount
Vite, bridge bundle, `verify:dist`
- `cd web-panel; pnpm exec vitest run ` - one web test
- `build.cmd -EnableUpdateNotifications` - the opt-in update-check variant
## Rules
`.claude/rules/` holds the working rules. Claude
1 project uses a version of this
33k14d agoReviewMountCreate a free account to mount
code (REQUIRED before commits)
cargo make fmt
# Run clippy lints
cargo make ci-clippy
```
## Testing Conventions
Language tests, upgrade tests, and benchmarks: `language-tests/CLAUDE.md`.
Parser tests: `surrealdb/parser-next/CLAUDE.md`.
### Keep
Steady2 mentions in 2 weeks
No other project uses it yet
33k4mo agoReviewMountCreate a free account to mount
CLAUDE.md
Conventions for the SurrealQL test suite in `language-tests/`.
## Commands
```bash
# Run language tests
cd language-tests && cargo run run
# Run specific language test
# Note: all paths are relative
No other project uses it yet
33k4mo agoReviewMountCreate a free account to mount
designed for zero false positives through real-world condition simulation.
## Development Commands
### Building and Testing
- `make build` - Build the main nuclei binary to ./bin/nuclei
- `make test` - Run unit tests with
No other project uses it yet
33k11mo agoReviewMountCreate a free account to mount
Claude Code Configuration
> **Note:** Every command you need — building, running, testing, linting,
> formatting — is defined as a recipe in the project `justfile`. Run
> `just --list` to see them
No other project uses it yet
33k18mo agoReviewMountCreate a free account to mount
import sorting + formatting)
make format
# Lint code (ruff + pyright type checking)
make lint
# Run tests
make test
# Run all checks (format, lint, test)
make check
```
### Server Development (run from server
No other project uses it yet
33k55d agoReviewMountCreate a free account to mount
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.