task (they're usually listed in an "Implementation Files" section)
- **Check core/tests/** for integration tests that validate the feature (for core tasks)
- **Check packages/interface/src/** for interface implementations (for interface tasks
No other project uses it yet
39k25d agoReviewMountCreate a free account to mount
Build and test
The MCP server source lives in `microsoft/playwright`, in `packages/playwright-core/src/tools/`.
This repo ships `@playwright/mcp`: `cli.js` and `index.js` run the server from the `playwright-core`
alpha that `package.json` pins
39k2d agoReviewMountCreate a free account to mount
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
No other project uses it yet
38k3d 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
No other project uses it yet
38k3d 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
35k59d 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
35k5mo agoReviewMountCreate a free account to mount
instead of `String`. Note that `&str` is better than `Cow ` here.
## Testing
- Write unit tests for your code.
- Prefer fixture tests over inline (`#[test]`) tests.
- You can do `UPDATE
No other project uses it yet
34k39d 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
34k45d 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
34k21d agoReviewMountCreate a free account to mount
I/O-bound work (network calls, API queries). **Keep concurrency 1** for CPU-bound (npm test, build, lint) or commands sharing state (ports, lock files, same-repo writes).
GitHub API rate-limit
Steady5 mentions in 2 weeks
1 project uses a version of this
33k5mo agoReviewMountCreate a free account to mount
delegated to the Node CLI.
## Essential Commands
```bash
# Development
npm install # Install dependencies
npm test # Run tests
npm version X.Y.Z --ignore-scripts=false # Sync, commit, and tag all package versions
33k4mo 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.