facing, add a `.server-changes/` file instead. See `.server-changes/README.md` for format and documentation.
**Write the description for users, not maintainers.** Both changesets and `.server-changes/` notes ship verbatim
install
pnpm --filter @huggingface/transformers test
pnpm --filter @huggingface/transformers typegen
pnpm --filter @huggingface/transformers docs-generate
```
## Documentation generation
Run the full documentation generator after any JSDoc, docs snippet, task metadata,
or generated
lite app bundles its own `ego-browser` binary that embeds this runtime; `skills/ego-browser/SKILL.md` documents that binary's usage (`ego-browser nodejs <<'EOF' ... EOF`). The repo CLI built here takes
consistency**: Use structured logging throughout
6. **Testing coverage**: Aim for comprehensive test coverage
7. **Documentation**: Comment exported functions and types
Remember: This is a mission-critical networking tool used
lint` for PR-relevant lint validation, or the reason
they were skipped is documented.
- `make generate` was run when config structs or components changed, and the
regenerated files are committed
sync.Mutex` or `atomic` types
- Use `context.Context` for cancellation propagation
- Channels should have clear ownership; document who closes them
- Prefer `sync.Once` for one-time teardown (`pendingPermission.resolve()`)
### 7. i18n
All user-facing
before creating a new component.
3. Use the semantic tokens and supported component axes documented in the
guideline.
4. Treat `src/style/tokens`, `src/style/generated`, and shared UI primitives as
the executable source
type, :default => value` — defined in `logstash-core/lib/logstash/config/mixin.rb`. The framework handles validation, coercion, and documentation generation from these declarations.
- **Set output concurrency at the class level** with `concurrency :shared
changing, read the nested `AGENTS.md` in that directory and any applicable ancestors. Load other documentation when the task needs it.
## Start Here
- Run `git status --short` before editing and preserve
Documentation Instructions
These rules apply to `docs/` changes in addition to the root instructions.
## Who the docs are for
Two audiences, nothing else. If a page serves neither, it does
branch protections to make another change pass. Maintainer override labels require an explicit, documented decision.
- Repository settings, rulesets, secrets, and required-check changes require explicit user authorization; editing workflow files
React Site Instructions
These rules apply to the public landing page and documentation experience under `site/`.
## Contracts that must not break
- Keep the site independently installable with
make changes here depend on the Python
KVCacheManagerV2 implementation or its migration documents; those files are
temporary and will be removed after the migration.
The current C++ headers and tests
async work.
- Treat Objective-C and third-party callback isolation as untrusted unless documented. Hop explicitly to the correct actor and use `@Sendable` where a callback crosses isolation.
- Avoid `nonisolated
necessary public APIs.
- **Strong Typing**: Use strong typing to ensure that code is self-documenting and to catch errors at compile time.
## Sample Structure
Samples (in `./samples/` folder) should follow
Samples Structure & Design Choices — .NET
> This file documents the structure and conventions of the .NET samples so that
> agents (AI or human) can maintain them without rediscovering decisions.
## Directory layout
AGENTS.md
Instructions for AI coding agents working in the Python codebase.
**Key Documentation:**
- [DEV_SETUP.md](DEV_SETUP.md) - Development environment setup and available poe tasks
- [CODING_STANDARD.md](CODING_STANDARD.md) - Coding standards, docstring format, and performance
Multimodal user inputs support both legacy (`text`, `binary`) and draft-style (`image`, `audio`, `video`, `document`) shapes.
- Interrupted runs complete with `RUN_FINISHED.outcome.type == "interrupt"` and canonical `outcome.interrupts`; do not document