What is a CLAUDE.md file and how does it work?

A CLAUDE.md file is a Markdown conventions file that Claude Code reads automatically when you start a session. It contains your project's folder structure, coding standards, naming conventions, and performance rules - so Claude writes consistent code from the first prompt. standarx generates this file for you in under 3 minutes with a guided wizard for React and Next.js projects.

How do I create cursor rules (.cursor/rules/*.mdc) for my project?

A .cursor/rules/*.mdc file tells Cursor's AI Composer exactly how to structure and write code for your project. With standarx, you select your framework (React or Next.js), choose a folder structure, toggle coding standards, and configure performance optimizations. The tool generates a clean .cursor/rules/*.mdc file you drop into your project root - Cursor reads it automatically.

Why does my AI coding assistant write messy or inconsistent code?

AI coding assistants like Claude Code, Cursor, and Codex produce inconsistent code because they don't know your project's specific conventions. Without explicit rules, the AI invents a different folder layout every time, mixes naming patterns, skips error handling, and ignores performance optimizations. The fix is giving your AI a conventions file (CLAUDE.md, .cursorrules, or AGENTS.md) that defines what "good" means for your stack. standarx generates these files automatically.

How do I stop AI from changing my folder structure every time?

AI coding agents change folder structures because they have no reference for your project's architecture. The solution is creating a rules file that explicitly defines your directory layout, what each folder is for, and how new files should be organized. standarx lets you configure a complete folder structure (with definitions for each directory), then generates a Markdown file your AI reads before writing any code - ensuring consistent structure across every session.

What coding standards should my AI agent follow for React and Next.js?

For React and Next.js projects, your AI agent should follow standards covering: named exports for components, TypeScript strict mode, proper error boundaries, semantic HTML, file size limits, import ordering, consistent naming conventions (PascalCase for components, camelCase for utilities), and accessibility (ARIA attributes, keyboard navigation). standarx provides a curated library of 30+ coding standards you can toggle on/off and customize, then generates a file your AI obeys.

What is "vibe coding" and how do I fix problems with it?

Vibe coding is when you build with AI tools (like Cursor or Claude Code) without setting explicit rules - you just "vibe" and let the AI decide everything. The problems: inconsistent folder structures, mixed coding patterns, missing optimizations, and unmaintainable code. The fix is giving your AI a conventions file before you start coding. standarx generates these files (CLAUDE.md, .cursorrules, AGENTS.md) so your AI follows consistent standards from line one - structured vibe coding.

How-To

How to Create a CLAUDE.md That Claude Actually Reads

CLAUDE.md takes 20 minutes to set up and saves hours every week. Here is exactly how to do it right.

Last updated: 2026-07-01

What CLAUDE.md is

CLAUDE.md is a Markdown file that Claude Code reads automatically at the start of every session. It is your project's onboarding document for Claude -it tells Claude your tech stack, folder structure, coding conventions, and rules before any code is written. There is no setup required: just create the file and Claude will read it.

Where to put it

Put CLAUDE.md at the root of your repository. Claude reads it automatically. You can also put CLAUDE.md files in subdirectories -Claude reads them when working in that directory. This is useful for monorepos where the backend and frontend have different conventions.

What to include (and what to skip)

Include: tech stack, folder structure, key conventions (exports, naming, typing), what Claude must never do, and how to run tests. Skip: general programming advice Claude already knows, copy-pasted documentation from libraries, and anything longer than about 300 lines. Longer files get partially deprioritized. Concise, concrete, specific beats exhaustive.

Minimal effective CLAUDE.md

This template covers the essentials in under 100 lines.

CLAUDE.md

# Project Overview
[One paragraph describing what this project is and does.]

## Stack
- Framework: [Next.js 16 App Router / React 19 / etc.]
- Language: TypeScript (strict)
- Styling: [Tailwind CSS v4 / CSS Modules / etc.]
- State: [Zustand / Context / React Query]
- Testing: [Vitest + React Testing Library]

## Folder Structure
src/
├── app/        # [Routes only / Pages]
├── components/ # Shared UI components
├── hooks/      # Custom React hooks
├── lib/        # Server utilities (server-only)
├── types/      # Global TypeScript types
└── utils/      # Pure helper functions

## Key Rules
1. Named exports only -never default export a component.
2. No `any` in TypeScript -use `unknown` and narrow.
3. [Framework-specific rule, e.g.: "Server Components are default -add 'use client' only when needed"]
4. One component per file -file name is kebab-case.
5. Booleans prefixed isX / hasX / canX.

## Never Do
- [Your most commonly violated rule]
- [Another frequent violation]

## Run Tests
```bash
npm run test
```

How to test that Claude is reading it

Start a fresh Claude Code session and ask: "Summarize the most important rules from my CLAUDE.md." Claude should be able to list your key rules. Then ask it to write a small component and check each convention. If Claude can't summarize your rules or still violates them, your file is too long, too vague, or the rules aren't specific enough -add concrete examples.