agent-docs

Separate tool-agnostic agent guidance from Claude-specific content in documentation.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/outfitter-dev/agents-internal --skill agent-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-docs
Source: https://github.com/outfitter-dev/agents-internal/tree/main/internal/skills/agent-docs
Command: npx skills add https://github.com/outfitter-dev/agents-internal --skill agent-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation for AI agents — AGENTS.md, CLAUDE.md, and agent-readable content patterns. Use when creating agent entry points, structuring .claude/ directories, or when "CLAUDE.md", "AGENTS.md", "agent documentation", "machine-readable", or "writing for agents" are mentioned. Covers both configuration and content patterns for agent consumption.

Core Features & Use Cases

  • Guidelines for agent documentation structure and entry points
  • Clear separation of tool-agnostic (AGENTS.md) and Claude-specific (CLAUDE.md) guidance
  • Recommended directory layouts (e.g., .claude/, .claude/rules) and usage patterns

Quick Start

Create an AGENTS.md at the project root and reference it from CLAUDE.md using the @-mention pattern, then move Claude-specific guidance into .claude/CLAUDE.md.

Frequently Asked Questions about agent-docs

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

FAQPage Schema
How do I structure CLAUDE.md and AGENTS.md files for an AI coding project?

To structure agent documentation, create an AGENTS.md at the project root for tool-agnostic guidance and a minimal root CLAUDE.md that references it using @-mentions, moving Claude-specific details into .claude/CLAUDE.md to separate concerns.

What is the difference between AGENTS.md and CLAUDE.md?

AGENTS.md provides tool-agnostic guidance for any AI agent, while CLAUDE.md contains Claude-specific instructions. Separating them ensures your documentation remains reusable across different assistants while keeping Claude configurations isolated.

How do I organize .claude/rules without duplicating content?

Organize .claude/rules by placing modular rules in separate files under the directory, ensuring content is not duplicated between the root CLAUDE.md, .claude/CLAUDE.md, and rules files to maintain a single source of truth.

When do I need to use the @-mention pattern in CLAUDE.md?

Use the @-mention pattern in CLAUDE.md when you need to reference AGENTS.md or other documentation files from the root, keeping the root file minimal while importing tool-agnostic agent guidance and modular rules.

Can I use AGENTS.md for AI assistants other than Claude?

Yes, AGENTS.md is designed as tool-agnostic agent guidance, making it reusable across different AI assistants, while Claude-specific configurations are isolated in CLAUDE.md and the .claude directory structure.

What's the best way to maintain agent documentation during repository restructuring?

During repository restructuring, maintain agent documentation by enforcing a minimal root CLAUDE.md with @-mentions, placing Claude-specific details in .claude/CLAUDE.md, and preserving modular rules under .claude/rules without duplicating content.