agents_md

Creates AGENTS.md convention files defining project rules, structure, and coding standards for AI assistants.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill agents-md-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents_md
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/agents_md
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill agents-md-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding assistants often ignore project-specific conventions because they lack persistent context about your codebase rules. This Skill guides you through creating AGENTS.md files that encode your tech stack, directory structure, naming conventions, and forbidden patterns so AI agents consistently follow your standards. ## Core Features & Use Cases - Root AGENTS.md Templates: Generate a project-level instruction file covering tech stack, directory structure, naming rules, and forbidden patterns like any types or console.log in production. - Nested Module Conventions: Create scoped AGENTS.md files for subdirectories like src/components or src/api with module-specific rules. - Monorepo Configuration: Define cross-package rules and package maps for monorepos with shared UI and utility packages. - Use Case: You onboard an AI assistant to a Next.js 15 monorepo. Use this Skill to generate a root AGENTS.md plus nested files for components and API routes, so every AI-generated change respects your Tailwind, Zod, and Server Components conventions. ## Quick Start Create an AGENTS.md file for my project that documents the tech stack, directory structure, naming conventions, and forbidden patterns for AI coding assistants.

Frequently Asked Questions about agents_md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an AGENTS.md file for my project?

Start by reading your package.json, tsconfig.json, and linter configs to extract the tech stack. Then document the directory structure, naming conventions, forbidden patterns, and preferred approaches in a root AGENTS.md file at your repository root.

What should an AGENTS.md file contain?

An AGENTS.md file should contain a project overview, tech stack list, directory structure map, code conventions for naming and imports, forbidden patterns like any types, and preferred approaches such as Server Components or Zod validation.

Can I use multiple AGENTS.md files in a monorepo?

Yes, you can place nested AGENTS.md files in subdirectories like src/components or src/api with module-specific rules. A root file defines cross-package rules and a package map, while nested files override or extend conventions for their scope.

How do I keep AGENTS.md conventions up to date?

Update AGENTS.md whenever you add new technology, change naming patterns, or restructure directories. Treat it as living documentation and verify periodically that AI assistants do not violate the stated rules.

What are the limitations of AGENTS.md convention files?

AGENTS.md only works with AI assistants that read and respect instruction files, and rules are advisory rather than enforced. For hard guarantees, combine conventions with linters, type checking, and CI validation.