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 -The Cross-Tool AI Rules File

AGENTS.md is the closest thing the AI coding tool ecosystem has to a universal standard. One file that works across Codex, Cursor, Jules, Copilot, and Gemini CLI.

Last updated: 2026-07-01

What AGENTS.md is

AGENTS.md is an open, cross-tool standard -plain markdown with no proprietary syntax -that tells AI coding agents about your project. It is now stewarded by the Agentic AI Foundation under the Linux Foundation. Unlike CLAUDE.md (Claude-specific) or .cursor/rules (Cursor-specific), AGENTS.md is designed to be read by any tool that supports it. The list is growing: Codex, Cursor, Jules (Google), GitHub Copilot Agent, Gemini CLI, and others.

What to put in AGENTS.md

Keep it under 300 lines. Agents deprioritize content buried deep in long files. Cover: project overview and stack, folder structure, key conventions, what the agent must never do, and how to run tests. Concrete examples beat abstract descriptions every time.

Complete AGENTS.md template

This template covers the essentials. Customize the stack section for your project.

AGENTS.md

# Project Agent Guidelines

## Project Overview
[One paragraph: what this project is, what it does, who it is for.]

## Tech Stack
- Language: TypeScript (strict)
- Framework: Next.js 16 App Router
- Styling: Tailwind CSS v4
- UI: shadcn/ui
- State: Zustand
- Testing: Vitest + React Testing Library

## Repository Structure
```
src/
├── app/        # Routes (App Router). Thin pages only.
├── components/ # Shared UI components.
├── features/   # Business domain modules.
├── hooks/      # Custom React hooks.
├── lib/        # Server-only utilities.
├── types/      # Global TypeScript types.
└── utils/      # Pure helper functions.
```

## Coding Conventions

### Naming
- Files: kebab-case | Components: PascalCase | Hooks: useCamelCase
- Booleans: isX, hasX, canX | Event handlers: handleX | Prop callbacks: onX
- Constants: UPPER_SNAKE_CASE

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

### TypeScript
- No `any`. Use `unknown` and narrow with type guards.
- No enums. Use union string literals.
- Zod for all external data validation.

## What You Must NOT Do
- Do NOT add pages/ directory -this project uses App Router exclusively.
- Do NOT use useEffect for data fetching -use Server Components.
- Do NOT use any without an explicit comment explaining why.
- Do NOT create files outside the established folder structure.

## Running Tests
```bash
npm run test        # Unit tests (Vitest)
npm run test:e2e    # End-to-end (Playwright)
```

## Pull Request Guidelines
- All new features need a unit test.
- Keep PRs focused: one feature or fix per PR.
- Update types in src/types/ if you add new data shapes.

AGENTS.md -The Cross-Tool AI Rules File

What AGENTS.md is

What to put in AGENTS.md

Complete AGENTS.md template

Generate your AGENTS.md in minutes