shows up as an English optimize on a
Thai research result, nowhere near the code that caused it.
Two things worth keeping in mind if you touch this:
- **The stated
without storage duplication.
### Delegation Guidelines for this Repository
- **Mandatory TDD Review:** When delegating any task that involves modifying code or architecture, explicitly instruct the invoked subagent or skill to read
before claiming one, label honestly, make tests exercise the code they cover — and what will be closed rather than reviewed.
Per-module instructions live in `core/ /.claude/CLAUDE.md`, each with
state or explicitly
CLI-managed host configuration; explain that ownership boundary. Other internal
filesystem code uses `internal/vfs` and validates paths.
- If FileIO lacks a host-local tree operation, prefer
follow its links to the relevant pages.
- Treat source code and tests as authoritative. A brief's unknowns and review items are verification gaps, not automatic requirements.
- Prefer the narrowest
year from now? Is it genuinely essential and **non-obvious from the code itself**?
## CodeReview
Unless you have specific instructions to the contrary, when asked to reviewcode (named
This file
summarizes; it never overrides it.
## Review guidelines
These rules apply to all codereviews on this repository, including automated
reviewers (Codex, CodeRabbit).
- **Language:** always review in English, regardless
boundary
Every workflow, ownership, branch-enforcement, release, or repository-automation
change requires explicit security review under `MAINTAINERS.md`.
## Workflow rules
- Grant the minimum required `permissions`.
- Pin third-party actions to immutable
APIs. Introduce a Node-only runtime dependency only when the task explicitly requires compatibility code and the owning module already has that role.
- Preserve existing public exports and configuration compatibility
that followed it. Reasoning written as ordinary
prose is not detectable and stays a review judgement. The check is a literal match, which is why
this line describes the marker
that covers the change. Use broad wrappers
when touching shared surfaces or before handoff:
- Code tests: `scripts/test/test.sh` (JS, then Python, then policy).
- Focused runners: `scripts/test/test-js.sh`, `scripts/test/test-docs.sh`,
`scripts/test/test-python.sh`, `scripts/test/test-global.sh`.
`test-python.sh` takes
namespace catalog, running crumbs init"
load: "node_modules/agentcrumbs/skills/agentcrumbs/init/SKILL.md"
## agentcrumbs
Add crumbs as you write code — not just when debugging. Mark lines with
`// @crumbs` or wrap blocks in `// #region @crumbs`. They
skills/transformers-js/SKILL.md) — how to use the library
itself. Load this skill when working on code that calls `@huggingface/transformers`.
## Contributing
Before opening a pull request:
- **Check for existing work.** Search open
design system lives in `packages/cli/.agents/skills/cli-ux/` and should be loaded only when the task or codereview touches user-facing CLI behavior.
## First Steps
1. Inspect the current source and tests
generate-check` so generated code stays in sync.
- Do not leave formatting or generated-file drift for the user to discover at
push or review time; run the relevant `make