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 Write Cursor Rules in 2026

The .cursor/rules format changed. Here is the complete guide to writing .mdc rule files that Cursor actually follows.

Last updated: 2026-07-01

The .cursor/rules format (current)

Cursor moved from a single .cursorrules file to a .cursor/rules/ directory of .mdc files. Each .mdc file is Markdown with YAML frontmatter. The frontmatter controls when the rule is applied: always (loaded every request), auto-attached (loaded when matching files are open), agent-requested (Cursor decides when it's relevant), or manual (only when you reference it).

YAML frontmatter options

The three frontmatter fields: description (required -tells Cursor what the rule covers, also used for agent-requested mode), globs (optional array of file patterns for auto-attachment), alwaysApply (boolean -whether to load regardless of context). Use alwaysApply: true sparingly -only for project-wide conventions. Scope everything else with globs.

Step-by-step: create your first rule file

Here is a minimal but complete example of a well-structured .mdc rule file.

.cursor/rules/react-conventions.mdc

---
description: React component and naming conventions for this project
globs: ["**/*.tsx", "src/components/**", "src/hooks/**"]
alwaysApply: false
---

# React Conventions

## Components
- Named exports only. No default exports.
- One component per file.
- Props typed with interfaces above the component.

## Hooks
- Custom hooks in src/hooks/ with use prefix.
- Always include dependency array in useEffect.

## Naming
- Files: kebab-case (user-card.tsx)
- Components: PascalCase (UserCard)
- Booleans: is/has/can prefix (isLoading, hasError)

## What NOT to Do
- Never use default exports for components.
- Never use useEffect to fetch data.
- Never inline anonymous functions as event handler props.

Rule scoping strategy

Create separate .mdc files per concern rather than one giant file: react.mdc, typescript.mdc, testing.mdc, structure.mdc. Use globs to auto-attach the right rules to the right file types. This keeps context tight -your testing rules don't load when you're editing a UI component.

Testing your rules

After adding a rule file, test it immediately: open Cursor, open a file that matches your globs, and ask Cursor to create something that would normally violate your rules. Check if the output follows the rule. If not, the rule is too vague -add a concrete "do this, not that" example. Concrete examples beat prose descriptions every time.