boundary conditions and error states
5. **User experience** - Accessibility, performance, and usability considerations
6. **Documentation** - Add comments for complex logic, but prefer self-documenting code
---
Most formatting and common issues
11k51d agoReviewMountCreate a free account to mount
user's own working
directory and deliverables land there — never in this repo.
Deep documentation already lives in [`docs/`](docs/) — read it before large changes and keep it in
sync
Steady3 mentions in 2 weeks
No other project uses it yet
11k3mo agoReviewMountCreate a free account to mount
Documentation instructions
## TypeScript documentation
- Make all TypeScript documentation changes under `docs/typescript/`.
- Add new TypeScript pages to the v2 TypeScript navigation in `docs/docs.json`.
- Update existing v2 TypeScript pages instead of their
Steady9 mentions in 2 weeks
No other project uses it yet
11k10d agoReviewMountCreate a free account to mount
PixelRAG
Visual RAG: render documents (web pages, PDFs) as screenshot tiles and retrieve over the images
with a Qwen3-VL embedding model. See `README.md` for the product overview and `deploy/README.md
No other project uses it yet
11k19d agoReviewMountCreate a free account to mount
development builds due to private API keys
- Code signing configured through SharedXcodeSettings for development
- Documentation and technical notes are located in the `Technotes/` folder
## Code Formatting
Prefer idiomatic modern Swift
11k25d agoReviewMountCreate a free account to mount
style, `var` usage, single-change PRs, English-only code, license, and the rest — are documented in [`CONTRIBUTING.md`](CONTRIBUTING.md). Follow those first.
Project-specific additions:
- Do not write comments within
10k5mo agoReviewMountCreate a free account to mount
cache entries; it does not delete build outputs.
## Running Tests
See `tests/README.md` for full documentation. Quick reference:
```bash
# Full test suite (use after builds to verify correctness)
CTEST_PARALLEL_LEVEL
10k2mo agoReviewMountCreate a free account to mount
scope and local validation, follow [Local validation](AGENTS.md#local-validation), including the presentation-document allowlist and the full product-content gate.
## Candidate and publication controls
Follow [the release workflow manual
10k4d agoReviewMountCreate a free account to mount
scope and local validation, follow [Local validation](AGENTS.md#local-validation), including the presentation-document allowlist and the full product-content gate.
## Candidate and publication controls
Follow [the release workflow manual
10k4d agoReviewMountCreate a free account to mount
specific tests with `#if NET8_0_OR_GREATER`
- Test results: `test-results/ / .trx`
## Documentation
Docusaurus 3 site in `docs/`. Dev server: `cd docs && pnpm start`. See [DOCUMENTATION.md](DOCUMENTATION.md) for full
Steady4 mentions in 2 weeks
No other project uses it yet
9.8k3y agoReviewMountCreate a free account to mount
addresses_are_incorrect`, not `invalid_email_addresses_message`.
> For complete style rules (imports, formatting, documentation, Compose conventions), see `docs/STYLE_AND_BEST_PRACTICES.md`.
---
## Anti-Patterns
In addition to the Key Principles above, follow these
9.6k7mo 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.