required selected evaluations,
then run the full free suite once on the final integrated code. During repairs,
focused checks replace a full-suite run before every commit.
`bun run test
primitives.
4. **SEE IT — Playwright / Chrome DevTools MCP.** You are not done when the code compiles.
Open the page in a real browser, screenshot it, read the console, exercise interactive
commit message: commit messages,
PR titles and bodies, PR and issue comments, review comments, and code comments. There is no
scope in which the footer is permitted — if you find
server `.python-version` file)
- Type checking: **pyright** (enforced in CI)
- Linting: **ruff**
## Code Style
### TypeScript
- ES modules with `.js` extension in import paths
- Strict TypeScript typing for all functions
individual hooks in `hooks-config.json`.
## Answering Best Practice Questions
When the user asks a Claude Code best practice question, **always search this repo first** (`best-practice/`, `reports/`, `tips/`, `implementation/`, and `README.md
Hiring**: Add 10 engineers to accelerate product development
2. **Product**: Launch AI codereview feature by end of Q2
3. **Sales**: Expand into European market
4. **Fundraising**: Begin Series
formatting and notebook structure.
## Slash Commands
These commands are available in Claude Code and CI:
- `/notebook-review` - Review notebook quality
- `/model-check` - Validate Claude model references
- `/link-review` - Check links in changed files
patches.
## GitHub
### Pull Requests
Use the `gh-create-pr` skill. Fallback: read `.agents/skills/gh-create-pr/SKILL.md` directly.
### CodeReview
When reviewing a GitHub PR, do NOT run `pnpm lint` / `pnpm test` / `pnpm format
Academic Research Skills
A suite of Claude Code skills for rigorous academic research, paper writing, peer review, and pipeline orchestration.
## Skills Overview
| Skill | Purpose | Key Modes |
|-------|---------|-----------|
| `deep-research` v2.12.1
AGENTS.md` as loaded. Claude Code does not reliably inline that import.
Before any planning, coding, reviewing, or answering a project question, you MUST call the Read tool on the repo
state the change actually carries. Describe the code
as it stands: do not narrate what earlier commits tried or what a review round changed. Naming the
merged pull request that
Important:** When mentioning agentic coding or AI tooling in CVs/cover letters, explicitly reference **Claude Code** by name.
## Verification Checklist
After creating or updating a CV or cover letter, re-read
code (ruff check, mypy)
./scripts/validate.sh
```
Both scripts must pass with no errors before codereview.
**PR Title Format:**
PR titles must follow one of these formats:
- `type: description` — e.g., `feat
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.