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.

Tool-Specific

AGENTS.md vs CLAUDE.md vs .cursor/rules

Three files, three tools, one goal: make your AI agent follow your rules. Here is exactly what each file does and which ones your project needs.

Last updated: 2026-07-01

The short version

CLAUDE.md is read exclusively by Claude (Anthropic's tool). .cursor/rules is read exclusively by Cursor. AGENTS.md is a cross-tool open standard read by a growing list of tools including Codex, Cursor, Jules, GitHub Copilot, and Gemini CLI. If you use one tool, use that tool's native file. If you use multiple tools or want a single source of truth, use AGENTS.md (or use AGENTS.md as the source and generate the others from it).

File-by-file breakdown

CLAUDE.md: read by Claude Code and Claude in IDEs at every session start. Project-wide scope; can be nested in subdirectories for sub-project rules. Free-form markdown. No required structure. .cursor/rules/*.mdc: the current Cursor format. Replaced the legacy .cursorrules file (which still works but is deprecated). Each .mdc file has YAML frontmatter for scoping: always-apply, auto-attach to file patterns, agent-requested, or manual. This scoping is unique -no other format supports it natively. AGENTS.md: the open standard. Plain markdown, no required structure. Supported by Codex, Cursor, Jules, GitHub Copilot, Gemini CLI, and more. Stewarded by the Linux Foundation.

Which ones does your project need?

If you only use Claude Code: CLAUDE.md only. If you only use Cursor: .cursor/rules/ only. If you use both: maintain AGENTS.md as the source of truth, then have CLAUDE.md and a .cursor/rules/main.mdc import or mirror the same content so nothing drifts out of sync. The worst pattern is maintaining separate files with inconsistent rules -one tool follows TypeScript conventions, the other doesn't. Keep one source of truth.

The .cursorrules file -is it dead?

Not dead, but legacy. Cursor still reads .cursorrules for backward compatibility, but the new .cursor/rules/*.mdc format is strictly better: scoped rules prevent irrelevant context from being loaded, and you can organize by concern (one file for React, one for TypeScript, one for testing). Migrate when you get a chance -the performance and accuracy improvement is measurable.