Zero is a pre-1 experiment in building an agent-first programming language. Keep public-facing changes honest about what works today without weakening that positioning. Zero is still being shaped around the needs of agents. Breaking changes are acceptable when they move the language, standard library, compiler, or tooling closer to that goal. Do not preserve legacy behavior by default. Prefer the clearer agent-facing design over compatibility shims, migration layers, or carrying old paths forward. Keep examples, docs, tests, and command contracts…
5.4k5mo agoReviewMountCreate a free account to mount
Guidance for AI coding agents working in this repository. agent-desktop is a tool that AI agents invoke, not an agent. It is a Rust CLI and C library that reads native accessibility trees and returns structured JSON with ref-based element ids. The observe-act loop lives in the calling agent. It never embeds an LLM and has no GUI or interactive prompt. It does not automate web pages (use agent-browser). It cannot see UIs that expose no accessibility tree. Each platform…
4.8k2d agoReviewMountCreate a free account to mount
This project uses the packaged Geistdocs architecture. The @vercel/geistdocs package owns shared runtime behavior; this app owns local content, configuration, adapters, and site-specific routes. Use these instructions when an AI coding agent edits this project.
4.8k2d agoReviewMountCreate a free account to mount
CONTRIBUTING.md is the contribution guide: setup and commands, the constraints the implementation must respect, the debugging and testing workflow, and the security requirements that every change must preserve. It applies…
Steady10 mentions in 2 weeks
No other project uses it yet
4.4k33d agoReviewMountCreate a free account to mount
Instructions for AI coding agents working with this codebase. Do not say the work is "ready", "done", "good to go", "complete", or similar until you have personally run the binary and exercised the change on its happy path. A passing test suite is necessary, not sufficient — tests in this repo do not always construct the full runtime, attach a TTY, or spawn background threads, so they will not catch startup crashes, render regressions, or thread-lifetime bugs. Before reporting the…
3.7k1d agoReviewMountCreate a free account to mount
These instructions apply to work under sdk/ and supplement the repository-level AGENTS.md. This file is maintainer guidance, not consumer documentation. Keep setup and the supported public surface in sdk/README.md. Keep exact API shapes in the SDK modules, their tests, and the declarations in sdk/types/. Add details here only when they help an agent choose the right owner, preserve a non-obvious invariant, or run the right proof. The native Node-API architecture and security model are documented in sdk/NAPI.md. The SDK has…
3.7k1d agoReviewMountCreate a free account to mount
Instructions for work under tests/. They supplement the repository-level AGENTS.md, which still owns the readiness rules, CI gates, and Zig conventions. tests/ holds the checks that run against the built binary or against a model of its design. Unit tests do not live here: Zig tests stay inline in the src/ file they cover. Pick the lowest layer that proves the behavior, and extend the closest existing file before creating a new one. Only files that end in .test.ts at…
3.7k1d agoReviewMountCreate a free account to mount
All apps and examples with dev servers use portless to avoid hardcoded ports. Portless assigns random ports and exposes each app via .localhost URLs. Naming convention: - Docs app: docs.wterm → docs.wterm.localhost - Examples: <name>.wterm → <name>.wterm.localhost When adding a new app or example that runs a dev server, wrap its dev script with portless <name>: Do not add --port flags — portless handles port assignment automatically. Do not add portless as a project dependency; it must be installed globally.
3.6k3d agoReviewMountCreate a free account to mount
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices. This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree…
3.6k3d agoReviewMountCreate a free account to mount
Instructions for AI coding agents working with this codebase. This is a Turborepo monorepo with pnpm workspaces: The CLI is a Rust binary with an npm shim. The Rust crate lives in packages/opensrc/cli/. Or from root: turbo dev, turbo build Releases are manual, single-PR affairs. The maintainer controls the changelog voice and format. To prepare a release: When the PR merges, CI compares packages/opensrc/package.json version to what's on npm. If it differs, it builds all 7 platform binaries, publishes to…
3k7mo agoReviewMountCreate a free account to mount
This file is the workflow index. Before planning, editing files, or acting on an issue/PR, read workflow context, then select the matching path below. If the directing person's role is unknown, follow its mandatory GitHub permission lookup and routing rules. Read required guides in full before the relevant stage. Read additional guides only when their conditions apply; the linked steps are mandatory, not optional reference material. Normal development targets canary. The linked production/release workflows define the exceptions. Repository specialists (researchers,…
Steady12 mentions in 2 weeks
No other project uses it yet
2.6k16d agoReviewMountCreate a free account to mount
This project uses the packaged Geistdocs architecture. The @vercel/geistdocs package owns shared runtime behavior; this app owns local content, configuration, adapters, and site-specific routes. Use these instructions when an AI coding agent edits this project.
Steady12 mentions in 2 weeks
No other project uses it yet
2.6k16d agoReviewMountCreate a free account to mount
%% lat:begin %% # Before starting work Use Lat's knowledge graph to ground each task before changing code. After EVERY task, before responding to the user: Lat.md is the project's structured knowledge graph for architecture, design decisions, behavior, and tests. The graph lives in lat.md/ as cross-linked Markdown describing what the project does and why. Use it to ground work in actual architecture, and keep it a focused snapshot of the current implemented state rather than a journal or changelog.
Surging1 mention in 2 weeks
1 project uses a version of this
2k24d agoReviewMountCreate a free account to mount
Use Lat's knowledge graph to ground each task before changing code. After EVERY task, before responding to the user: Lat.md is the project's structured knowledge graph for architecture, design decisions, behavior, and tests. The graph lives in lat.md/ as cross-linked Markdown describing what the project does and why. Use it to ground work in actual architecture, and keep it a focused snapshot of the current implemented state rather than a journal or changelog. Project-specific lat documentation belongs in lat.md/. Do…
Surging1 mention in 2 weeks
1 project uses a version of this
2k24d agoReviewMountCreate a free account to mount
Use pnpm for all package management commands (not npm or yarn). Exception: End-user install instructions should use npm (e.g. npx emulate, npm install emulate) since npm is universal. emulate is a zsh built-in command (it sets shell emulation mode). Running bare emulate in zsh invokes the shell built-in, not the npm binary. Always use npx emulate in user-facing CLI examples, docs, skills, help output, and post-command messages. The only exception is when emulate appears as a subprocess argument to another…
This version has breaking changes. APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules -->
This document contains critical rules and guidelines for AI agents working on this codebase. All log statements MUST use static strings only. NEVER include dynamic values, regardless of severity. The…
1.8k9mo agoReviewMountCreate a free account to mount
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 may also find…
1.7k8mo agoReviewMountCreate a free account to mount
This file is the source of truth for agent guidance in this repo. CLAUDE.md is symlinked here. After any code changes, always run: Fix errors before finishing. Do not bypass hooks with --no-verify. When changes are pushed to main:
1.6k7mo agoReviewMountCreate a free account to mount
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices. This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree…
Surging+28 new adopters in 4 weeks
38 projects use a version of this
1.6k7mo agoReviewMountCreate a free account to mount
VercelAGENTS.md