legibility--enhancer

Create and refine AGENTS.md files with root and subdirectory templates.

57|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/patterninc/code-mint --skill legibility-enhancer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legibility--enhancer
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/legibility--enhancer
Command: npx skills add https://github.com/patterninc/code-mint --skill legibility-enhancer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative guidance for creating high-quality AGENTS.md files throughout a codebase, ensuring explicit UX intent and consistent documentation.

Core Features & Use Cases

  • Stepwise collaboration workflow for drafting, reviewing, and finalizing AGENTS.md in root and subdirectories.
  • Provides templates and conventions to align repository guidance with onboarding goals.
  • Used when onboarding new repos to agent-first practices or remediating legibility gaps identified by audits.

Quick Start

Draft an initial AGENTS.md following the root and subdirectory templates and tailor UX intents for your scope.

Frequently Asked Questions about legibility--enhancer

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

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

To create an AGENTS.md file, draft the initial document using structured root and subdirectory templates, then tailor the UX intents and conventions for your specific codebase scope. This stepwise collaboration workflow guides drafting, reviewing, and finalizing the content.

What is an AGENTS.md file used for in a codebase?

An AGENTS.md file is used to improve repository legibility and onboarding by providing collaborative guidance, capturing explicit UX intent, and documenting conventions for human-AI interaction across the codebase.

When do I need to add AGENTS.md files to subdirectories?

You need to add AGENTS.md files to subdirectories when remediating legibility gaps identified by audits or onboarding new repos to agent-first practices, ensuring scoped guidance and consistent documentation throughout the codebase.

Can I use this workflow to document UX intent for agents?

Yes, you can use this workflow to document UX intent through provided templates designed for extracting structured UX intent, key files, and conventions, ensuring explicit human-AI legibility across your repository.

What's the best way to remediate repository legibility gaps?

The best way to remediate repository legibility gaps is to run a structured audit workflow that drafts, reviews, and finalizes AGENTS.md files using root and subdirectory templates to align repository guidance with onboarding goals.

Does this approach require any specific dependencies to start?

No, this approach requires no external dependencies to start; you simply draft an initial AGENTS.md following the root and subdirectory templates and tailor the UX intents for your repository scope.