claude-md-enhancer_skill

This skill analyzes and generates customized CLAUDE.md files for projects, enforcing best practices, modular structure, and tech-stack alignment.

Python

388

GitHub Stars

10

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alirezarezvani/claude-code-skill-factory --skill claude-md-enhancer

analyzer.py12.9 KB
expected_output.json9.8 KB
generator.py19.1 KB
HOW_TO_USE.md12.2 KB
README.md15.8 KB
sample_input.json4.4 KB
SKILL.md16.1 KB
template_selector.py16.7 KB
validator.py14.9 KB
workflow.py15.5 KB

Overview

This skill analyzes, generates, and enhances CLAUDE.md files tailored to your project type, tech stack, and team size. I provide interactive initialization, modular file support, and validation against native Claude Code best practices to produce clear, production-ready CLAUDE.md guidance. Use it to create new documentation, improve existing CLAUDE.md files, or standardize AI-assisted development workflows.

How this skill works

I inspect your repository or provided CLAUDE.md content to detect project type, tech stack, team size, and development phase. I then validate structure and formatting, generate new files or add missing sections, and recommend modular layouts (backend/, frontend/, docs/) when appropriate. All changes are suggested for review before applying so custom content is preserved and outputs match native Claude Code format.

When to use it

Initializing CLAUDE.md for a new project to enforce consistent AI agent guidance
Enhancing an existing CLAUDE.md to follow Claude Code best practices and native format
Splitting a large root CLAUDE.md into modular context-specific files (backend, frontend, database)
Adapting CLAUDE.md guidance to a specific tech stack (TypeScript, Python, FastAPI, React, etc.)
Standardizing CLAUDE.md content across teams or onboarding documentation

Best practices

Analyze existing file first and preserve custom content; only add or enhance sections
Keep the root CLAUDE.md concise (navigation hub) and move detailed guidelines to subfiles
Select template size by team and phase: Minimal for solo/prototype, Core for MVPs, Detailed for production
Validate generated output against native Claude Code examples and the /update-claude-md format
Include tech-specific setup, workflows (TDD, CI/CD), and testing & error-handling sections

Example use cases

Create a CLAUDE.md for a TypeScript React web app with PostgreSQL and Docker for a small team
Enhance a long monolithic CLAUDE.md by splitting into backend/CLAUDE.md and frontend/CLAUDE.md
Generate a production-ready CLAUDE.md for a Python FastAPI service with CI/CD and TDD workflows
Add missing testing requirements and error-handling patterns to improve agent reliability
Customize templates for team size and complexity, turning a core template into modular files

FAQ

No. Enhancements preserve custom content and propose additions; you must confirm any changes before they are applied.

How do you choose template complexity?

I combine detected project type, tech stack, team size, and phase to recommend Minimal, Core, or Detailed templates and suggest modular structure when the project has multiple major components.