We recommend developing in a virtual environment managed by uv: List the available skills, and what each one is for, with: Install them with: diffusers-cli skills update refreshes what you installed. Skills used to be installed through the Makefile, which symlinked the project-level .claude/skills and .agents/skills at .ai/skills in this repo. Remove those links if they exist — otherwise the install writes through them into .ai/ itself: At the start of a session, confirm the setup and tell the user…
This file provides guidance to AI coding agents working on the skills CLI codebase. skills is the CLI for the open agent skills ecosystem. Aliases: skills a works for add. skills i, skills install (no args) restore from skills-lock.json. skills ls works for list. skills experimentalinstall restores from skills-lock.json. skills experimentalsync crawls node_modules for skills.
Most SDK source is generated from the OpenAI API schema. Follow CONTRIBUTING.md before changing generated files. Handwritten policy, automation, tests, and examples should remain small and should not alter exported SDK APIs unless the change explicitly requires it. Follow the custom-code guidance. Budget changes belong in a separate PR containing only .castiron-ratchet.json, with an explicit justification in the PR description. Increases require a human approving review before merging. Agents may investigate and draft proposals, but must not approve budget increases…
A collection of skills for AI coding agents working with Vercel projects. Skills are packaged instructions and scripts that extend agent capabilities. bash bash /mnt/skills/user/{skill-name}/scripts/{script}.sh [args] Skills are loaded on-demand…
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 may also find it…
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…
Version 1.0.0 Engineering January 2026 Note: This document is mainly for agents and LLMs to follow when maintaining, generating, or refactoring React Native codebases. Humans may also find it useful,…
Version 1.0.0 Vercel Engineering Note: This standalone guide is compiled from SKILL.md and its reference files for agents that consume a single AGENTS.md document. Edit the source files, not this…
Cross-agent entry point for the Vercel Optimize skill. The full procedure is in SKILL.md. Use this skill when the user asks to optimize a Vercel project, reduce a Vercel bill,…
PR titles must follow Conventional Commits. See .github/workflows/lint-pr-title.yml for the enforced constraints. Format: <type>: <Description> Turborepo configuration, task behavior, and CLI commands can vary between installed versions and may differ from your training data. Resolve the turbo package from this file's directory or relevant workspace; in monorepos, it may not be visible from the repository root. For example, run node -p "require.resolve('turbo/package.json')" from a workspace that depends on turbo. Read docs/README.md inside that installed package first, then read the relevant…
The root AGENTS.md also applies to this app. Geistdocs owns shared runtime behavior, while this app owns Turborepo content, routes, metadata, assets, and adapters. 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…
Turborepo configuration, task behavior, and CLI commands can vary between installed versions and may differ from your training data. Resolve the turbo package from this file's directory or relevant workspace; in monorepos, it may not be visible from the repository root. For example, run node -p "require.resolve('turbo/package.json')" from a workspace that depends on turbo. Read docs/README.md inside that installed package first, then read the relevant pages from its docs/ directory before changing Turborepo configuration or commands. Heed deprecation notices. These…
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 file contains repository-wide rules for agents and contributors. Use these sources for details instead of duplicating them here: When Corridor's analyzePlan tool is available, create a plan and use the tool to analyze it before generating or modifying code. Apply the resulting security guidance before writing code. Work inside the package you are changing; libs/DEVELOPMENT.md covers environment setup (uv, make) and the edit-test-lint loop. Do not add dependencies unless required. When adding one, justify its maintenance, adoption, and release…
You are a content writer for a technology company. Your job is to create engaging, informative content that educates readers about AI, software development, and emerging technologies. Our content focuses on: - AI agents and automation - Developer tools and productivity - Software architecture and best practices - Emerging technologies and trends Before writing on any topic: 1. Use the researcher subagent for in-depth topic research 2. Gather at least 3 credible sources 3. Identify the key points readers need…
You are an expert software engineer that solves coding tasks autonomously. You work inside a sandboxed environment with full shell access. Follow this phased workflow for every task: For complex tasks, delegate to subagents: - Use task(subagenttype="researcher") for researching APIs, docs, or patterns - Use task(subagenttype="general-purpose") for independent subtasks
You are a content writer for a technology company. Your job is to create engaging, informative content that educates readers about AI, software development, and emerging technologies. You have access to per-user memory files at /memories/user/. Use ls /memories/user/ to discover available files. Always read your user memory files before starting work. When the user shares preferences, update /memories/user/preferences.md using edit_file.
You are a market research specialist. Your job is to gather and synthesize market data to support go-to-market decisions. Write a thorough markdown report — include methodology, detailed findings per topic, and actionable recommendations for the GTM strategy. Save it to /memories/subagents/market-researcher/market-research-report.md using the writefile tool. The other structured fields should be concise extracts from that report. Return the file path in fullreport_path.
Hugging FaceAGENTS.md
