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.

Problem-Solving

Cursor AI Keeps Putting Files in the Wrong Place

It's not a Cursor bug. Cursor doesn't know your folder structure -because you haven't told it yet. Here's the fix.

Last updated: 2026-07-01

Why this happens

Cursor generates code based on training data patterns. If your project uses a feature-based folder structure (src/features/auth/components/LoginForm.tsx), but the most common React pattern in training data is a flat src/components/ structure, Cursor will default to flat. It isn't broken -it just doesn't know your project's conventions without being told.

The fix: encode your folder structure explicitly

Add a .cursor/rules/.mdc file that maps out your exact folder structure and what belongs in each folder. Be specific. "Put components in components/" is too vague. "UI components used across 2+ routes live in src/components/. Route-specific components live in src/app/[route]/_components/ with an underscore prefix." is actionable.

Folder structure rules template

Customize this with your actual paths and drop it in .cursor/rules/structure.mdc.

.cursor/rules/structure.mdc

---
description: Project folder structure and file placement rules
alwaysApply: true
---

# File Placement Rules

When creating new files, use these rules to decide where they go:

## Components
- src/components/  → Shared UI used in 2+ different routes/features
- src/app/[route]/_components/  → UI used only in that specific route (underscore prefix hides from routing)
- src/features/[feature]/components/  → UI specific to one business domain

## Logic
- src/hooks/  → Shared custom hooks used across 2+ features
- src/features/[feature]/hooks/  → Hooks specific to one feature
- src/utils/  → Pure helper functions (no side effects, no React)
- src/lib/  → Pre-configured server-only clients (Prisma, Stripe, auth)

## State
- src/store/  → Zustand stores for global UI state only
- (Never store server/async data in Zustand -use React Query cache)

## Types
- src/types/  → Global TypeScript interfaces used across features
- src/features/[feature]/types.ts  → Types specific to one feature

## API / Server
- src/app/api/[route]/route.ts  → Next.js route handlers
- src/features/[feature]/actions/  → Server Actions for this feature

## DO NOT
- Do not create a pages/ directory (App Router project)
- Do not put logic in app/ route files -keep route files thin
- Do not create new top-level src/ folders without discussion

What to do after adding this file

Test it immediately. Ask Cursor: "Create a LoginForm component for the auth feature." Without the rules file, it would create src/components/LoginForm.tsx. With the rules file, it should create src/features/auth/components/LoginForm.tsx. If it still gets it wrong, be even more explicit -add a "When creating a component for a specific feature, always put it in src/features/[feature]/components/." line.