agent-md-refactor

Refactor bloated agent instruction files into linked, categorized markdown documents.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/saajunaid/junai --skill agent-md-refactor-saajunaid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-md-refactor
Source: https://github.com/saajunaid/junai/tree/main/.github/skills/workflow/agent-md-refactor
Command: npx skills add https://github.com/saajunaid/junai --skill agent-md-refactor-saajunaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor bloated agent instruction files (AGENTS.md, .cursorrules, .github/ files, etc.) to follow progressive disclosure principles, splitting monolithic docs into organized, linked documentation.

Works with CLAUDE.md, Cursor (.cursorrules), GitHub Copilot (.github/), Windsurf (.windsurfrules), and any agent system.

Core Features & Use Cases

  • Progressive disclosure: root remains minimal; detailed guidance lives in linked category files (e.g., typescript.md, testing.md, code-style.md, git-workflow.md, architecture.md)
  • Cross-agent compatibility: works with CLAUDE.md, .cursorrules, .github/, .windsurffrules, and other agent systems
  • Structured refactoring: splits monolithic files into categorized, linked documents for easier maintenance and updates

Quick Start

Refactor the bloated agent instruction files by splitting AGENTS.md, .cursorrules, and related files into organized, linked documentation using progressive disclosure.

Frequently Asked Questions about agent-md-refactor

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

FAQPage Schema
How do I refactor bloated agent instruction files using progressive disclosure?

Refactoring bloated agent instruction files with progressive disclosure creates a minimal root file that links to categorized markdown sub-files, replacing monolithic documentation with organized, modular guidance for easier maintenance.

What is progressive disclosure for agent documentation modularization?

Progressive disclosure for agent documentation modularization keeps root instruction files minimal while moving detailed guidance into linked, topic-specific markdown files like typescript.md or testing.md that override defaults where needed.

Can I split CLAUDE.md and .cursorrules files into modular subdirectory documents?

Yes, you can split CLAUDE.md and .cursorrules files into modular subdirectory documents. The refactoring process works across Claude, Cursor, GitHub Copilot, and Windsurf ecosystems by creating linked categorized guidance files.

Does this approach work with GitHub Copilot and Windsurf agent ecosystems?

Yes, this approach works with GitHub Copilot and Windsurf agent ecosystems. It supports cross-agent compatibility for CLAUDE.md, .cursorrules, .github/, and .windsurfrules files by applying structured refactoring across different agent systems.

What's the best way to split monolithic agent docs into linked categorized files?

The best way to split monolithic agent docs is structured refactoring: generate a minimal root file pointing to topic-specific markdown files such as code-style.md, git-workflow.md, and architecture.md, ensuring progressive disclosure across directories.

When should I modularize my agent instruction docs instead of keeping a single file?

You should modularize agent instruction docs when files become bloated and hard to maintain, requiring progressive disclosure to split monolithic structures into categorized, linked documents for easier updates and actionable instructions.