- Dependencies: PEP 440 compatible release clauses (rich ~= 14.0), avoid pinning patch releases (rich ~= 14.0.0). - Only add code that is actually used. No speculative APIs or exports. - _internal/ is private — no backwards compatibility needed when refactoring. - uv: uv sync, uv run <cmd>, uv add <pkg> - ruff: uv run ruff check . (lint), uv run ruff format . (format) - pytest: uv run pytest, uv run pytest tests/testfoo.py, uv run pytest -k testname. Tests…
- For requests to add A2UI rendering to AG-UI applications or to scaffold an AG-UI + A2UI quickstart, use skills/ag-ui-a2ui-integration/SKILL.md. - When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through nx (i.e. nx run, nx run-many, nx affected) instead of using the underlying tooling directly - You have access to the Nx MCP server and its tools, use them to help the user - When answering questions about the repository, use the nxworkspace…
Cloudflare's command-line tool and networking daemon written in Go. Production-grade tunneling and network connectivity services used by millions of developers and organizations worldwide. Notes on linting: - .golangci.yaml is configured with new-from-rev and whole-files: true. Touching a file triggers linting of the ENTIRE file, not just the changed hunks. Expect to fix pre-existing issues in files you modify, or add targeted // nolint: <linter> comments with a short justification. - Prefer defer func() { _ = resource.Close() }() over defer…
Packer is HashiCorp's open-source (BUSL-1.1) CLI for building automated machine images. It is a Go program that orchestrates pluggable builders, provisioners, post-processors, and data sources through the hashicorp/packer-plugin-sdk, driven by…
Before planning, generating, reviewing, or modifying any user-facing UI, read docs/design-system/design.md completely. Treat it as the active product design contract for all UI work in this repository. Use docs/design-system/index.html as the visual reference. The Markdown guideline remains authoritative when the two formats differ. For UI implementation: 1. Inspect the nearest existing product surface for behavior and layout context. 2. Reuse primitives from src/components/ui before creating a new component. 3. Use the semantic tokens and supported component axes documented in the…
Comprehensive reference for AI coding agents. Skill Seekers is a Python CLI tool (v3.6.0) that converts documentation sites, GitHub repos, PDFs, videos, notebooks, wikis, and more into AI-ready skills for 21+ LLM platforms and RAG pipelines. Skill Seekers is a universal preprocessing layer that transforms raw documentation and code into structured knowledge assets. It supports 17+ source types and exports to 21+ AI platforms including Claude, Gemini, OpenAI, LangChain, LlamaIndex, and various vector databases. Note: tests/conftest.py checks that skill_seekers is…
Logstash is a server-side data processing pipeline that ingests data from multiple sources, transforms it, and sends it to various destinations. It's part of the Elastic Stack and is a…
Guidance for coding agents working with the QA test infrastructure. See also the root AGENTS.md for general project conventions. The qa/ directory contains three independent test suites: Each suite has…
Guidance for coding agents working with X-Pack (Elastic-licensed) features. See also the root AGENTS.md for general project conventions. X-Pack provides commercial features that extend the Logstash core. Most features integrate…
claude-obsidian is a local-first Agent Skills package for building source-cited, compounding Obsidian knowledge bases. It also ships a Claude Code plugin adapter. The portable workflow is implemented in skills/ and the standard-library claude_obsidian/ core; host hooks never define knowledge behavior. - This repository is the product source. It is not the default user vault. - A user vault is the directory containing .claude-obsidian.json, wiki/, and .raw/. Mutable state always belongs there. - templates/vault/ is the distributable seed. Root wiki/, .raw/,…
This is a routing guide for coding agents. Keep shared instructions model-independent; put task-specific detail next to the code or in the linked guides. Rules closer to the code take precedence. For the directory you are changing, read the nested AGENTS.md in that directory and any applicable ancestors. Load other documentation when the task needs it.
These rules apply to docs/ changes in addition to the root instructions. Two audiences, nothing else. If a page serves neither, it does not belong here. Internal process artefacts (migration task lists, validation checklists, design proposals, release runbooks) are not documentation. Keep them out of docs/, or fold the durable part into internals/contributing.md. Six top-level sections: start/, cases/, desktop/, im/, cli/, internals/. Register any added section in the sections array of site/scripts/generate-docs-manifest.mjs. docs/en/ mirrors the Chinese tree file for file.…
VercelAGENTS.md
