Free Claude developer tool

CLAUDE.md Generator

Create a concise project briefing Claude Code can load across sessions. Focus on stable facts Claude should not have to rediscover every time it works in the repository.

Local processing: generation runs in your browser. FixTools does not send the form content to Claude or Anthropic.

Project nameProject summaryStack — one item per lineCommands — one per lineArchitectureRules — one per lineDefinition of done

Generated output

CLAUDE.md

# My Next.js App

Production web application using the Next.js Pages Router.

## Stack
- Next.js 14
- React 18
- Tailwind CSS
- Node.js 24

## Commands
- npm test
- npm run build
- npm run lint

## Architecture
Tool pages live under pages/. Shared UI lives under components/. Preserve public URLs and canonical tags.

## Project rules
- Do not change public URLs without redirects
- Do not claim a tool works unless it is implemented
- Run tests and production build before opening a PR

## Definition of done
Tests pass, production build passes, changed routes render correctly, and SEO metadata remains valid.

How to use this tool

STEP 1

Describe the project, stack and commands Claude should know.

STEP 2

Add architecture boundaries, coding rules and completion criteria.

STEP 3

Copy the result to CLAUDE.md in the project and keep it updated as the codebase changes.

What belongs in CLAUDE.md?

Useful content includes build, test and lint commands; stable architecture; naming and formatting rules; deployment constraints; files Claude should avoid; and project-specific definitions of done.

Keep instructions specific

“Use two-space indentation” is actionable. “Write clean code” is not. Claude Code documentation recommends specific, structured instructions and regular maintenance.

Use imports when the file grows

CLAUDE.md can import other instruction files, letting teams keep the root briefing concise while splitting specialized guidance into smaller documents.

Related Claude resources

CLAUDE.md Guide →Claude Code Guide →Claude Skill Generator →Claude MCP Guide →

Frequently asked questions

Where should CLAUDE.md live?

A project CLAUDE.md can live in the repository. Claude Code also supports user-level instructions for personal preferences across projects.

Should secrets be stored in CLAUDE.md?

No. Treat project instructions as source-controlled documentation and keep credentials or sensitive secrets out of them.

Can CLAUDE.md replace Skills?

Not always. CLAUDE.md is best for persistent project context and rules; Skills are better for reusable procedures that should load when relevant.