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

.cursorrules is Legacy. Here's What Changed.

Cursor deprecated the single .cursorrules file in favor of .cursor/rules/*.mdc. Here's exactly what changed and what you should do about it.

Last updated: 2026-07-01

What changed and why

The original .cursorrules was a single flat file that loaded on every request -every prompt, every context window. This was wasteful: your React conventions loaded when you were editing a SQL migration, and your testing rules loaded when you were writing CSS. The new .cursor/rules/*.mdc format lets you scope rules to specific file patterns, making context tighter and reducing token waste.

The .cursorrules file -still works, but legacy

Cursor still reads .cursorrules for backward compatibility. If you have one, you don't need to migrate immediately. But new features (scoping, auto-attachment, agent-requested mode) are only available in the .mdc format. The .cursorrules format is effectively frozen -no new capabilities will be added to it.

What .cursor/rules/*.mdc adds

Four activation modes -(1) alwaysApply: true, loads on every request (equivalent to old .cursorrules behavior). (2) globs scoping, auto-attaches when matching files are open. (3) agent-requested, Cursor reads the description and decides when the rule is relevant. (4) Manual, only loaded when you explicitly reference the rule. This scoping is the major advantage -you can have 10+ rule files without bloating every context window.

How to migrate from .cursorrules

(1) Create the .cursor/rules/ directory. (2) Split your .cursorrules into logical groups (react.mdc, typescript.mdc, structure.mdc). (3) Add YAML frontmatter to each with description and globs. (4) Set alwaysApply: true only for project-wide conventions. (5) Delete .cursorrules once you've verified the new files work.

Migration example

# Before: .cursorrules (single file, always loaded)
React conventions...
TypeScript conventions...
Testing conventions...
Folder structure...
[Everything loads every time, regardless of context]

# After: .cursor/rules/ directory

# .cursor/rules/react.mdc
---
description: React component conventions
globs: ["**/*.tsx", "src/components/**"]
alwaysApply: false
---
[React rules -only loads when .tsx files are open]

# .cursor/rules/typescript.mdc  
---
description: TypeScript strict mode conventions
globs: ["**/*.ts", "**/*.tsx"]
alwaysApply: false
---
[TypeScript rules -loads for all TS files]

# .cursor/rules/project.mdc
---
description: Project-wide architecture and structure
alwaysApply: true
---
[Critical rules -always loaded]