reward.py` is the single source of truth for scoring:
```bash
uv run reward.py # Self-test
```
See `SCORING.md` for the full rubric.
## Experiments
Experimental training configurations live in `experiments/`:
```
experiments/
├── lfm2
2 projects use a version of this
30k3mo agoReviewMountCreate a free account to mount
Vultr, Hetzner, local deployment
### Philosophy
- Stability over features
- Security over convenience
- Clarity over cleverness
- Test everything
- Stay in scope - solve exactly what the issue asks, nothing more
- Test assumptions
No other project uses it yet
30k11mo agoReviewMountCreate a free account to mount
Build production bundles
- `make clean` - Clean build directory
- `make all` - Full build (compile + deploy)
### Testing
- `npm test` - Run full test suite using WebDriverIO
- `npm run test-single -- ` - Run single test
No other project uses it yet
30k3mo agoReviewMountCreate a free account to mount
indexes. This keeps field-access coupling and batched / non-batched handling in one tested place.
* Batching based on batched / non-batched should be avoided. Deal with it at argument-level
30k3mo agoReviewMountCreate a free account to mount
indexes. This keeps field-access coupling and batched / non-batched handling in one tested place.
* Batching based on batched / non-batched should be avoided. Deal with it at argument-level
1 project uses a version of this
30k3mo agoReviewMountCreate a free account to mount
just that one). `apps/sim`'s tsconfig excludes `*.test.ts(x)`, so `type-check` skips its tests; CI's `test-types` job ratchets their errors per file and TS code instead (`check
30k13d agoReviewMountCreate a free account to mount
make multiple commits so that the changes are easier to review.
4. Run appropriate tests and validation
5. If the tests, are not passing, please fix the issues and continue
No other project uses it yet
29k27d agoReviewMountCreate a free account to mount
Node**: `.nvmrc` is `24.16.0`; `engines.node` in root `package.json` is `>=24.16.0`; CI runs the unit-test matrix on Node `22.x` and `24.x` and every other job off `.nvmrc`.
- **Monorepo
No other project uses it yet
29k5mo agoReviewMountCreate a free account to mount
case that
cannot occur is dead code that still has to be read, tested and reasoned about. This applies to db
columns, API payloads, stored settings and config keys alike
29k2d agoReviewMountCreate a free account to mount
styles for injected elements
├── dist/ # Built extension files (generated)
├── promo/ # Store promotional materials
└── tests/ # Test files
```
## Development Commands
```bash
npm run dev chrome # Development mode for Chrome
npm run build
Steady4 mentions in 2 weeks
No other project uses it yet
29k3mo agoReviewMountCreate a free account to mount
coverage expansion** — public audit record `audit/productivity-2026-07/` (all 7 legacy skills scored, 24/24 scripts smoke-tested, coverage map vs the personal-productivity canon) + 3 gap-filling plugins, each with
29k6mo agoReviewMountCreate a free account to mount
preferred equity, hard money / bridge funds, and private credit, pasted from any source. Stress-tests returns against public benchmarks plus an illiquidity premium, converts the fee stack to gross
Steady17 mentions in 2 weeks
No other project uses it yet
29k6mo 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.