this contract (when/how to run the sweep, the `-readme-only` + author-preservation safeties) is documented in `printing-press-library/AGENTS.md` under "Bulk SKILL.md/README.md retrofits".
The same lockstep applies
AGENTS.md
Instructions for AI agents working on Docker documentation.
This site builds https://docs.docker.com/ using Hugo.
## Project structure
```text
content/ # Documentation source (Markdown + Hugo front matter)
├── manuals/ # Product docs (Engine
React Composition Patterns
**Version 1.0.0**
Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React codebases using composition. Humans
React Best Practices
**Version 1.0.0**
Vercel Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React and Next.js codebases. Humans
implementation milestones, blockers, and verification results there.
- Do not wait until the end to document decisions. If a decision changes schema, API contract, trust policy, user-facing workflow, or publishing
Prefer functional programming patterns where appropriate
- Use type-safe builders and DSLs for configuration
- Document public APIs with KDoc comments
- NEVER suppress compiler warnings without a good reason
## Quality Gates
coding agents work effectively in the Cloudflare Workers SDK
monorepo. Prefer authoritative configuration and documentation over copying
details into this file: copied versions, rule lists, and counts become stale.
## Start
agents working in this repository. Human contributors
should also read [CONTRIBUTING.md](CONTRIBUTING.md) and the
[documentation site](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/index.html)
which are the source of truth.
## Project Summary
The NVIDIA Container
skills or duplicate docs-site content. The TSDoc-in-source IS the canonical API documentation for the SDK packages.
For higher-level Supabase guidance (the documentation site, MCP tools, schema
feat:` for new features (not just docs)
- `fix:` for bug fixes
- `docs:` for documentation only
- `refactor:`, `test:`, `chore:` as appropriate
- **Stage files explicitly**: Never use `git add .` or `git commit
logic
- `packages/desktop` - Electron desktop app
- `packages/plugin` - agent integration package
- `packages/server` - local collaboration server
- `docs` - documentation site
## Process safety
Never signal a pid you did not spawn. Signal a held `ChildProcess
shows AI provider usage widgets (Claude, Codex, Cursor, Grok, Devin, and more).
This file documents the engineering conventions for the project. Read it before contributing.
## Agent Instructions
AGENTS.md
assets.lock`
without rebuilding the daemon changes nothing. The pin semantics and
failure signatures stay documented in `app/AGENTS.md` ("Boot-asset
pin").
- `arcbox-snapshot` — snapshot lineage: the checkpoint catalog
(`snapshot`), the device
empty & absolute. It does NOT validate namespaces, resources, seccomp,
capabilities, or hook paths. Document what you rely on before treating it
as a security boundary.
## Conventions & pitfalls
- **ID schemes differ
tokio`/`aya`/`fc-sdk`).
- **Adding a rule**: append a `Rule` whose `reason` names the document
that owns it (charter decision, design doc, AGENTS.md section) — the
reason is what a violation
production
`.unwrap()` or `.expect()`; restrict `unsafe` to justified low-level/FFI
boundaries and document each block with `// SAFETY:`.
- Use checked, saturating, or overflowing arithmetic where overflow affects a
security decision
Error propagation control
- Recovery mechanisms
- Notification on errors
# UI Design Guidelines for Dagu
This document outlines the design principles and guidelines for the Dagu UI based on user feedback