claude-md-generator

Generates and audits CLAUDE.md files and .claude/ directory structures for Claude Code projects.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/fercosnt/fernando-claude-marketplace --skill claude-md-generator-fercosnt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-generator
Source: https://github.com/fercosnt/fernando-claude-marketplace/tree/main/prompt-suite/skills/claude-md-generator
Command: npx skills add https://github.com/fercosnt/fernando-claude-marketplace --skill claude-md-generator-fercosnt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CLAUDE.md is the only persistent context mechanism across Claude Code sessions, yet most projects either lack one or have bloated files that Claude ignores. This Skill creates optimized CLAUDE.md files from scratch or audits and fixes existing ones using context engineering principles compiled from 60+ sources. ## Core Features & Use Cases - Create Mode: Runs a short interview, explores the project (package.json, migrations, tsconfig), then generates a 50-80 line CLAUDE.md plus the full .claude/ structure (settings.json, rules with path-scoping, slash commands). - Improve Mode: Audits an existing CLAUDE.md against an 11-criteria quality scorecard, produces a diagnostic report with a 0-100 score, and applies fixes after approval. - Templates & Defaults: Ships templates for 7 project types (Next.js + Supabase, MCP server, design system, n8n, Express API, React Native, data pipelines) with a default stack assumption when unspecified. - Use Case: Your CLAUDE.md has grown to 350 lines and Claude ignores half the instructions. Run the audit mode to get a scored diagnosis and a refactored version under 80 lines with detail moved into .claude/rules/. ## Quick Start Ask the assistant to create or improve the CLAUDE.md for your project, mentioning your stack and any multi-tenancy or automation requirements.

Frequently Asked Questions about claude-md-generator

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

FAQPage Schema
How do I create a CLAUDE.md file for a new Claude Code project?

Run the create mode, which asks a short interview about your project purpose, stack, multi-tenancy, and automation, then explores your codebase. It generates a 50-80 line CLAUDE.md plus .claude/settings.json, rules files, and slash commands.

How long should a CLAUDE.md file be?

The ideal length is 50-80 lines, with 200 as the acceptable maximum. Beyond 300 lines Claude begins ignoring instructions, and performance degrades uniformly as instruction count grows, so excess detail should move to .claude/rules/ files.

How do I fix a CLAUDE.md that Claude keeps ignoring?

Use the improve mode, which audits the file against an 11-criteria scorecard covering size, command coverage, rule placement, positive framing, and progressive disclosure. It produces a scored diagnostic report and applies fixes after your approval.

What should I include vs exclude in CLAUDE.md?

Include project-specific commands, rules that differ from language defaults, architectural decisions, gotchas, and domain glossary. Exclude standard conventions, linter-covered style rules, code snippets, API documentation, and personality instructions, which the system prompt governs.

Does CLAUDE.md work for projects that are not Next.js and Supabase?

Yes. The skill ships templates for seven project types including MCP servers, design systems, n8n automation, Express APIs, React Native, and data pipelines. The Next.js plus Supabase stack is only the default when no stack is specified.

What are .claude/rules files with path-scoping?

They are topic-specific rule files in .claude/rules/ that load conditionally via YAML frontmatter with glob paths, such as supabase/migrations/**/*.sql. They keep detailed guidance out of CLAUDE.md and load only when Claude works on matching files.