agents-md

Create or update AGENTS.md files documenting conventions and workflows for monorepos and modules.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Nymbo/Skills --skill agents-md
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agents-md
Source: https://github.com/Nymbo/Skills/tree/main/agents-md
Command: npx skills add https://github.com/Nymbo/Skills --skill agents-md

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create or update AGENTS.md files documenting scoped conventions, monorepo maps, cross-domain workflows, and (optionally) per-module feature maps.

Core Features & Use Cases

  • Root AGENTS.md: Global rules + module map + cross-domain workflows.
  • Nested AGENTS.md: Tech-specific instructions for each component/module.
  • Maps: Module map and optional feature maps at the module level.

Quick Start

Place a root AGENTS.md at the repo root; then add nested AGENTS.md at module roots and optionally feature maps in each module.

Frequently Asked Questions about agents-md

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

FAQPage Schema
How do I document conventions and module maps for a monorepo?▼

Create AGENTS.md files at your repo root and in each module directory. Root AGENTS.md defines global rules and builds a module map; nested files provide tech-specific guidance per component. This centralizes cross-domain workflows and governance for both AI agents and human collaborators.

What should go in a root AGENTS.md file?▼

Root AGENTS.md contains global conventions, a module map inventory of all components, and cross-domain workflows. It serves as the entry point for understanding your monorepo's structure and orchestration patterns.

Can I include feature maps alongside module documentation?▼

Yes. Feature maps are optional per-module additions that inventory capabilities within each component. Pair them with module-level AGENTS.md to guide agents through feature discovery and module responsibilities.

When do I need scoped AGENTS.md files instead of a single documentation file?▼

Use scoped AGENTS.md when managing multiple modules or domains. Nested files isolate tech-specific conventions and prevent global rules from becoming unwieldy, making guidance clearer for both human contributors and AI agents navigating each component.

How do module maps help with monorepo governance?▼

Module maps inventory all components and their relationships, establishing a single source of truth for structure. They enable consistent cross-domain collaboration by showing dependencies, ownership, and interaction patterns across your codebase.

What's the difference between root and nested AGENTS.md files?▼

Root AGENTS.md defines shared rules and the module map; nested AGENTS.md at each module root provide tech-specific instructions and optional feature maps. Nesting keeps global guidance concise while allowing component-level customization.