patches.
- Update docs alongside code; do not alter build targets without discussion.
- Use repository scripts (pnpm) and keep formatting consistent with existing files.
- Always review the root `CLAUDE.md` before beginning
source of truth for public loops.
The current Git tree holds application code and the content-free site shell.
Do not commit published loop records, bootstrap data, generated loop pages
once` in new C++ header files instead of macro-based `#ifndef`/`#define` include guards.
## CodeReview
- For pull request or diff review tasks, read and follow `.agents/skills/code-review/SKILL.md`.
## Test Placement
- Prefer
Validation is done through:
- Build verification in CI
- Manual testing of sample applications
- Documentation review
## Code Style and Conventions
### Formatting
```bash
# Format code before committing (REQUIRED)
dotnet format
# Verify formatting
guidance to Codex (Codex.ai/code) when working with code in this repository.
## What this repository is
A standalone agent skill for reviewing and improving interface polish, published for installation
secrets, `.env` files, private URLs, personal/customer data, or real production data; use fake placeholders. Review `git status` and the staged diff before committing, and never force-add ignored files
AGENTS.md
Instructions for AI coding agents working with this codebase.
## Monorepo Structure
This is a **Turborepo** monorepo with pnpm workspaces:
- `packages/opensrc/` — Rust CLI distributed via npm
- `apps/docs/` — Next.js documentation site
multiple focused commits inside the same goal PR when useful. Planning docs,
tests, implementation, code-review fixes, CI fixes, and small follow-up docs
belong in the same PR when
open that PR in the same task and link it from the code PR.
- If the host cannot run subagents, read `docs/AGENTS.md` in the primary task, complete the documentation work
Unit tests
- Integration tests
- End-to-end tests
### Code Formatting
- Always ensure that the code is formatted correctly by running prettier before committing changes.
### Branches and Pull Requests
- Unless specifically
Unit tests
- Integration tests
- End-to-end tests
### Code Formatting
- Always ensure that the code is formatted correctly by running prettier before committing changes.
### Branches and Pull Requests
- Unless specifically
history.** No "this used to be X", no bug
archaeology in comments — write code as if it had always been this way.
- **Report facts, then your reading — labelled as yours
seats, and entitlements are organisation-scoped in enterprise.
## UI and Security
- Do not hard-code user-facing strings. Add CE strings to `src/client/src/constants/messages/en.ts`; enterprise-only strings belong in the private